Bug 989966 - VM's disk remains locked after LSM failed
Summary: VM's disk remains locked after LSM failed
Keywords:
Status: CLOSED DUPLICATE of bug 970889
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: x86_64
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.3.0
Assignee: Nobody's working on this, feel free to take it
QA Contact: Aharon Canan
URL:
Whiteboard: storage
: 989955 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-30 08:29 UTC by Aharon Canan
Modified: 2016-02-10 18:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-30 14:44:04 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
logs (1.60 MB, application/x-gzip)
2013-07-30 08:29 UTC, Aharon Canan 		no flags Details
View All

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
Note You need to log in before you can comment on or make changes to this bug.