-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
co/service-ca reported Progressing=True only for a node reboot which should not happened during a normal cluster upgrade.
Sep 26 02:27:22.901 W clusteroperator/service-ca condition/Progressing reason/_ManagedDeploymentsAvailable status/True Progressing: \nProgressing: service-ca does not have available replicas
Sep 26 02:27:22.901 - 25s W clusteroperator/service-ca condition/Progressing reason/_ManagedDeploymentsAvailable status/True Progressing: \nProgressing: service-ca does not have available replicas
{code:none}
The example job does an upgrade from 4.20.0-0.ci-2025-09-23-172020 to 4.21.0-0.ci-2025-09-26-000607
How reproducible:
Seems always for 4.20 - 4.21 upgrades
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
co does not go Progressing=True only for a node reboot
Additional info:
- relates to
-
OTA-1637 Fail CI if any Cluster Operator reports Progressing=True only up to cluster scaling or a node rebooting
-
- In Progress
-