Bug 1055520
| Summary: | NPE: CanDoActionFailure - Import a vm that has memory state snapshot | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-engine | Assignee: | Arik <ahadas> |
| Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | acathrow, adahms, gklein, iheim, istein, lpeer, mavital, mbourvin, michal.skrivanek, ofrenkel, pnovotny, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| 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 13:31:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1031371 | ||
| Bug Blocks: | |||
|
Comment 1
Arik
2014-01-28 12:53:30 UTC
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. 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. 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. 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 |