Description of problem:
We’ve confirmed that the e2e tests are broken on the 4.15 release.
Please see the related PR for details: https://github.com/openshift/operator-framework-olm/pull/1012
Version-Release number of selected component (if applicable):
4.15
How reproducible:
To confirm the issue, we pushed a PR without any code changes: https://github.com/openshift/operator-framework-olm/pull/1012
We re-triggered the tests multiple times, and the failures were consistent each time — indicating the problem is not related to any code change in the PR itself.
Actual results:
Failures - Timeout
Expected results:
Pass
See the errors:
Subscription when bundle unpack retries are enabled [It] should retry failing unpack jobs /go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/subscription_e2e_test.go:2681 [FAILED] Expected <wait.errInterrupted>: timed out waiting for the condition { cause: <*errors.errorString | 0xc0002521d0>{ s: "timed out waiting for the condition", }, } to be nil In [It] at: /go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/subscription_e2e_test.go:2814 @ 05/25/25 01:14:57.429
[FAIL] Install Plan [It] creation with permissions /go/src/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/installplan_e2e_test.go:2940
Since the test failures started appearing and the check is no longer marked as optional, we believe one of the following might be true:
a) The test may have been made non-optional even though it was already failing intermittently.
b) The root cause might be external — for example, a recent RHEL update or a change in an OpenShift component could have increased processing time, leading to timeouts.
Note: It is blocking the https://issues.redhat.com//browse/OCPBUGS-56358 get merged.
- depends on
-
OCPBUGS-61391 [4.13] olmv0 e2e flakes
-
- Closed
-
- links to