Bug 2280657

Summary:	[MDR][RDR][Discovered Apps]: On fresh installation Ramen pod crashes on managed cluster as OADP Operator is not installed
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	akarsha <akrai>
Component:	odf-dr	Assignee:	Raghavendra Talur <rtalur>
odf-dr sub component:	ramen	QA Contact:	akarsha <akrai>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	asagare, hnallurv, kseeger, muagarwa, ocs-bugs, prsurve, rtalur, sagrawal
Version:	4.16	Keywords:	TestBlocker
Target Milestone:	---
Target Release:	ODF 4.16.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.16.0-130	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-17 13:22:43 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 akarsha 2024-05-15 15:00:45 UTC

Description of problem (please be detailed as possible and provide log
snippests):

On fresh installation Ramen pod crashes on managed cluster as OADP Operator is not installed that is after creating DRPolicy on hub cluster, ramen-dr-cluster-operator pod on managed clusters goes into CrashLoopBackOff state due velero crds missing

Similar issue seen even in upgraded cluster from 4.15 to 4.16, that is after upgrade ramen pod on managed clusters crashes as OADP Operator is not installed

$ oc get pod -n openshift-dr-system
NAME                                         READY   STATUS             RESTARTS      AGE
pod/ramen-dr-cluster-operator-7ff75496cc-j5fw5  1/2     CrashLoopBackOff   9 (12s ago)   44m

Version of all relevant components (if applicable):
OCP: 4.16.0-0.nightly-2024-05-08-222442
ODF: 4.16.0-99.stable
ACM: 2.10.2
CEPH: 18.2.0-192.el9cp (d96dcaf9fd7ef5530bddebb07f804049c840d87e) reef (stable)

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?
always

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Deploy MDR/RDR
2. Observe the ramen-dr-cluster-operator pod status on managed clusters


Actual results:
ramen-dr-cluster-operator pod goes into CrashLoopBackOff state

Expected results:
ramen-dr-cluster-operator pod should not go into CrashLoopBackOff state

Additional info:

Comment 17 errata-xmlrpc 2024-07-17 13:22:43 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

Comment 18 Red Hat Bugzilla 2024-11-15 04:25:42 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days