+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1150245 +++ ====================================================================== Description of problem: Memory volumes are created on a storage domain without allowing the user to choose where they go, and their existence may interfere with the admin's ability to manage that domain (see, e.g., bug 1145658). One way around this is the ability to remove these volumes (see bug 1150242), but as they may be important, it's also critical to have the ability to move them to another domain. (Originally by Allon Mureinik)
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant. (Originally by Sandro Bonazzola)
*** Bug 1509807 has been marked as a duplicate of this bug. *** (Originally by Tal Nisan)
Allon / Tal, how this bug is different from this: 1150242? To me sounds like this bug implementation should contain bz#1150242 and this other bz can be close duplicate of this one.
Verified with the following code: ------------------------------------------ ovirt-engine-4.2.2.5-0.1.el7.noarch vdsm-4.20.23-1.el7ev.x86_64 Verified with the following scenario: ------------------------------------------ 1. Created a VM with disks 2. Start the VM 3. Created snapshot with memory 4. Via the Webadmin -> disks tab select the data memory snapshot disk and move it to another domain 5. Move the meta data memory snanpshot disk to the same domain as the data memory snapshot disk 6. Power off the VM 7. Preview the snapshot 8. Undo the previewed snapshot 9. Start the VM Moving to verified
Those are indeed the correct steps, moving of the two volumes and see if the snapshot can be previewed with the memory
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. https://access.redhat.com/errata/RHEA-2018:1488
BZ<2>Jira Resync