Bug 1066413

Summary: vmHotplugDisk failed with "VolumeError: Bad volume specification"
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Nir Soffer <nsoffer>
Status: CLOSED ERRATA QA Contact: Aharon Canan <acanan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acanan, adahms, amureini, bazulay, ebenahar, eedri, gklein, iheim, kjachim, lpeer, nsoffer, obasan, sbonazzo, scohen, sgrinber, yeylon, ykaul, zdover
Target Milestone: ---Keywords: ZStream
Target Release: 3.3.3Flags: amureini: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: vdsm-4.13.2-0.14.el6ev Doc Type: Bug Fix
Doc Text:
Previously, the vmHotplugDisk action would fail with the error "VolumeError: Bad volume specification". This was caused by a multipath race condition that would result in a situation in which multipath was not given enough time to create the /dev/mapper entry for the LUN on the host on which the virtual machine was running. Now, the logic used to scan for device visibility has been revised so that multipath has the time required for creating the /dev/mapper entry for the LUN on the host on which the virtual machine is running.
Story Points: ---
Clone Of: 1044068 Environment:
Last Closed: 2014-05-27 08:57:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1044068    
Bug Blocks:    

Comment 1 Allon Mureinik 2014-02-18 11:37:53 UTC
Nir, please handle the backporting.

Comment 2 Nir Soffer 2014-03-02 13:40:21 UTC
Remove upstream patches.

Comment 4 Aharon Canan 2014-05-07 14:48:44 UTC
Verified using is36

Verification steps:
1. create 2 unattached LUNs and a VM
2. attach one of the LUNs when the VM is down
3. start VM and install OS
4. attach another LUN and check VM can access it.

Comment 6 errata-xmlrpc 2014-05-27 08:57:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0548.html