Bug 2115020

Summary:	[RDR] Sync schedule is not removed from mirrorpeer yaml after DR Policy is deleted
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Aman Agrawal <amagrawa>
Component:	management-console	Assignee:	gowtham <gshanmug>
Status:	CLOSED ERRATA	QA Contact:	Aman Agrawal <amagrawa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.11	CC:	gshanmug, jefbrown, muagarwa, nthomas, ocs-bugs, odf-bz-bot, sagrawal, skatiyar, srangana, vbadrina
Target Milestone:	---	Keywords:	Reopened
Target Release:	ODF 4.13.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-21 15:22:14 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 Vineet 2022-09-12 08:45:57 UTC

DRPolicy is not reconciled by MCO and should be handled by Ramen for updating the MirrorPeer configuration.

Comment 4 Shyamsundar 2022-09-12 13:31:35 UTC

As the console creates the DRPolicy and the MirrorPeer resources, and updates the MirrorPeer resource with a schedule when a DRPolicy is additionally created, the console would have to ensure removal of the schedule as well.

- DRPolicy resource is not aware of MirrorPeer resource
- MirrorPeer resource is not adding/removing the schedules watching for existing DRPolicy resources
- The above resources are mostly independent (other than MirrorPeer creating DRCluster resource or updating them)

From a console workflow the removal of the schedule has to ensure there are no other DRPolicy resources with the same schedule, and if so reomove the schedule from the MirrorPeer as well.

Moving this to the console component.

Comment 12 Sanjal Katiyar 2022-10-13 09:32:08 UTC

will take up in 4.13

Comment 24 Mudit Agarwal 2023-04-03 10:53:06 UTC

Fixed in version: 4.13.0-121

Comment 31 errata-xmlrpc 2023-06-21 15:22:14 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix update), 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://access.redhat.com/errata/RHBA-2023:3742