Bug 2280657 - [MDR][RDR][Discovered Apps]: On fresh installation Ramen pod crashes on managed cluster as OADP Operator is not installed
Summary: [MDR][RDR][Discovered Apps]: On fresh installation Ramen pod crashes on manag...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.16
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.16.0
Assignee: Raghavendra Talur
QA Contact: akarsha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-15 15:00 UTC by akarsha
Modified: 2024-11-15 04:25 UTC (History)
8 users (show)

Fixed In Version: 4.16.0-130
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-07-17 13:22:43 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github RamenDR ramen pull 1462 0 None open vrg: don't watch velero CRs unless CRDs are installed 2024-06-18 08:40:33 UTC
Github red-hat-storage ramen pull 292 0 None open Bug 2280657: Backport of upstream PR 1450 2024-06-11 04:53:14 UTC
Github red-hat-storage ramen pull 305 0 None open Bug 2280657: Backport of upstream PR 1461 2024-06-17 18:35:32 UTC
Github red-hat-storage ramen pull 308 0 None open Bug 2280657: backport of upstream PR 1462 2024-06-19 19:11:13 UTC
Red Hat Product Errata RHSA-2024:4591 0 None None None 2024-07-17 13:22:44 UTC

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
Note You need to log in before you can comment on or make changes to this bug.