Red Hat Bugzilla – Bug 982004
[vdsm] vdsm fails to rollback tasks after a failure in create snapshot (with several disks)
Last modified: 2016-02-10 15:12:28 EST
Created attachment 770081 [details]
Description of problem:
After a failure in create snapshot to vm with several disks, vdsm fails to roll-back the unfinished tasks:
Traceback (most recent call last):
File "/usr/share/vdsm/storage/volume.py", line 348, in parentVolumeRollback
File "/usr/share/vdsm/storage/blockVolume.py", line 381, in teardown
File "/usr/share/vdsm/storage/resourceManager.py", line 630, in releaseResource
"registered" % (namespace, name))
ValueError: Resource '283c1cc8-1d44-47f6-970d-5df9f4b4dedf_lvmActivationNS.a5bb5e48-57c8-4d5a-a077-0ffa7e478dbe' is not currently registered
Version-Release number of selected component (if applicable):
Steps to Reproduce: on a block pool:
1. create vm with 3 disks
2. create snapshot to the vm
3. while snapshot creation tasks are running, restart vdsm service
after vdsm comes up, it fails to roll-back the unfinished create snapshot tasks
vdsm should be able to perform roll-back after a failure in create snapshot
In parentVolumeRollback a pvol.prepare() call is missing:
def parentVolumeRollback(cls, taskObj, sdUUID, pimgUUID, pvolUUID):
cls.log.info("parentVolumeRollback: sdUUID=%s pimgUUID=%s"
" pvolUUID=%s" % (sdUUID, pimgUUID, pvolUUID))
if pvolUUID != BLANK_UUID and pimgUUID != BLANK_UUID:
pvol = sdCache.produce(sdUUID).produceVolume(pimgUUID,
if not pvol.isShared() and not pvol.recheckIfLeaf():
cls.log.error("Unexpected error", exc_info=True)
VDSM performs roll-back after the failure, but the deleteImage task gets stuck.
Adding this bug as depends on bug 1019394.
Marking as verified, the roll-back is being done by vdsm.
Checked on RHEVM3.3 - is18.1
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.