'rook-ceph-detect-version-XXX' pod is stuck in 'Pending' state during the automatic upgrade from OCS 4.2.1 to 4.2.2.

Solution Verified - Updated -

Issue

  • rook-ceph-detect-version-XXX pod is stuck in Pending state during the automatic upgrade from OCS 4.2.1 to 4.2.2 and the upgrade doesn't starts.

  • rook-ceph-detect-version-XXX, csi-cephfsplugin-provisioner-XXX, csi-rbdplugin-provisioner-XXX, noobaa-core-0 and rook-ceph-drain-canary pods are stuck in Pending state after autmatic upgrade is triggered for OCS.

  • OCS pods are stuck in Pending state, with messages in Events:

    Events:
      Type     Reason            Age        From               Message
      ----     ------            ----       ----               -------
      Warning  FailedScheduling  <unknown>  default-scheduler  0/15 nodes are available: 12 node(s) didn't match node selector, 3 node(s) had taints that the pod didn't tolerate.
    

Environment

  • Red Hat OpenShift Container Storage 4.2

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