-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.18, 4.19.0, 4.20.0
-
None
-
Approved
-
False
-
-
Release Note Not Required
-
In Progress
(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:
[sig-olmv1][OCPFeatureGate:NewOLM][Skipped:Disconnected] OLMv1 operator installation should block cluster upgrades if an incompatible operator is installed [Suite:openshift/conformance/parallel]
Test has a 94.71% pass rate, but 95.00% is required.
Sample (being evaluated) Release: 4.19
Start Time: 2025-05-21T00:00:00Z
End Time: 2025-05-28T08:00:00Z
Success Rate: 94.71%
Successes: 179
Failures: 10
Flakes: 0
Base (historical) Release: 4.18
Start Time: 2025-01-26T00:00:00Z
End Time: 2025-02-25T23:59:59Z
Success Rate: 0.00%
Successes: 0
Failures: 0
Flakes: 0
View the test details report for additional context.
- depends on
-
OCPBUGS-56813 Component Readiness: [OLM] fix olm.maxOpenShiftVersion float parsing
-
- Verified
-
- is cloned by
-
OCPBUGS-56813 Component Readiness: [OLM] fix olm.maxOpenShiftVersion float parsing
-
- Verified
-
-
OCPBUGS-56820 [release-4.18] OLMv1: faulty parsing of olm.maxOpenShiftVersion allows cluster upgrades when they should be blocked
-
- Closed
-
- links to
-
RHEA-2024:11038 OpenShift Container Platform 4.19.z bug fix update