Description of problem (please be detailed as possible and provide log snippests): [RDR] ramenOpsNamespace should be set by default and required namespace should be created by ramen or mco operator Version of all relevant components (if applicable): OCP version:- 4.16.0-0.nightly-2024-04-03-065948 ODF version:- 4.16.0-69 CEPH version:- ceph version 18.2.1-76.el9cp (2517f8a5ef5f5a6a22013b2fb11a591afd474668) reef (stable) ACM version:- 2.10.0 SUBMARINER version:- v0.17.0 VOLSYNC version:- volsync-product.v0.9.0 VOLSYNC method:- destinationCopyMethod: Direct Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: The user must set the namespace value for ramenOpsNamespace in the Ramen Hub configmap and ensure that namespace exists before adding the value. Expected results: Namespace should be created by the ramen or mco operator, and value should be set by default. Additional info:
Talur, can you please backport it to 4.16
(In reply to Mudit Agarwal from comment #4) > Talur, can you please backport it to 4.16 Mudit, PR 1342 is already backported. Automatic creation of the namespace is handled in https://github.com/RamenDR/ramen/pull/1366 and it is in POST now.
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.16.0 security, enhancement & 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/RHSA-2024:4591