Bug 1058764 - Not possible to power off VM that failed migration.
Summary: Not possible to power off VM that failed migration.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.3.1
Assignee: Arik
QA Contact: Ilanit Stein
URL:
Whiteboard: virt
Depends On: 1048790
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-28 13:51 UTC by rhev-integ
Modified: 2014-03-03 13:32 UTC (History)
12 users (show)

Fixed In Version: is34
Doc Type: Bug Fix
Doc Text:
The process for confirming completion of migration has been revised to add a null check that ensures the destination VDS is valid. This makes it possible to shut down virtual machines source hosts even if migration fails.
Clone Of: 1048790
Environment:
Last Closed: 2014-03-03 13:32:03 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0227 0 normal SHIPPED_LIVE rhevm 3.3.1 bug fix update 2014-03-03 18:29:31 UTC
oVirt gerrit 23705 0 None None None Never
oVirt gerrit 23760 0 None None None Never

Comment 1 Michal Skrivanek 2014-01-28 13:53:37 UTC
merged to ovirt-engine-3.3 as http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=930c229433a32d79a383900392690eeed5a61824

Comment 3 Ilanit Stein 2014-02-11 10:45:08 UTC
Verified on is34.

Have 3 rhel hosts. 
- Run VM on host1.
- Have host 3 avail memory not sufficient to contain this VM.
- Migrate VM (to any host).
- VM starts to migrate to host2 (since host 3 memory is full)
- While migration is running, Kill qemu process on host2 by:
ps aux | grep qemu | grep -v grep | grep -v supervdsmServer | awk '{print $2}' | xargs -I^ kill -9 ^ 
- As a result: a. migration fail b. Trying another host (host 3) - which fail as well. VM stays running on host1.
- Power off the VM succeeded.

Comment 5 errata-xmlrpc 2014-03-03 13:32:03 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0227.html


Note You need to log in before you can comment on or make changes to this bug.