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.

Description of problem:

if you shut down a vm while storage domain is not accessible we will not release the lock on the vm and if we try to move it to a different domain the vm will be stuck in image locked forever. 

I used iscsi storage domain consisting of 2 luns from different storage servers. I blocked only one of the storage servers from the host using iptables. 

also, this does not happen in upstream.  

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

vdsm-4.9-112.6.el6_2.x86_64

How reproducible:

100%

Steps to Reproduce:
1. create DC with two SD (my master domain consisted of luns from 2 different storage servers).  
2. run vm and block connectivity to one of the storage servers from the host using iptables
3. when vm pauses stop it and restore SD connectivity
4. move vm to a different domain. 
  
Actual results:

vm will be stuck in image lock forever

Expected results:

we should be able to move vm

Additional info: full log

Created attachment 560473 [details]
log

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

si13. fixed. This bug was open on 3.0. There is no move VM now. VM is not entering image lock status while moving it's disks. Reproduced according to instructions above. VM with 2 disks (each disk in different SD). Blocked connection to on of the SD. Vm entered to paused state. Stopped VM and restored connection to SD. After connection was restored successfully moved VMs disk to another storage domain.