Why RHV VMs are imported without any LUNs during the DR failover
Issue
- The VM is having only direct LUNs attached. While importing the VM to the DR site, the VM is imported without any LUNs. The engine log shows the below error.
2020-01-03 14:13:48,740+08 WARN [org.ovirt.engine.core.bll.exportimport.ImportVmCommand] (default task-28) [] Skipping validation for external LUN disk '2078a6a2-e2a3-4835-b91f-1111111111111' since partialImport flag is true. Invalid external LUN disk might reflect on the run VM process
- While importing the VM manually from the GUI it's showing
Uncaught exception
in the UI.
2020-01-07 02:20:14,852-05 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-1) [3f28a13f-1656-4994-9aa5-a613d9e6795d] Uncaught exception: com.google.gwt.event.shared.UmbrellaException: Exception caught: undefined
- While importing the VM without the
partial Import
flag usingPython SDK/Ansible
, it's showing the error below.
ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot import VM. VirtIO-SCSI is disabled for the VM]". HTTP response code is 409.
Environment
- Red Hat Virtualization 4.3.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.