OVN CNI cannot assign ports to newly created pods on RHOCP 4

Solution Verified - Updated -

Issue

  • Pods that are restarted or created in a specific host/node in OpenShift Container Platform cluster are stuck in a creation loop with following error:

    Mon XX XX:XX:XX <node-name> hyperkube[1942]: E0103 XX:XX:XX.171308    1942 remote_runtime.go:116] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to create pod network sandbox k8s_openscap-pod-XXXXXXXXXX: error adding pod <pod-name> to CNI network \"multus-cni-network\": <pod-name>:ovn-kubernetes]: error adding container to network \"ovn-kubernetes\": CNI request failed with status 400: '<pod-name> failed to configure pod interface: timed out waiting for OVS port binding (ovn-installed) for XX:XX:XX:XX:XX:X
    
  • The OVN pods are not able to assign a port to the newly created pods.

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.8+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content