Node went to NotReady due to the network issue in RHOCP 4

Solution Verified - Updated -

Issue

  • Newly added node went to NotReady state and showing the below error message:

    container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: 
No CNI configuration file in /etc/kubernetes/cni/net.d/
  • Pods of the openshift-multus and openshift-network-diagnostics namespace are not able to schedule on the NotReady node.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

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