Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 907167

Summary: engine: if we power off a vm with multiple disks during live storage migration the disks will remain locked (after snapshot is created)
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: ovirt-engineAssignee: Daniel Erez <derez>
Status: CLOSED CURRENTRELEASE QA Contact: Dafna Ron <dron>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, amureini, dyasny, iheim, lpeer, Rhev-m-bugs, scohen, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: SF8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Dafna Ron 2013-02-03 14:48:40 UTC 
Created attachment 692356 [details]
logs

Description of problem:

I powered off a vm during live storage migration (after the snapshot has been created and the actual move has started) and the vm's disks got stuck in image locked. 
this only happened with vm with multiple disks.

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

sf5

How reproducible:

100%

Steps to Reproduce:
1. create a vm with several disks
2. run the vm and start a live storage migration for all the disks 
3. after the snapshot is completed and the disks are starting to migrate power off the vm
  
Actual results:


Expected results:


Additional info: full logs and screen shot 

please also see bug: https://bugzilla.redhat.com/show_bug.cgi?id=896445

this behaviour happened when the vm was creating the snapshot. 
now we see this behaviour after the snapshot is completed. 

***this is not a refresh UI issue***

even after the tasks are cleared from spm the images remain locked: 


[root@gold-vdsc ~]# vdsClient -s 0 getAllTasksInfo
dd0cb9d2-6a33-4466-a7d0-e7c0b9890fe9 :
	verb = cloneImageStructure
	id = dd0cb9d2-6a33-4466-a7d0-e7c0b9890fe9
1263d57a-226d-426e-82fe-e510432218c7 :
	verb = cloneImageStructure
	id = 1263d57a-226d-426e-82fe-e510432218c7
9ec1b47c-9b89-43b4-a5ff-65ec7b272e93 :
	verb = cloneImageStructure
	id = 9ec1b47c-9b89-43b4-a5ff-65ec7b272e93

2013-02-03 16:34:46,552 INFO  [org.ovirt.engine.core.bll.AsyncTaskManager] (QuartzScheduler_Worker-41) Cleared all tasks of pool b08d859c-f654-4976-8c7c-e102d4c252fb.

[root@gold-vdsc ~]# vdsClient -s 0 getAllTasksInfo

[root@gold-vdsc ~]# 


the images are locked: 

engine=# SELECT imagestatus,image_guid from images;
 imagestatus |              image_guid              
-------------+--------------------------------------
           0 | 00000000-0000-0000-0000-000000000000
           1 | b07bd93c-3302-44e9-bb77-ac49ac5e4372
           1 | f352f70d-a807-4dd6-afd7-8f1e8f1283c7
           1 | bbd2e904-00c9-40cb-8ecb-5f62c611116d
           1 | bf835dd8-e93d-4404-88c7-4b649f90930b
           1 | 8d86e6df-302f-4cb9-9b2c-d84505362a56
           2 | a7dc6501-31bf-4d72-8d22-7562e8065867
           2 | bf563b5c-675e-41b4-96dc-207b6d95df4b
           2 | 0b1d980c-1da9-42c2-bff3-645e3b23f3fd
Comment 1 Dafna Ron 2013-03-04 16:33:50 UTC 
verified on sf9
Comment 2 Itamar Heim 2013-06-11 09:32:24 UTC 
3.2 has been released
Comment 3 Itamar Heim 2013-06-11 09:33:15 UTC 
3.2 has been released
Comment 4 Itamar Heim 2013-06-11 09:49:04 UTC 
3.2 has been released