-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
4.21
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Rejected
-
Squirtle Sprint 279
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
During Upgrade: The operator MUST report Progressing=True (since a version change is a configuration change). It is defined in the o/api docs.
However, CO/operator-lifecycle-manager did not in these upgrade jobs: example1.
: [Monitor:legacy-cvo-invariants][bz-OLM] clusteroperator/operator-lifecycle-manager must go Progressing=True during an upgrade test expand_less1h7m35s{ clusteroperator/operator-lifecycle-manager was never Progressing=True during the upgrade window from 2025-11-12T09:04:26Z to 2025-11-12T10:12:00Z and CVO waited for it over 2 minutes from 2025-11-12T09:27:08Z to 2025-11-12T09:29:12Z}
Version-Release number of selected component (if applicable):
The job upgrades a cluster to 4.21.0-0.nightly-2025-11-12-073943 (from 4.21.0-0.nightly-2025-11-05-234508).
How reproducible:
Seems always for patch level updates
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- clones
-
-
- New
-
- is cloned by
-
-
- New
-
- relates to
-
OTA-1643 Fail CI if there are COs that do not report Progressing=True during a cluster upgrade
-
- In Progress
-