Network operator stuck in progressing status due to "DaemonSet "/openshift-ovn-kubernetes/ovnkube-node" is not available (awaiting 1 nodes)"

Solution Verified - Updated -

Issue

  • Network operator stuck in progressing status due to DaemonSet /openshift-ovn-kubernetes/ovnkube-node is not available (awaiting 1 nodes)

    $ oc get events -n openshift-ovn-kubernetes 

Warning  Unhealthy  pod/ovnkube-node-xxx  (combined from similar events): Readiness probe errored: rpc error: code = Unknown desc = command error: time="2023-04-28T13:36:03Z" level=error msg="exec failed: unable to start container process: error adding pid 3281820 to cgroups: failed to write 3281820: open /sys/fs/cgroup/systemd/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod946c970a_908d_4228_9781_76206184dc7f.slice/crio-065417eb7a0c1481c526cd96c44f3d1a4221e034965b50b13c3ea4bdc647795a.scope/cgroup.procs: no such file or directory"

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