-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21, 4.21.0
-
None
Description of problem:
When networkType is not OVNKubernetes, there's no operand ovnkube-control-plane,network-node-identity,loud-network-config-controller, so skip these rollout check, but has operand multus-admission-controller.
Version-Release number of selected component (if applicable):
v4.21
How reproducible:
Always
Steps to Reproduce:
1. Install a hosted cluster and networkType is not OVNKubernetes, we can set cilium
2. Check test TestUpgradeControlPlane/Main/Wait_for_control_plane_components_to_complete_rollout
3. test failed with error:
{code:java}
Failed === RUN TestUpgradeControlPlane/Main/Wait_for_control_plane_components_to_complete_rollout
eventually.go:258: Failed to get **v1beta1.ControlPlaneComponent: client rate limiter Wait returned an error: context deadline exceeded
util.go:642: Failed to wait for control plane components to complete rollout in 30m0s: context deadline exceeded
eventually.go:383: observed invalid **v1beta1.ControlPlaneComponent state after 30m0s
eventually.go:400: - observed **v1beta1.ControlPlaneComponent e2e-clusters-7t729-control-plane-upgrade-x4bfh/cluster-network-operator invalid: incorrect condition: wanted RolloutComplete=True, got RolloutComplete=False: WaitingForOperands(failed to get deployment ovnkube-control-plane: Deployment.apps "ovnkube-control-plane" not found
Actual results:{code:none}
Test for cni operands rollout failed.
Expected results:
Shoud skip cni related operands rollout check.
Additional info: