-
Bug
-
Resolution: Done
-
Critical
-
4.17
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Starting with payload 4.17.0-0.nightly-2024-06-27-123139 we are seeing hypershift-release-4.17-periodics-e2e-aws-ovn-conformance failures due to
: [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]
{
"metric": {
"__name__": "ALERTS",
"alertname": "PrometheusKubernetesListWatchFailures",
"alertstate": "firing",
"container": "kube-rbac-proxy",
"endpoint": "metrics",
"instance": "10.132.0.19:9092",
"job": "prometheus-k8s",
"namespace": "openshift-monitoring",
"pod": "prometheus-k8s-0",
"prometheus": "openshift-monitoring/k8s",
"service": "prometheus-k8s",
"severity": "warning"
},
It looks like this was introduced with cluster-monitoring-operator/pull/2392
- is triggering
-
-
- Closed
-
- links to
