Pod goes in pending state and reports orphaned pod "xxxx-xxxx-xxxx" found, but volume paths are still present on disk

Solution Verified - Updated -

Issue

Pod is not able to bind with PVC and below mentioned repetitive errors are observed in kubelet logs:

E1022 02:07:13.655775   2862 kubelet_volumes.go:154] `orphaned pod "xxxxxx-xxxx-xxxx-xxxx" found, but volume paths are still present on disk` : There were a total of 1 errors similar to this. Turn up verbosity to see them.
E1022 02:07::15.654964    2862 kubelet_volumes.go:154] orphaned pod "xxxxxx-xxxx-xxxx-xxxx" found, but volume paths are still present on disk : There were a total of 1 errors similar to this. Turn up verbosity to see them.
E1022 02:07:17.655510    2862 kubelet_volumes.go:154] orphaned pod "xxxxxx-xxxx-xxxx-xxxx" found, but volume paths are still present on disk : There were a total of 1 errors similar to this. Turn up verbosity to see them.

Below is the event reported:

MountVolume.MountDevice failed for volume "pvc-xxxxx-xxxxx-xxxx-xxx" : rpc error: code = Aborted desc = an operation with the given `Volume ID aaaaaa-aaa-aaaa-aaaaa already exists`

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.x

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