Description of problem (please be detailed as possible and provide log snippests): Ramen as of the latest commit has changed DRCluster to be a cluster scoped resource. This change needs to be reflected in MCO where the DRCluster is being created in the 'default' namespace. Version of all relevant components (if applicable): 4.11 Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes Steps to Reproduce: 1. Create a DR Setup 2. Create a DRPolicy through UI or just a MirrorPeer through CLI 3. Check the DRCluster resource with cluster names provided in MirrorPeer Actual results: DRClusters are created in default namespace Expected results: DRCluster are to be created without any namespace defined as a cluster scope resource. Additional info:
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 (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix 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/RHSA-2022:6156