OCPBUGS-56821: Add prometheus alert for image stream import failure

[jubittajohn]

Adds prometheus alert ImageStreamImportFailed, for image stream import failure: using the metric openshift_imagestreamcontroller_error_count

• increase(Counter[Time]) doesn’t count the first value of the counter because increase() always compares with the previous value. For the first time, when the counter has a value of 1, there isn’t any previous value to calculate a difference against. Hence, to account for it, we need to use increase(Counter[Time]) > 0 or Counter > 0

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@jubittajohn: This pull request references Jira Issue OCPBUGS-56821, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Add prometheus alert for image stream import error: using the metric openshift_imagestreamcontroller_error_count

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jubittajohn
Once this PR has been reviewed and has the lgtm label, please assign sanchezl for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@jubittajohn: This pull request references Jira Issue OCPBUGS-56821, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.0) matches configured target version for branch (4.21.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (xiuwang+1@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Adds prometheus alert ImageStreamImportFailed, for image stream import failure: using the metric openshift_imagestreamcontroller_error_count

• increase(Counter[Time]) doesn’t count the first value of the counter because increase() always compares with the previous value. For the first time, when the counter has a value of 1, there isn’t any previous value to calculate a difference against. Hence, to account for it, we need to use increase(Counter[Time]) > 0 or Counter > 0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@jubittajohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn	4f77748	link	true	/test e2e-aws-ovn
ci/prow/unit	4f77748	link	true	/test unit

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale