-
Bug
-
Resolution: Done
-
Normal
-
4.19.0, 4.20.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Per Slack thread deads@redhat.com found CR Regression for
[sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early][apigroup:config.openshift.io] [Skipped:Disconnected] [Suite:openshift/conformance/parallel]
due to
"metric": {
"__name__": "ALERTS",
"alertname": "PodDisruptionBudgetLimit",
"alertstate": "firing",
"namespace": "e2e-disruption-monitor-64nmr",
"poddisruptionbudget": "service-network",
"prometheus": "openshift-monitoring/k8s",
"severity": "critical"
},
caused by a bug in the attempt to wait for pods to initialize.
origin#29876 addresses the issue
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to