Description of problem:
The implementation of registering a VM containing snapshots with memory disks is broken, the parameters created for copying the memory always assume the source domain is the domain of which the VM is registered from which is not always the case.
This is not a regression but it used to work mainly because the backend logic is placing the memory disks in the same domain where most of the VM disks reside but it's not guaranteed to be there especially now when you can move them to other domains.
This logic is based on the import from export domain but should be changed when registering a VM from data domain.
*** Bug 1150249 has been marked as a duplicate of this bug. ***
The change in this flow seems to be too complicated for 4.2.z and might cause more regressions than being useful, moving to 4.3
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
*** Bug 1828236 has been marked as a duplicate of this bug. ***
this bug is in modified state and targeting 4.4.3, shouldn't it be re-targeted to 4.4.1?
Verified on rhv-release-4.4.1-5-001.noarch according those steps:
1. Create a blank VM with disk
2. Run the VM
3. Create a snapshot with memory and power off the VM
4. Move one of the memory disks AND vm disk to a different storage domain
5. Deactivate and detach the storage domain which holds the memory disks and vm disk
6. Attach the storage back
7. Import the VM back to the environment
Imported vm from step 7 should have a snapshot including memory.
(see image attached)
Created attachment 1699613 [details]
snap with memory verification
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.
Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.