-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20
-
None
-
None
-
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/openshift-samples did not in these upgrade jobs: example1.
: [Monitor:legacy-cvo-invariants][bz-Samples] clusteroperator/openshift-samples must go Progressing=True during an upgrade test expand_less 50m45s
{ clusteroperator/openshift-samples was never Progressing=True during the upgrade window from 2025-11-14T14:06:47Z to 2025-11-14T14:57:32Z and CVO waited for it over 2 minutes from 2025-11-14T14:26:59Z to 2025-11-14T14:30:14Z}
Version-Release number of selected component (if applicable):
The job upgrades a cluster to 4.21.0-0.ci-2025-11-14-130445-test-ci-op-q7d5riik-latest (from 4.21.0-0.ci-2025-11-12-215635).{code}
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.