Created attachment 1084674 [details] engine and vdsm logs showing VM OVF being removed when VM only has an attached direct LUN Description of problem: OVF file is removed for any given VM when only a direct LUN disk is attached to it Version-Release number of selected component (if applicable): 3.6 How reproducible: 100% Steps to Reproduce: 1. Create a VM with no disks, ensure that the VM's OVF file is created on all domains 2. Add a direct LUN disk to the VM, check on the VM's OVF file Actual results: The VM's OVF file is removed from all domains Expected results: The OVF file is expected to stays in place, as it does with shareable disks, the direct LUN disk alias shouldn't be included within the VM's OVF file Additional info: Please find the attached VDSM (SPM) and engine logs
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Verified on: ------------- vdsm-4.17.12-0.el7ev.noarch rhevm-3.6.1.1-0.1.el6 The OVF file stays in place and isn't removed from all domains.
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.