Pods stuck in ContainerCreating with "timed out waiting for OVS port binding " error after OpenShift 4.17 to 4.18 upgrade

Solution Verified - Updated -

Issue

  • Pods fail to configure interface and get stuck in the ContainerCreating status.

  • After upgrading from Red Hat OpenShift v4.17.38 to v4.18.30, some pods are stuck in the ContainerCreating state with the following error:

    error configuring pod [openshift-logging/logging-loki-xxxxx] networking: [openshift-logging/logging-loki-xxxxxx/7bca877c-fddc-4a19-ae3d-ec6761b3fbdb:ovn-kubernetes]: error adding container to network
 "ovn-kubernetes": CNI request failed with status 400: '[openshift-logging/logging-loki-xxxxxx b8809523e96497f81003b1d1e7ebf29f3e87ce007369a3fcdd0f35a1b28784c4 network default NAD default]
 [openshift-logging/logging-loki-xxxxxx b8809523e96497f81003b1d1e7ebf29f3e87ce007369a3fcdd0f35a1b28784c4 network default NAD default] failed to configure pod interface: timed out waiting for OVS port binding (ovn-installed) for aa:bb:cc:dd:ee:ff [10.x.x.x/23]

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.17
    • 4.18
  • OVN-Kubernetes (OVN-K)

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