Bug 892638 - [3.1.z] engine: rerun of HA vm fails when vm's pid is killed during live snapshot
Summary: [3.1.z] engine: rerun of HA vm fails when vm's pid is killed during live snap...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 3.1.5
Assignee: Arik
QA Contact: meital avital
URL:
Whiteboard: virt
Depends On: 878041
Blocks: 891634
TreeView+ depends on / blocked
 
Reported: 2013-01-07 13:42 UTC by Idith Tal-Kohen
Modified: 2014-09-28 06:38 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, if a highly available virtual machine was killed during a live snapshot, the virtual machine would not be able to be re-run because the virtual machine would be in a different state than was expected by the engine. Now, the status of the virtual machine is saved when live snapshot is initiated and is referenced so that a virtual machine can be re-run after it has been killed during a live snapshot.
Clone Of: 878041
Environment:
Last Closed: 2013-06-18 09:34:39 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-2013:0950 0 normal SHIPPED_LIVE rhevm 3.1.5 bug fix update 2013-06-18 13:34:15 UTC
oVirt gerrit 10618 0 None None None Never

Comment 5 Aharon Canan 2013-06-10 14:38:57 UTC 
Verified using 3.1.5 (si29)

verification steps:
1. Create snapshot while VM is up
2. while snapshot kill the VM process on the relevant host (kill -9 the qemu-kvm process)
3. check that snapshot created and that VM is up again


environment:
VM server with HA
2 hosts
2 storage domain (ISCSI)
1 DC
Comment 6 Aharon Canan 2013-06-10 14:45:07 UTC 
just to make things clearer, 

In this bug I verified the live snapshot and not the live storage migration
for the live storage migration we have different bug.
Comment 8 errata-xmlrpc 2013-06-18 09:34:39 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-2013-0950.html
Note You need to log in before you can comment on or make changes to this bug.