Bug 2120104 - [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
Summary: [RDR] When a duplicate DRPolicy is created with a different Sync schedule, th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.12.0
Assignee: Sanjal Katiyar
QA Contact: Aman Agrawal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-21 17:43 UTC by Aman Agrawal
Modified: 2023-08-09 16:46 UTC (History)
9 users (show)

Fixed In Version: 4.12.0-74
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-08 14:06:28 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.