-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
Rejected
-
NI&D Sprint 278
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
co/ingress reported Progressing=True only for a node reboot which should not happened during a normal cluster upgrade.
Sep 26 02:13:48.268 W clusteroperator/ingress condition/Progressing reason/Reconciling status/True ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...\n).
Sep 26 02:13:48.268 - 34s W clusteroperator/ingress condition/Progressing reason/Reconciling status/True ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...\n).
Sep 26 02:21:41.748 W clusteroperator/ingress condition/Progressing reason/Reconciling status/True ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...\n).
Sep 26 02:21:41.748 - 35s W clusteroperator/ingress condition/Progressing reason/Reconciling status/True ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...\n).
Sep 26 02:30:30.771 W clusteroperator/ingress condition/Progressing reason/Reconciling status/True ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...\n).
Sep 26 02:30:30.771 - 33s W clusteroperator/ingress condition/Progressing reason/Reconciling status/True ingresscontroller "default" is progressing: IngressControllerProgressing: One or more status conditions indicate progressing: DeploymentRollingOut=True (DeploymentRollingOut: Waiting for router deployment rollout to finish: 1 of 2 updated replica(s) are available...\n).
{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
-