-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.15
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
No
-
None
-
None
-
Rejected
-
Sprint 247, Sprint 248, NE Sprint 260
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
| : [bz-Routing] clusteroperator/ingress should not change |
Has been failing for over a month in the e2e-metal-ipi-sdn-bm-upgrade jobs
I think this is because there are only two worker nodes in the BM environment and some HA services loose redundancy when one of the workers is rebooted.
In the medium term I hope to add another node to each cluster but in the sort term we should skip the test.
—
Update on Dec 10, 2025
The failure appeared in non-upgrade job too: example
The cluster has 3 workers.
: [Monitor:legacy-cvo-invariants][bz-Routing] clusteroperator/ingress should not change condition/Available expand_less2h8m47s{ 2 unexpected clusteroperator state transitions during e2e test run. These did not match any known exceptions, so they cause this test-case to fail:
Dec 09 18:32:32.018 E clusteroperator/ingress condition/Available reason/IngressUnavailable status/False The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
Dec 09 18:32:32.018 - 32s E clusteroperator/ingress condition/Available reason/IngressUnavailable status/False The "default" ingress controller reports Available=False: IngressControllerUnavailable: One or more status conditions indicate unavailable: DeploymentAvailable=False (DeploymentUnavailable: The deployment has Available status condition set to False (reason: MinimumReplicasUnavailable) with message: Deployment does not have minimum availability.)
1 unwelcome but acceptable clusteroperator state transitions during e2e test run. These should not happen, but because they are tied to exceptions, the fact that they did happen is not sufficient to cause this test-case to fail:
Dec 09 18:33:04.078 W clusteroperator/ingress condition/Available reason/IngressAvailable status/True The "default" ingress controller reports Available=True. (exception: Available=True is the happy case)
}
- is cloned by
-
-
- Closed
-
- relates to
-
-
- New
-
-
OTA-362 CI: fail update suite if any ClusterOperator go Available=False
-
- Closed
-
