Created attachment 1682144 [details] engine.log Description of problem: When importing a VM that contains snapshots with memory disks to the environment, the VM imported successfully with the snapshot but the memory disks are missing. 2020-04-27 14:36:59,083+03 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-865) [678f91c3-f74a-424d-ba4a-fc0758a449da] Memory metadata/dump disk could not be added 2020-04-27 14:36:59,116+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [78d18087] Before acquiring and wait lock 'EngineLock:{exclusiveLocks='[587ff205-6054-4b11-b1f5-849afe474847=OVF_UPDATE]', sharedLocks=''}' 2020-04-27 14:36:59,116+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [78d18087] Lock-wait acquired to object 'EngineLock:{exclusiveLocks='[587ff205-6054-4b11-b1f5-849afe474847=OVF_UPDATE]', sharedLocks=''}' 2020-04-27 14:36:59,117+03 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-78) [78d18087] Running command: ProcessOvfUpdateForStoragePoolCommand internal: true. Entities affected : ID: 587ff205-6054-4b11-b1f5-849afe474847 Type: StoragePool 2020-04-27 14:36:59,203+03 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-865) [678f91c3-f74a-424d-ba4a-fc0758a449da] Memory disks of snapshot 's1'(id: 'b5f87da4-bf4c-4611-bf85-74caf059d3d2') could not be added since storage domain id 'null' does not exists 2020-04-27 14:36:59,214+03 ERROR [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (EE-ManagedThreadFactory-engine-Thread-865) [678f91c3-f74a-424d-ba4a-fc0758a449da] Memory metadata/dump disk could not be added Version-Release number of selected component (if applicable): 4.4_master How reproducible: 100% Steps to Reproduce: 1. Create a VM with disk 2. Run the VM 3. Create a snapshot with memory 4. Deactivate and detach the storage domain which holds the memory disks 5. Attach the storage back 6. Import the VM back to the environment Actual results: VM imported with the snapshot but without the memory disks Expected results: VM should be imported with the snapshot and with the memory disks Additional info: Engine logs attaced
*** This bug has been marked as a duplicate of bug 1573600 ***
Bug 1573600 describes the case where the memory disks are not on the same SD that was re-attached (in case one of the memory disks was migrated). This bug is a private case of bug 1573600.