Adding new OpenShift Container Platform 4 - Node is failing with "failed to initialize top level QOS containers: root container [kubepods] doesn't exist"

Solution Verified - Updated -

Issue

  • During UPI nodes provisioning, two system:serviceaccount:openshift-machine-config-operator:node-bootstrapper are being issued for the same node, causing the second not being approved and leaving the node in unusable stat.
  • Newly added Node is pending CSR approval for system:serviceaccount:openshift-machine-config-operator:node-bootstrapper showing Failed to start ContainerManager" err="failed to initialize top level QOS containers: root container [kubepods] doesn't exist error in the kubelet logs.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.13
    • 4.14
    • 4.15
  • cgroup v2

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