Pods stuck in Terminating state on node lost

Solution Verified - Updated -

Issue

  • After all nodes are gone offline and nodes reports NotReady status, all pods present in that node are going into Terminating state so that the new replicas are not scheduled on the other available nodes.
  • The VM pod is stuck in terminating state once the underlying node is reporting NotReady.

Environment

  • Red Hat OpenShift Container Platform
    • 4.16
  • Red Hat OpenShift Virtulization

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