After deleting the iscsi storage, ISCSIADM operations got stuck and wouldn't end.This caused connectStoragePool/GetDeviceList to fail on timeout. This has been fixed by removing forceIscsiScan() as iscsiadm already does that when refreshing sessions, and rewriting the logic with a simpler implementation.
Description of problem:
After deletion of iscsi storage (not from engine) - ISCSIADM operation got stuck and won't end.
this causes that connectStoragePool/GetDeviceList fail on timeout
Version-Release number of selected component (if applicable):
si17
vdsm-xmlrpc-4.10.2-19.0.el6ev.noarch
vdsm-cli-4.10.2-19.0.el6ev.noarch
vdsm-4.10.2-19.0.el6ev.x86_64
vdsm-python-4.10.2-19.0.el6ev.x86_64
rhevm-3.2.0-10.26.rc.el6ev.noarch
Steps to Reproduce:
1. iscsi pool - two hosts, one domain, pool is up
2. delete the iscsi storage
Actual results:
1. connectStoragePool always fail on timeout
2. getDeviceList doesn't work
3. lock queue on vdsm grows indefinitely.
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-0040.html