-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.21.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Approved
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:
[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]
Significant regression detected.
Fishers Exact probability of a regression: 99.98%.
Test pass rate dropped from 100.00% to 93.41%.
Sample (being evaluated) Release: 4.20
Start Time: 2025-10-13T00:00:00Z
End Time: 2025-10-20T08:00:00Z
Success Rate: 93.41%
Successes: 85
Failures: 6
Flakes: 0
Base (historical) Release: 4.18
Start Time: 2025-01-26T00:00:00Z
End Time: 2025-02-25T00:00:00Z
Success Rate: 100.00%
Successes: 79
Failures: 0
Flakes: 0
View the test details report for additional context.
This has caused problems throughout 4.20 and 4.21 jobs, it may have resolved but it also seems to be happening sporadically and fairly often. It almost feels like an external service is down causing this?
We need to get this under control to keep CI signal stable.
Filed by: dgoodwin@redhat.com
- is duplicated by
-
OCPBUGS-65530 Insights operator regressed on firing alert: KubeJobFailed - periodic-gathering
-
- Closed
-