OpenshiftSDN containers stuck in unready status due timedrift events in RHOCP 4

Solution Unverified - Updated -

Issue

  • Why is the sdn container stuck in unready status after a time drift event in the OCP node?

    $ oc get pod -n openshift-sdn -owide
NAME        READY       STATUS    RESTARTS   AGE   IP         NODE     
sdn-xxx     1/2 <--     Running   xx         xxm   x.x.x.x   <node-name>

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