Pod goes in pending state and reports orphaned pod found and Volume ID already exists in OpenShift 4

Solution Verified - Updated -

Issue

  • A pod is not able to bind with PVC and in Pending or ContainerCreating status.
  • There is an 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
    
  • Below mentioned repetitive errors are observed in kubelet logs:

    E0101 00:00:00.000000    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.
    E0101 00:00:00.000000    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.
    E0101 00:00:00.000000    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.
    

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