Bug 918469 - vdsm: DeleteImage is failing with postzero = true on block devices
Summary: vdsm: DeleteImage is failing with postzero = true on block devices
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.2.0
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.2.0
Assignee: Federico Simoncelli
QA Contact: Elad
URL:
Whiteboard: storage
: 918652 (view as bug list)
Depends On:
Blocks: 922807
TreeView+ depends on / blocked
 
Reported: 2013-03-06 10:08 UTC by Elad
Modified: 2016-02-10 17:39 UTC (History)
9 users (show)

Fixed In Version: vdsm-4.10.2-11.0.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Storage
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Elad 2013-03-06 10:08:33 UTC
Description of problem:

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Have 1 VM
2. Add a disk to the VM with 'wipe after delete'
3. Remove the disk
  
Actual results:
The deletion of the disk fails 

Expected results:
DEletion of the disk should work

Additional info:


Thread-97254::DEBUG::2013-03-06 08:40:50,545::lvm::447::OperationMutex::(_reloadlvs) Operation 'lvm reload operation' released the operation mutex
c37b977a-b45c-4324-9ff1-780b3113cccb::DEBUG::2013-03-06 08:40:50,546::lvm::498::OperationMutex::(_invalidatelvs) Operation 'lvm invalidate operation' got the operation mutex
66682964-5334-4e4d-af80-b95f5e4a9b14::DEBUG::2013-03-06 08:40:50,548::lvm::498::OperationMutex::(_invalidatelvs) Got the operational mutex
c37b977a-b45c-4324-9ff1-780b3113cccb::DEBUG::2013-03-06 08:40:50,548::blockSD::224::Storage.BlockSD::(zeroImgVolumes) Ignoring failed permission change: General Storage Exception
: ('5 [] [\'  Logical volume "77927e81-5ed1-4fc5-8b21-ffc5a2133768" is already writable\']\nc9a85789-053b-4781-8c20-2f30adb1c995/{\'77927e81-5ed1-4fc5-8b21-ffc5a2133768\': ImgsPa
r(imgs=(\'dfbaaf32-e963-4aa8-a7bb-c712bc6812b9\',), parent=\'00000000-0000-0000-0000-000000000000\')}',)
66682964-5334-4e4d-af80-b95f5e4a9b14::DEBUG::2013-03-06 08:40:50,550::lvm::510::OperationMutex::(_invalidatelvs) Operation 'lvm invalidate operation' released the operation mutex
c37b977a-b45c-4324-9ff1-780b3113cccb::ERROR::2013-03-06 08:40:50,551::task::833::TaskManager.Task::(_setError) Task=`c37b977a-b45c-4324-9ff1-780b3113cccb`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 840, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/storage/task.py", line 307, in run
    return self.cmd(*self.argslist, **self.argsdict)
  File "/usr/share/vdsm/storage/blockSD.py", line 963, in zeroImage
    zeroImgVolumes(sdUUID, imgUUID, toZero)
  File "/usr/share/vdsm/storage/blockSD.py", line 229, in zeroImgVolumes
    proc = _zeroVolume(sdUUID, volUUID)
  File "/usr/share/vdsm/storage/blockSD.py", line 191, in _zeroVolume
    cmd = tuple(constants.CMD_LOWPRIO)

Comment 1 Eduardo Warszawski 2013-03-06 10:22:59 UTC
LOWPRIO was removed from constanst in:

I5abd61c03ce907ea94761f0209a4626669051eb1

Bad merge.

Comment 3 Federico Simoncelli 2013-03-06 15:11:07 UTC
This is not limited to downstream, the exact same problem affected upstream and the fix was submitted as:

commit 5ffc0d64d7abdd4ad3dd36b2fd375134bf2ff918
Author: Dan Kenigsberg <danken>
Date:   Tue Feb 19 11:08:09 2013 +0200

    Drop remnant CMD_LOWPRIO
    
    Commit aba12f81be549 attempted to drop all CMD_LOWPRIO, but due to a sloppy
    rebase, one reference remains.

http://gerrit.ovirt.org/12184

Comment 6 Elad 2013-03-13 17:59:03 UTC
Tested on SF10.

Comment 7 Ayal Baron 2013-03-25 08:53:20 UTC
*** Bug 918652 has been marked as a duplicate of this bug. ***

Comment 8 Itamar Heim 2013-06-11 08:37:40 UTC
3.2 has been released

Comment 9 Itamar Heim 2013-06-11 08:37:51 UTC
3.2 has been released

Comment 10 Itamar Heim 2013-06-11 08:37:52 UTC
3.2 has been released

Comment 11 Itamar Heim 2013-06-11 08:45:48 UTC
3.2 has been released


Note You need to log in before you can comment on or make changes to this bug.