Created attachment 990394 [details] engine.log, vdsm.log and the OVF_STORE disk Description of problem: After domain import and registering a VM to the DC, the Virt-IO-SCSI flag appears to be disabled although it was enabled in the previous setup. The VM has Virt-IO-SCSI disks. Version-Release number of selected component (if applicable): rhev 3.5 vt13.9 How reproducible: Always Steps to Reproduce: 1. Create a VM and make sure that the Virt-IO-SCSI flag is enabled (in the resource allocation tab in the VM creation prompt) 2. Attach Virt-IO-SCSI disks to the VM 3. Put the domain where the disks are located in maintenance so the OVF_STORE disk will be updated. Detach the domain from the DC 4. Attach the domain back to the DC. Activate the domain. 5. Import the VM Actual results: The Virt-IO-SCSI flag is disabled in the VM configuration. Could be that during OVF upload, the flag is ignored. I checked the OVF after its upload and I can't see this flag. Expected results: The Virt-IO-SCSI flag should not be ignored Additional info: engine.log, vdsm.log and the OVF_STORE disk The VM UUID is 6bb874c9-6e64-4b72-8eb8-72f50cd7ccc0
Tentative targeting for 3.5.1, pending discussion with PM and QA stakeholders.
Can you please describe the impact of the import result? is the VM working or not?
The VM cannot boot from its disk if the disk interface is Virt-IO-SCSI.
3.5.1 is already full with bugs (over 80), and since none of these bugs were added as urgent for 3.5.1 release in the tracker bug, moving to 3.5.2
Tested using ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764
RHEV 3.6.0 has been released, setting status to CLOSED CURRENTRELEASE