DRPolicy is not reconciled by MCO and should be handled by Ramen for updating the MirrorPeer configuration.
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.
will take up in 4.13
Fixed in version: 4.13.0-121
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