Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1518428

Summary:	Export storage domain is not recovered in a DR scenario
Product:	[oVirt] ovirt-engine	Reporter:	Maor <mlipchuk>
Component:	Backend.Core	Assignee:	Maor <mlipchuk>
Status:	CLOSED DUPLICATE	QA Contact:	meital avital <mavital>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	amureini, bugs, mlipchuk
Target Milestone:	ovirt-4.2.2	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	DR
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-11 14:18:04 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:

Description Maor 2017-11-28 21:54:40 UTC

Description of problem:
On a DR site to site scenario we fail over and fail back the engine setup syncing between the storage domains replications.
Since export storage domain can not be force detach, it can not be re-attach  to the setup without adjusting its meta data (see https://www.ovirt.org/documentation/how-to/storage/clear-the-storage-domain-pool-config-of-an-exported-nfs-domain/)

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Add an export storage domain to the setup
2. Make the export domain replicated to another storage domain (or use the existing one)
3. Try to fail over the setup and attach the export storage domain from oVirt 


Actual results:
Attaching the export domain will fail since the metadata consists the pool uuid

Expected results:
We should add an ansible script to clean the export storage domain metadata

Additional info:

Comment 2 Yaniv Kaul 2017-11-29 13:14:55 UTC

Severity?

Comment 3 Maor 2017-11-29 15:39:54 UTC

Export domain does not run any VMs, so I don't see any crucial impact if the user will manually have to attach it again, combined with the fact that we plan to make export domain obsolete and use it as a data domain, I would make it a low severity

Feel free to change if you think otherwise

Comment 4 Maor 2018-01-11 14:18:04 UTC

Noticed now that I opened a duplicate bug on that issue, closing this one since BZ1533428 already applied with the correct product/component.

*** This bug has been marked as a duplicate of bug 1533428 ***