VMDK OSDs failing with devicePath is empty

Solution Verified - Updated -

Issue

  • Issue is with the Monitors and OSDs failing with the following event:
"MapVolume.WaitForAttach failed for volume \"pvc-xxxxxxx-xxxx-xxxx-951d-b0b175fbd47c\" : WaitForAttach failed for VMDK \"[EXAMPLE] kubevols/openshift-xxxxx-dynamic-pvc-xxxxxxxx-xxxx-xxxx-951d-b0b175fbd47c.vmdk\": devicePath is empty
  • Mons/osds in the openshift-storage namespace stuck in CLBO / CrashLoopBackOff status

Environment

  • Red Hat OpenShift Container Storage
    • 4.6

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