Failed to configure pod interface: timed out waiting for OVN port binding #1110
Replies: 5 comments
-
Please attach log bundle |
Beta Was this translation helpful? Give feedback.
-
Hi, this problem has been present for about 2 days and no machineconfig has been applied |
Beta Was this translation helpful? Give feedback.
-
Hi! experiencing this with OCP 4.10.3. Added a machine configuration on workers and masters, and I am hitting the same issue. How did you solve it? EDIT: for my specific use case, there was an issue with security groups on the IaaS (OpenStack). Traffic between master nodes was dropped on some ports. (https://bugzilla.redhat.com/show_bug.cgi?id=2071272) |
Beta Was this translation helpful? Give feedback.
-
Any update about this issue? |
Beta Was this translation helpful? Give feedback.
-
Try following the Rebuild all Openshift-OVN-Kubernetes pods knowledge-base article. It worked for me. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
The problem happened when we tried to apply new configuration that request the restart of nodes.
For example:
Version
Client Version: 4.9.0-0.okd-2021-11-28-035710
Server Version: 4.9.0-0.okd-2022-01-14-230113
Kubernetes Version: v1.22.1-1827+e790d7fa218bce-dirty
Log bundle
28m Warning FailedCreatePodSandBox pod/apiserver-vfkpj (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_apiserver-vfkpj_openshift-apiserver **error adding pod openshift-apiserver_apiserver-vfkpj to CNI network** "multus-cni-network": [openshift-apiserver/apiserver-vfkpj/4581fd06-fc1d-4baa-9390-825666f47f74:ovn-kubernetes]: error adding container to network "ovn-kubernetes": CNI request failed with status 400: '[openshift-apiserver/apiserver-vfkpj ] [openshift-apiserver/apiserver-vfkpj ] failed to configure pod interface: timed out waiting for OVS port binding (ovn-installed) for...
Beta Was this translation helpful? Give feedback.
All reactions