After applying NNCP and rebooting, ovs-configuration service failed, causing node to turn `NotReady`

Solution Verified - Updated -

Issue

  • After making changes using NodeNetworkConfigurationPolicy(NNCP) and rebooting the node, the node turns into NotReady.

  • Direct-SSH to the affected node shows ovs-if-br-ex is not configured:

    $ sudo -i
    # nmcli connection show
    NAME                 UUID                TYPE            DEVICE
    Wired connection 1  <UUID_of_interface>  ethernet        <interface_name>
    lo                  <UUID_of_interface>  loopback        lo
    ovs-if-br-ex        <UUID_of_interface>  ovs-interface   --
    
  • During the RHOCP cluster upgrade, after node reboot, the node turns into the NotReady state.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)

    • 4.14+
  • 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