Update to OpenShift Container Platform 4.11 stuck because openshift-dns-operator pod is in CrashLoopBackOff state

Solution Verified - Updated -


  • Today, the update from 4.10.20 to 4.11.16 got stuck because of an blocked network clusteroperator. Checking further we found the below message reported by the network co and also openshift-dns-operator is reporting CrashLoopBackOff state with failed to create operator: failed to create operator manager: Get \"\": dial tcp i/o timeout.

    message: DaemonSet "/openshift-network-diagnostics/network-check-target" is not
    available (awaiting 1 nodes)


  • Red Hat OpenShift Container Platform (RHOCP) 4.11

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