Bug 2273705

Summary:	[RDR] [Discovered Apps] ramenOpsNamespace should be set by default and required namespace should be created by ramen or mco operator
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Pratik Surve <prsurve>
Component:	odf-dr	Assignee:	Raghavendra Talur <rtalur>
odf-dr sub component:	ramen	QA Contact:	Pratik Surve <prsurve>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	ebenahar, kseeger, muagarwa, rtalur
Version:	4.16
Target Milestone:	---
Target Release:	ODF 4.16.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.16.0-102	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-17 13:18:31 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:

Description Pratik Surve 2024-04-05 18:48:56 UTC

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:

Comment 4 Mudit Agarwal 2024-05-07 06:04:51 UTC

Talur, can you please backport it to 4.16

Comment 7 Raghavendra Talur 2024-05-13 05:15:02 UTC

(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.

Comment 12 errata-xmlrpc 2024-07-17 13:18:31 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 (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