-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
4.12.z
-
Important
-
No
-
Rejected
-
False
-
Description of problem:
When NP are in place is not possible to create/recreate PODs as no CNI can be assigned
Version-Release number of selected component (if applicable):
The client has been affected from 4.12.5 after upgrading to 4.12.24 the issue persists
How reproducible:
Tried in Lab but was not possible to reproduce
Actual results:
Warning FailedCreatePodSandBox 0s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_prometheus-adapter-79fd9cf8fc-rmrl5_openshift-monitoring_72b07a5d-d4a4-4735-9236-7540d9d9b2fd_0(7aaa30a2ad6ef868ddfcb29a7435e539712af6e6a16abb12fbf45dcf222de15e): error adding pod openshift-monitoring_prometheus-adapter-79fd9cf8fc-rmrl5 to CNI network "multus-cni-network": plugin type="multus" name="multus-cni-network" failed (add): [openshift-monitoring/prometheus-adapter-79fd9cf8fc-rmrl5/72b07a5d-d4a4-4735-9236-7540d9d9b2fd:ovn-kubernetes]: error adding container to network "ovn-kubernetes": CNI request failed with status 400: '[openshift-monitoring/prometheus-adapter-79fd9cf8fc-rmrl5 7aaa30a2ad6ef868ddfcb29a7435e539712af6e6a16abb12fbf45dcf222de15e] [openshift-monitoring/prometheus-adapter-79fd9cf8fc-rmrl5 7aaa30a2ad6ef868ddfcb29a7435e539712af6e6a16abb12fbf45dcf222de15e] failed to configure pod interface: timed out waiting for OVS port binding (ovn-installed) for 0a:58:c0:a8:XX:XX [192.168.0.1/25]
Expected results:
The interface get correctly assigned and the POD can move to a running state.
Additional info:
This affects all nodes independently of the role. Doing an OVN DB rebuild did not help.
- links to
