Application pods stuck in terminating state in RHOCP4

Solution Verified - Updated -

Issue

  • Most of the stateful set pods are in CrashLoopBackOff state.

  • Application pods are in terminating state with the following logs:

    pod "7f5e86fb-bae0-47d5-a3b4-000382096a13" (UID: "ea23394f-db52-11e8-ad88-6c92bf6f20b2") with: remove 
/var/lib/kubelet/pods/7f5e86fb-bae0-47d5-a3b4-000382096a13/volumes/kubernetes.io~csi/: directory not empty

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