-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
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/cloud-controller-manager did not in these upgrade jobs: example1 and example2.
: [Monitor:legacy-cvo-invariants][bz-Cloud Compute] clusteroperator/cloud-controller-manager must go Progressing=True during an upgrade test expand_less22m5s{ clusteroperator/cloud-controller-manager was never Progressing=True during the upgrade window from 2025-11-09T07:44:33Z to 2025-11-09T08:06:38Z and CVO waited for it over 2 minutes from 2025-11-09T07:46:31Z to 2025-11-09T07:49:01Z}
Version-Release number of selected component (if applicable):
The job upgrades a cluster to 4.21.0-0.ci-2025-11-10-001017-test-ci-op-72jgbllp-latest (from 4.21.0-0.ci-2025-11-09-234655-test-ci-op-72jgbllp-initial).
How reproducible:
Seems always for patch level updates
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
- relates to
-
OTA-1643 Fail CI if there are COs that do not report Progressing=True during a cluster upgrade
-
- Review
-