Bug 1932620 - Alerts during a test run should fail the test job, but were not
Summary: Alerts during a test run should fail the test job, but were not
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.z
Assignee: sdasu
QA Contact: Amit Ugol
URL:
Whiteboard:
Depends On: 1932618 1932619
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-24 19:13 UTC by Clayton Coleman
Modified: 2022-06-13 15:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1932619
Environment:
Last Closed: 2022-06-13 15:22:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Clayton Coleman 2021-02-24 19:13:17 UTC 
+++ This bug was initially created as a clone of Bug #1932619 +++

+++ This bug was initially created as a clone of Bug #1932618 +++

https://github.com/openshift/cluster-baremetal-operator/pull/110 merged containing a failing alert ClusterOperatorBaremetalDown and TargetDown.

This was the passing run https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-baremetal-operator/110/pull-ci-openshift-cluster-baremetal-operator-master-e2e-agnostic/1364398641615212544

The query in the alert test "shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured" is subtly wrong.

For 4.6, 4.7, and 4.8, we can remove the broken filter clause because both KubeAPILatencyHigh and KubePodCrashLooping on kcm namespace were fixed. In the future we must use "unless X" instead of joining with a "-" because of the way the series match.

After this fix we will be correctly enforcing "no alerts may fire during a CI test run".
Comment 7 Tomas Sedovic 2022-06-13 15:22:43 UTC 
This has been fixed in OpenShift 4.8. I'm closing this BZ, if a backport to 4.6 is requested please reopen.
Note You need to log in before you can comment on or make changes to this bug.