The ovnkube-node fails to start on a new worker node

Solution Verified - Updated -

Issue

  • Pods fail to schedule on the node newly created because the network ClusterOperator is not available on it.

    "Error syncing pod, skipping" err="network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: no CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?" pod="openshift-multus/multus-xxxxx" podUID="4d340bce-xxxx-xxxx-xxxx-1d3b6f6733e0"

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.18.22

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