-
Bug
-
Resolution: Unresolved
-
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/olm did not in these upgrade jobs: example1.
: [Monitor:legacy-cvo-invariants][bz-OLM] clusteroperator/olm must go Progressing=True during an upgrade test expand_less33m45s{ clusteroperator/olm was never Progressing=True during the upgrade window from 2025-11-14T06:20:08Z to 2025-11-14T06:53:53Z and CVO waited for it over 2 minutes from 2025-11-14T06:33:02Z to 2025-11-14T06:35:47Z}
Version-Release number of selected component (if applicable):
The job upgrades a cluster to 4.21.0-0.nightly-2025-11-14-050926 (from 4.21.0-0.nightly-2025-11-13-042845).
How reproducible:
Seems quite often for patch level updates in the aggregate job: aggregated-aws-ovn-single-node-upgrade-4.21-micro-release-openshift-release-analysis-aggregator.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- clones
-
-
- Closed
-
- relates to
-
OTA-1643 Fail CI if there are COs that do not report Progressing=True during a cluster upgrade
-
- In Progress
-