Why all storage operations are failing in RHV after cloning direct LUN

Solution In Progress - Updated -

Issue

  • Direct LUNs which were configured as LVM within VM were cloned and mapped to the hosts in the RHV environment. After that all storage operations like the creation of disk, template, copying, and moving of disk, etc. are stuck in RHV.
  • All the LVM commands spawned by the vdsm is failing with the error below where vg1 is the LVM created within the VM.
] err=['  WARNING: Not using device /dev/mapper/360014056acce71a83d84a45adfb58eba for PV SEf62H-Be2m-n82e-CZ8F-61oS-Lsjd-EnZYCA.', '  WARNING: PV SEf62H-Be2m-n82e-CZ8F-61oS-Lsjd-EnZYCA prefers device /dev/mapper/360014052ab8263b51d84a9b9e4fe9107 because device was seen first.', '  Recovery of volume group "vg1" failed.', '  Cannot process volume group vg1']

Environment

  • Red Hat Virtualization 4.3.

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