Network cluster operator stuck in updating state during cluster upgrade from 4.15 to 4.16 in RHOCP 4

Solution Verified - Updated -

Issue

  • Network cluster operator stuck in updating state during cluster upgrade from 4.15 to 4.16:

    $ oc get co network
    network                         4.15.42   True        True          False      2y133d   DaemonSet "/openshift-network-diagnostics/network-check-target" is not available (awaiting 5 nodes)
    DaemonSet "/openshift-kube-proxy/openshift-kube-proxy" is not available (awaiting 3 nodes)
    DaemonSet "/openshift-multus/multus" is not available (awaiting 3 nodes)
    DaemonSet "/openshift-multus/multus-additional-cni-plugins" is not available (awaiting 3 nodes)
    DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 5 nodes)
    Deployment "/openshift-multus/multus-admission-controller" is not available (awaiting 1 nodes)
    Deployment "/openshift-network-diagnostics/network-check-source" is not available (awaiting 1 nodes)
    

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