Pods stuck in Terminating state on node lost
Issue
- After all nodes are gone
offlineand nodes reports NotReady status, all pods present in that node are going intoTerminating stateso 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.