Bug 1055520 – NPE: CanDoActionFailure - Import a vm that has memory state snapshot

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1055520 - NPE: CanDoActionFailure - Import a vm that has memory state snapshot

Summary:	NPE: CanDoActionFailure - Import a vm that has memory state snapshot

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.3.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	3.3.1
Assigned To:	Arik
QA Contact:	Pavel Novotny
Docs Contact:

URL:
Whiteboard:	virt
Keywords:	ZStream

Duplicates:	1056644 (view as bug list)
Depends On:	1031371
Blocks:
	Show dependency tree / graph

Reported:	2014-01-20 08:21 EST by rhev-integ
Modified:	2014-03-03 08:31 EST (History)
CC List:	13 users (show)

See Also:
Fixed In Version:	is34
Doc Type:	Bug Fix
Doc Text:	Previously, attempting to import a virtual machine with a memory snapshot into a storage domain in which no disk was set would result in an NPE error. This was caused by the import action assuming that the storage domain would exist. With this update, the existence of the storage domain is now confirmed and subsequent action handled accordingly, making it possible to successfully import virtual machines with memory snapshtos under these circumstances.
Story Points:	---
Clone Of:	1031371
Environment:
Last Closed:	2014-03-03 08:31:42 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	21450	None	None	None	Never
oVirt gerrit	21465	None	None	None	Never
Red Hat Product Errata	RHBA-2014:0227	normal	SHIPPED_LIVE	rhevm 3.3.1 bug fix update	2014-03-03 13:29:31 EST

Groups: None (edit)

Comment 1 Arik 2014-01-28 07:53:30 EST

*** Bug 1056644 has been marked as a duplicate of this bug. ***

Comment 3 Pavel Novotny 2014-02-11 15:59:38 EST

Verified in rhevm-3.3.1-0.47.el6ev.noarch (is34).

Verified by following the reproducer:
1. Starting vm ramSnapshotVM and waiting for it to boot
2. Starting cat on vm ramSnapshotVM from /dev/zero to /dev/null
3. Creating snapshot ram_snapshot_0 with RAM state
4. Stopping vm ramSnapshotVM
5. Exporting vm ramSnapshotVM to domain export_domain
6. Removing original vm to allow import vm without collapse snapshots
7. Importing vm ramSnapshotVM from export domain export_domain

Results:
VM was imported successfully. No NPE or errors found in engine.log.
Additionally, restoring VM state (incl. RAM) from the snapshot was also successful.

Comment 4 Ilanit Stein 2014-02-12 05:37:38 EST

Verification flow for this bug:

A. Reproduce failure (NPE) on is23 (for which this bug was reported), by using these steps:
1. Have 2 data storage domains.
2. Create a VM with disk on storage domain 1.
3. Starting vm ramSnapshotVM and waiting for it to boot
4. Starting cat on vm ramSnapshotVM from /dev/zero to /dev/null
5. Creating snapshot ram_snapshot_0 with RAM state
6. Stopping vm ramSnapshotVM
7. Exporting vm ramSnapshotVM to domain export_domain
8. Removing original vm to allow import vm without collapse snapshots
9. Importing vm ramSnapshotVM from export domain export_domain to storage domain 2

B. Use the same flow on is34, to see it is fixed.

Comment 5 Pavel Novotny 2014-02-12 09:42:23 EST

Re-verified in rhevm-3.3.1-0.47.el6ev.noarch (is34).

Used updated verification scenario in comment 4. 
The VM was created on one data domain and then imported to a second data domain. All eneded up well, no errors during VM import. The VM is operational, including the live snapshot.

Comment 7 errata-xmlrpc 2014-03-03 08:31:42 EST

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.