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

Bug 1525529

Summary: Powering down a VM while it's migrating results in the VM being stuck
Product: [oVirt] ovirt-engine Reporter: Logan Kuhn <logank>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.7.6CC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-14 05:31:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
VDSM log for the host the VM originated on
none
Engine log during the time it was in the stuck state none

Description Logan Kuhn 2017-12-13 14:04:25 UTC
Created attachment 1367396 [details]
VDSM log for the host the VM originated on

Description of problem:
If I start a VM migrating to another host, either as part of the host going into maintenance or a manual migration and then do a shutdown -h while the VM is running, but before the migration completes, the VM is stuck in migrating status.

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


How reproducible:
100%

Steps to Reproduce:
1. Migrate a VM to another host
2. Shutdown the VM from within the guest OS
3. VM is now stuck in migrating status without any ability to change it without modifying the database.

Actual results:
VM is stuck in migrating status

Expected results:
VM is in down status

Additional info:

Comment 1 Logan Kuhn 2017-12-13 14:04:57 UTC
Created attachment 1367398 [details]
Engine log during the time it was in the stuck state

Comment 2 Michal Skrivanek 2017-12-14 05:31:48 UTC
This has been fixed recently

*** This bug has been marked as a duplicate of bug 1505399 ***