-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.21
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Rejected
-
Squirtle Sprint 279
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
co/olm reported Progressing=True only for a node reboot which should not happened during a normal cluster upgrade.
: [Monitor:legacy-cvo-invariants][bz-OLM] clusteroperator/operator-lifecycle-manager-packageserver should stay Progressing=False while MCO is Progressing=True expand_less44m30s{ 2 (out of 7) unexpected clusteroperator state transitions while machine-config is progressing during the upgrade window from 2025-10-29T05:53:41Z to 2025-10-29T06:38:11Z. These did not match any known exceptions, so they cause this test-case to fail:
Oct 29 06:32:38.018 W clusteroperator/operator-lifecycle-manager-packageserver condition/Progressing status/True Working toward 0.0.1-snapshot
Oct 29 06:32:38.018 - 14s W clusteroperator/operator-lifecycle-manager-packageserver condition/Progressing reason/ status/True Working toward 0.0.1-snapshot
0 unwelcome but acceptable clusteroperator state transitions while machine-config is progressing during the upgrade window from 2025-10-29T05:53:41Z to 2025-10-29T06:38:11Z, as desired.}
How reproducible:
Seems always in
aggregated-aws-ovn-single-node-upgrade-4.21-micro-release-openshift-release-analysis-aggregator
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
co does not go Progressing=True only for a node reboot
Additional info:
- clones
-
-
- New
-
- relates to
-
OTA-1637 Fail CI if any Cluster Operator reports Progressing=True only up to cluster scaling or a node rebooting
-
- Closed
-
- links to