-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
4.13.z
-
Important
-
No
-
False
-
-
Customer Escalated
Description of problem:
OVN controlPlane is unstable bcz the ovnkube-master containers for all pods are in a restart/CLBO churn: restarting for no discernable reason as connectivity does NOT look to be impaired: though there is a failed kube-apiserver rollout as the installer pod cannot spin up due to the issue w ovnkube-master; both DBs are in sync'd and connected
Version-Release number of selected component (if applicable):
How reproducible:
unsure
Steps to Reproduce:
1. 2. 3.
Actual results:
no new pods can be created: all stuck in containerCreating due to error below
Expected results:
OVN controlPlane is stable and pods can be created
Additional info:
error for failed pods: InstallerPodNetworkingDegraded: Pod "installer-30-ocp-p6810-master-0" on node "ocp-p6810-master-0" observed degraded networking: (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_installer-30-ocp-p6810-master-0_openshift-kube-apiserver_9ff4d0c1-3348-45d9-a60b-d9d129699d8c_0(25b489a6a4ae9d76b5381a95d719a233cfb8e2abc352d26f6b874a22d2875d43): error adding pod openshift-kube-apiserver_installer-30-ocp-p6810-master-0 to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-network" failed (add): [openshift-kube-apiserver/installer-30-ocp-p6810-master-0/9ff4d0c1-3348-45d9-a60b-d9d129699d8c:ovn-kubernetes]: error adding container to network "ovn-kubernetes": CNI request failed with status 400: '[openshift-kube-apiserver/installer-30-ocp-p6810-master-0 25b489a6a4ae9d76b5381a95d719a233cfb8e2abc352d26f6b874a22d2875d43] [openshift-kube-apiserver/installer-30-ocp-p6810-master-0 25b489a6a4ae9d76b5381a95d719a233cfb8e2abc352d26f6b874a22d2875d43] failed to get pod annotation: timed out waiting for annotations: context deadline exceeded