Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1852974

Summary:	[Feature:Prometheus][Late] Alerts [Top Level] [Feature:Prometheus][Late] Alerts shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured
Product:	OpenShift Container Platform	Reporter:	Corey Daley <cdaley>
Component:	kube-controller-manager	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED DUPLICATE	QA Contact:	zhou ying <yinzhou>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4	CC:	alegrand, anpicker, aos-bugs, erooth, kakkoyun, lcosic, mfojtik, mloibl, pkrupa, spasquie, surbania
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	[Feature:Prometheus][Late] Alerts [Top Level] [Feature:Prometheus][Late] Alerts shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured
Last Closed:	2020-07-06 10:57:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Corey Daley 2020-07-01 16:51:10 UTC

test:
[Feature:Prometheus][Late] Alerts [Top Level] [Feature:Prometheus][Late] Alerts shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured 

is failing frequently in CI, see search results:
https://search.svc.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5BFeature%3APrometheus%5C%5D%5C%5BLate%5C%5D+Alerts+%5C%5BTop+Level%5C%5D+%5C%5BFeature%3APrometheus%5C%5D%5C%5BLate%5C%5D+Alerts+shouldn%27t+report+any+alerts+in+firing+state+apart+from+Watchdog+and+AlertmanagerReceiversNotConfigured

https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-to-4.4-nightly/1278187855524401152

Comment 1 Simon Pasquier 2020-07-03 08:30:03 UTC

Looking at 2 CI jobs [1][2], I see that KubePodCrashLooping alerts are firing during the tests for several pods:
* 6 alerts for kube-controller-manager-* pod in the openshift-kube-controller-manager namespace about containers kube-controller-manager-recovery-controller and cluster-policy-controller crashlooping.
* 1 alert for cluster-version-operator-* pod in the openshift-cluster-version namespace

Reassigning to the kube-controller-manager component team so they check why the kube-controller-manager pods are crashlooping.

[1] https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/684/pull-ci-openshift-cluster-network-operator-release-4.4-e2e-gcp/1278942064037335040
[2] https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/681/pull-ci-openshift-cluster-network-operator-release-4.4-e2e-gcp/1278880665059725312

Comment 2 Maciej Szulik 2020-07-06 10:57:30 UTC


*** This bug has been marked as a duplicate of bug 1842002 ***