Bug 1273376

Summary: OVF file is removed for any given VM when only a direct LUN disk is attached to it
Product: [oVirt] ovirt-engine Reporter: Gilad Lazarovich <glazarov>
Component: BLL.StorageAssignee: Maor <mlipchuk>
Status: CLOSED CURRENTRELEASE QA Contact: Eyal Shenitzky <eshenitz>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: acanan, bugs, ecohen, eshenitz, gklein, lsurette, rbalakri, Rhev-m-bugs, tnisan, yeylon
Target Milestone: ovirt-3.6.1Flags: tnisan: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+
Target Release: 3.6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: VM with LUN disk was not registered as part of the recovery OVF_STORE disk Consequence: Once a setup has been destroyed, a VM with only LUN disk could not be recovered. Fix: Make VM with LUN disks also part of the OVF_STORE disk. Result: VM with LUN disks are part of the OVF_STORE disk.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-16 12:20:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine and vdsm logs showing VM OVF being removed when VM only has an attached direct LUN none

Description Gilad Lazarovich 2015-10-20 10:28:41 UTC
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

Comment 1 Yaniv Lavi 2015-10-29 12:46:53 UTC
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.

Comment 2 Eyal Shenitzky 2015-12-08 13:34:02 UTC
 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.

Comment 3 Sandro Bonazzola 2015-12-16 12:20:13 UTC
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.