Bug 989966

Summary: VM's disk remains locked after LSM failed
Product: Red Hat Enterprise Virtualization Manager Reporter: Aharon Canan <acanan>
Component: ovirt-engineAssignee: Nobody's working on this, feel free to take it <nobody>
Status: CLOSED DUPLICATE QA Contact: Aharon Canan <acanan>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, amureini, iheim, lpeer, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.0   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-30 14:44:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
logs none

Description Aharon Canan 2013-07-30 08:29:51 UTC
Created attachment 780452 [details]
logs

Description of problem:
after running LSM which failed, VM's disk remains locked and we can't start the VM.

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

How reproducible:

Steps to Reproduce:
1. 2 hosts with 2 storage domain, running VM (thin disk - already migrate few times)
2. LSM the VM's disk
3. poweroff the VM

Actual results:
LSM failed, disk remains locked

Expected results:
VM's disk should be active after LSM fails

Additional info:

Comment 2 Sergey Gotliv 2013-07-30 14:59:19 UTC
*** Bug 989955 has been marked as a duplicate of this bug. ***

Comment 3 Aharon Canan 2013-07-30 15:07:08 UTC
I faced this issue on 3.2.2 
I think we should fix in 3.2.z as well

I will add "?" in 970889 for 3.2.z