Bug 2120104

Summary:	[RDR] When a duplicate DRPolicy is created with a different Sync schedule, the Sync schedule starts showing up in the mirrorpeer yaml even though the policy creation fails
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Aman Agrawal <amagrawa>
Component:	management-console	Assignee:	Sanjal Katiyar <skatiyar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Aman Agrawal <amagrawa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	gshanmug, jefbrown, kramdoss, muagarwa, nthomas, ocs-bugs, odf-bz-bot, skatiyar, srangana
Target Milestone:	---
Target Release:	ODF 4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.12.0-74	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-08 14:06:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 2 Shyamsundar 2022-09-15 11:59:37 UTC

I had a concern that creating the DRPolicy before MirrorPeer may have issues due to DRClusters and the related spec.region values, or DRCluster determining the available SCs and VRCs on the cluster to read their "ramendr.openshift.io/storageid" or "ramendr.openshift.io/replicationid" labels to determine the nature of sync/async between the clusters.

As the current workflow creates DRClusters anyway post DRPolicy creation, this should not matter as we move to reading the class labels as compared to the spec.region values from DRClusters.

So the proposed fix to create the policy first and then the MirrorPeer to avoid the BZ reported is fine.