Red Hat Bugzilla – Bug 998411
[vdsm] guest alignment scan fails on host due to lvchange (deactivate lv) failure
Last modified: 2016-02-10 12:34:56 EST
Created attachment 787953 [details]
Description of problem:
related to this new 3.3 feature:
I tried to scan alignment a disk that has been partitioned.
This action is failing every time because vdsm is unable to deactivate the volume
Version-Release number of selected component (if applicable):
Steps to Reproduce:
On a block pool:
- create a vm and run it with OS and guest-agent installed.
- add a new 3 GB disk and plug it to the vm.
- create a partition on the disk that starts from the 2048 sector with fdisk (need to change the units to sectors)
- scan alignment (on UI - under disk sub-tab, under VMs main tab - right click on the disk - 'scan alignment'
vdsm fails in lvchange (deactivate lv):
Thread-36873::ERROR::2013-08-19 11:19:21,416::task::850::TaskManager.Task::(_setError) Task=`d91d258d-e546-4af0-ae20-b5910d581072`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 857, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/logUtils.py", line 45, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/storage/hsm.py", line 3270, in teardownImage
File "/usr/share/vdsm/storage/blockSD.py", line 998, in deactivateImage
File "/usr/share/vdsm/storage/lvm.py", line 1129, in deactivateLVs
_setLVAvailability(vgName, toDeactivate, "n")
File "/usr/share/vdsm/storage/lvm.py", line 784, in _setLVAvailability
CannotDeactivateLogicalVolume: Cannot deactivate Logical Volume: ('General Storage Exception: ("5  [\' device-mapper: remove ioctl on failed: Device or resource busy\
and vdsm is unable to scan guest alignment
This volume is activated so I'm not sure about the expected results.
is13. guest alignment succeeds.
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
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.