Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 512151[details]
vdsm log
Description of problem:
teardownVolume should work even when is no connection to storage domain. In the result when it fail there is no way to remove vm.
Version-Release number of selected component (if applicable):
RHEVM:ic129
vdsm:vdsm-4.9-79.el6.x86_64
libvirt:libvirt-0.9.2-1.el6.x86_64
Setup:
Two ISCSI Data Domains
At least one vm with disk
How reproducible:
1)Block connection to all ISCSI Storages for more than 5 min
2)Unblock connection
3)Activate all storages
4)Try remove vm
Actual results:
Thread-386::INFO::2011-07-11 09:13:41,066::dispatcher::94::Storage.Dispatcher.Protect::(run) Run and protect: teardownVolume, args: ( sdUUID=197e4a67-6b85-4033-b486-e1319e2ea411 spUUID=5f3919f2-6777-43fb-af1e-c11d28359766 imgUUID=89861256-012e-4e68-ada0-1476ef1d773e volUUID=8b80496f-11e2-4a73-975c-b40059f8b2c8)
Thread-386::DEBUG::2011-07-11 09:13:41,067::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: moving from state init -> state preparing
Thread-386::DEBUG::2011-07-11 09:13:41,067::resourceManager::154::ResourceManager.Request::(__init__) ResName=`Storage.197e4a67-6b85-4033-b486-e1319e2ea411`ReqID=`288e79e9-656f-44f5-bd1b-b1a87a03a59b`::Request was made in '/usr/share/vdsm/storage/hsm.py' line '1701' at 'public_teardownVolume'
Thread-386::DEBUG::2011-07-11 09:13:41,068::resourceManager::467::ResourceManager::(registerResource) Trying to register resource 'Storage.197e4a67-6b85-4033-b486-e1319e2ea411' for lock type 'shared'
Thread-386::DEBUG::2011-07-11 09:13:41,068::resourceManager::508::ResourceManager::(registerResource) Resource 'Storage.197e4a67-6b85-4033-b486-e1319e2ea411' is free. Now locking as 'shared' (1 active user)
Thread-386::DEBUG::2011-07-11 09:13:41,068::resourceManager::191::ResourceManager.Request::(grant) ResName=`Storage.197e4a67-6b85-4033-b486-e1319e2ea411`ReqID=`288e79e9-656f-44f5-bd1b-b1a87a03a59b`::Granted request
Thread-386::DEBUG::2011-07-11 09:13:41,069::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: _resourcesAcquired: Storage.197e4a67-6b85-4033-b486-e1319e2ea411 (shared)
Thread-386::DEBUG::2011-07-11 09:13:41,069::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: ref 1 aborting False
Thread-386::DEBUG::2011-07-11 09:13:41,069::lvm::412::OperationMutex::(_reloadvgs) Operation 'lvm reload operation' got the operation mutex
Thread-386::DEBUG::2011-07-11 09:13:41,070::lvm::359::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm vgs --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 filter = [ \\"a%/dev/mapper/1987653345|/dev/mapper/19876544%\\", \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --noheadings --units b --nosuffix --separator | -o uuid,name,attr,size,free,extent_size,extent_count,free_count,tags 197e4a67-6b85-4033-b486-e1319e2ea411' (cwd None)
Thread-386::DEBUG::2011-07-11 09:13:41,217::lvm::359::Storage.Misc.excCmd::(cmd) FAILED: <err> = ' /dev/mapper/19876544: read failed after 0 of 4096 at 53687025664: Input/output error\n /dev/mapper/19876544: read failed after 0 of 4096 at 53687083008: Input/output error\n /dev/mapper/19876544: read failed after 0 of 4096 at 0: Input/output error\n /dev/mapper/19876544: read failed after 0 of 4096 at 4096: Input/output error\n Volume group "197e4a67-6b85-4033-b486-e1319e2ea411" not found\n'; <rc> = 5
Thread-386::WARNING::2011-07-11 09:13:41,221::lvm::416::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 [] [' /dev/mapper/19876544: read failed after 0 of 4096 at 53687025664: Input/output error', ' /dev/mapper/19876544: read failed after 0 of 4096 at 53687083008: Input/output error', ' /dev/mapper/19876544: read failed after 0 of 4096 at 0: Input/output error', ' /dev/mapper/19876544: read failed after 0 of 4096 at 4096: Input/output error', ' Volume group "197e4a67-6b85-4033-b486-e1319e2ea411" not found']
Thread-386::DEBUG::2011-07-11 09:13:41,222::lvm::439::OperationMutex::(_reloadvgs) Operation 'lvm reload operation' released the operation mutex
Thread-386::ERROR::2011-07-11 09:13:41,222::task::865::TaskManager.Task::(_setError) Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 873, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/hsm.py", line 1702, in public_teardownVolume
volclass = SDF.produce(sdUUID).getVolumeClass()
File "/usr/share/vdsm/storage/sdf.py", line 30, in produce
newSD = cls.__sdc.lookup(sdUUID)
File "/usr/share/vdsm/storage/sdc.py", line 83, in lookup
dom = self._findDomain(sdUUID)
File "/usr/share/vdsm/storage/sdc.py", line 107, in _findDomain
raise se.StorageDomainDoesNotExist(sdUUID)
StorageDomainDoesNotExist: Storage domain does not exist: ('197e4a67-6b85-4033-b486-e1319e2ea411',)
Thread-386::DEBUG::2011-07-11 09:13:41,223::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: Task._run: 18185c35-693f-40d0-b3fe-66a98651cfcf ('197e4a67-6b85-4033-b486-e1319e2ea411', '5f3919f2-6777-43fb-af1e-c11d28359766', '89861256-012e-4e68-ada0-1476ef1d773e', '8b80496f-11e2-4a73-975c-b40059f8b2c8') {} failed - stopping task
Expected results:
After activation should be connected to all storages,and vm should be remove
Additional info:
1)The same scenario works under older versions of vdsm.
2)All storage negative tests uses very similar scenario and because this issue its a testblocker for us.
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/RHEA-2011-1782.html
Created attachment 512151 [details] vdsm log Description of problem: teardownVolume should work even when is no connection to storage domain. In the result when it fail there is no way to remove vm. Version-Release number of selected component (if applicable): RHEVM:ic129 vdsm:vdsm-4.9-79.el6.x86_64 libvirt:libvirt-0.9.2-1.el6.x86_64 Setup: Two ISCSI Data Domains At least one vm with disk How reproducible: 1)Block connection to all ISCSI Storages for more than 5 min 2)Unblock connection 3)Activate all storages 4)Try remove vm Actual results: Thread-386::INFO::2011-07-11 09:13:41,066::dispatcher::94::Storage.Dispatcher.Protect::(run) Run and protect: teardownVolume, args: ( sdUUID=197e4a67-6b85-4033-b486-e1319e2ea411 spUUID=5f3919f2-6777-43fb-af1e-c11d28359766 imgUUID=89861256-012e-4e68-ada0-1476ef1d773e volUUID=8b80496f-11e2-4a73-975c-b40059f8b2c8) Thread-386::DEBUG::2011-07-11 09:13:41,067::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: moving from state init -> state preparing Thread-386::DEBUG::2011-07-11 09:13:41,067::resourceManager::154::ResourceManager.Request::(__init__) ResName=`Storage.197e4a67-6b85-4033-b486-e1319e2ea411`ReqID=`288e79e9-656f-44f5-bd1b-b1a87a03a59b`::Request was made in '/usr/share/vdsm/storage/hsm.py' line '1701' at 'public_teardownVolume' Thread-386::DEBUG::2011-07-11 09:13:41,068::resourceManager::467::ResourceManager::(registerResource) Trying to register resource 'Storage.197e4a67-6b85-4033-b486-e1319e2ea411' for lock type 'shared' Thread-386::DEBUG::2011-07-11 09:13:41,068::resourceManager::508::ResourceManager::(registerResource) Resource 'Storage.197e4a67-6b85-4033-b486-e1319e2ea411' is free. Now locking as 'shared' (1 active user) Thread-386::DEBUG::2011-07-11 09:13:41,068::resourceManager::191::ResourceManager.Request::(grant) ResName=`Storage.197e4a67-6b85-4033-b486-e1319e2ea411`ReqID=`288e79e9-656f-44f5-bd1b-b1a87a03a59b`::Granted request Thread-386::DEBUG::2011-07-11 09:13:41,069::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: _resourcesAcquired: Storage.197e4a67-6b85-4033-b486-e1319e2ea411 (shared) Thread-386::DEBUG::2011-07-11 09:13:41,069::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: ref 1 aborting False Thread-386::DEBUG::2011-07-11 09:13:41,069::lvm::412::OperationMutex::(_reloadvgs) Operation 'lvm reload operation' got the operation mutex Thread-386::DEBUG::2011-07-11 09:13:41,070::lvm::359::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm vgs --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 filter = [ \\"a%/dev/mapper/1987653345|/dev/mapper/19876544%\\", \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --noheadings --units b --nosuffix --separator | -o uuid,name,attr,size,free,extent_size,extent_count,free_count,tags 197e4a67-6b85-4033-b486-e1319e2ea411' (cwd None) Thread-386::DEBUG::2011-07-11 09:13:41,217::lvm::359::Storage.Misc.excCmd::(cmd) FAILED: <err> = ' /dev/mapper/19876544: read failed after 0 of 4096 at 53687025664: Input/output error\n /dev/mapper/19876544: read failed after 0 of 4096 at 53687083008: Input/output error\n /dev/mapper/19876544: read failed after 0 of 4096 at 0: Input/output error\n /dev/mapper/19876544: read failed after 0 of 4096 at 4096: Input/output error\n Volume group "197e4a67-6b85-4033-b486-e1319e2ea411" not found\n'; <rc> = 5 Thread-386::WARNING::2011-07-11 09:13:41,221::lvm::416::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 [] [' /dev/mapper/19876544: read failed after 0 of 4096 at 53687025664: Input/output error', ' /dev/mapper/19876544: read failed after 0 of 4096 at 53687083008: Input/output error', ' /dev/mapper/19876544: read failed after 0 of 4096 at 0: Input/output error', ' /dev/mapper/19876544: read failed after 0 of 4096 at 4096: Input/output error', ' Volume group "197e4a67-6b85-4033-b486-e1319e2ea411" not found'] Thread-386::DEBUG::2011-07-11 09:13:41,222::lvm::439::OperationMutex::(_reloadvgs) Operation 'lvm reload operation' released the operation mutex Thread-386::ERROR::2011-07-11 09:13:41,222::task::865::TaskManager.Task::(_setError) Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 873, in _run return fn(*args, **kargs) File "/usr/share/vdsm/storage/hsm.py", line 1702, in public_teardownVolume volclass = SDF.produce(sdUUID).getVolumeClass() File "/usr/share/vdsm/storage/sdf.py", line 30, in produce newSD = cls.__sdc.lookup(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 83, in lookup dom = self._findDomain(sdUUID) File "/usr/share/vdsm/storage/sdc.py", line 107, in _findDomain raise se.StorageDomainDoesNotExist(sdUUID) StorageDomainDoesNotExist: Storage domain does not exist: ('197e4a67-6b85-4033-b486-e1319e2ea411',) Thread-386::DEBUG::2011-07-11 09:13:41,223::task::492::TaskManager.Task::(_debug) Task 18185c35-693f-40d0-b3fe-66a98651cfcf: Task._run: 18185c35-693f-40d0-b3fe-66a98651cfcf ('197e4a67-6b85-4033-b486-e1319e2ea411', '5f3919f2-6777-43fb-af1e-c11d28359766', '89861256-012e-4e68-ada0-1476ef1d773e', '8b80496f-11e2-4a73-975c-b40059f8b2c8') {} failed - stopping task Expected results: After activation should be connected to all storages,and vm should be remove Additional info: 1)The same scenario works under older versions of vdsm. 2)All storage negative tests uses very similar scenario and because this issue its a testblocker for us.