Bug 1218733

Summary: Importing storage domains into an uninitialized datacenter leads to duplicate OVF_STORE disks being created, and can cause catastrophic loss of VM configuration data
Product: Red Hat Enterprise Virtualization Manager Reporter: Yaniv Lavi <ylavi>
Component: ovirt-engineAssignee: Maor <mlipchuk>
Status: CLOSED ERRATA QA Contact: Raz Tamir <ratamir>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.5.0CC: acanan, adahms, amureini, bcholler, ecohen, eedri, gklein, gwatson, jamills, juwu, lpeer, lsurette, mkalinin, mlipchuk, pablo.iranzo, pzhukov, rbalakri, rhev-integ, Rhev-m-bugs, sherold, tnisan, yeylon, ylavi
Target Milestone: ---Keywords: ZStream
Target Release: 3.5.1-1Flags: ylavi: Triaged+
Hardware: All   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, when importing an existing, clean storage domain that contains OVF_STORE disks from an old setup to an uninitialized data center, the OVF_STORE disks did not get registered after the data center was initialized and all virtual machine information was lost. With this update, when importing clean storage domains to an uninitialized data center, the OVF_STORE disks are registered correctly, and new unregistered entities are available in the Administration Portal under the Storage tab. In addition, storage domains with dirty metadata cannot be imported to uninitialized data centers.
Story Points: ---
Clone Of: 1217339 Environment:
Last Closed: 2015-05-11 16:50:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1214408, 1217339    
Bug Blocks: 1219038    

Comment 4 Allon Mureinik 2015-05-06 14:46:59 UTC
Maor, please provide some doctext for this issue.
Thanks!

Comment 10 errata-xmlrpc 2015-05-11 16:50:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0956.html