Bug 2049790 - Add error handling for GetCurrentStorageClusterRef
Summary: Add error handling for GetCurrentStorageClusterRef
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.10.0
Assignee: Pranshu Srivastava
QA Contact: Pratik Surve
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-02 17:18 UTC by Pranshu Srivastava
Modified: 2023-08-09 17:00 UTC (History)
7 users (show)

Fixed In Version: 4.10.0-141
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-13 18:52:48 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-multicluster-orchestrator pull 67 0 None open Bug 2049790: [release-4.10] Add error handling for GetCurrentStorageClusterRef 2022-02-03 05:54:01 UTC
Red Hat Product Errata RHSA-2022:1372 0 None None None 2022-04-13 18:52:58 UTC

Description Pranshu Srivastava 2022-02-02 17:18:07 UTC
Description of problem (please be detailed as possible and provide log
snippests): Add error handling for GetCurrentStorageClusterRef method that would otherwise cause a nil pointer dereference.


Version of all relevant components (if applicable): ODF 4.10


Can this issue reproducible? Yes.

Steps to Reproduce:
1. Deploy DR cluster
2. Deploy ODF over them
3. Create multiclusteroperator
4. Create mirror peer


Actual results: In cases when spoke cluster name does not match any managed cluster, we need to return an error and handle it in the caller. Failing to do so will create nil pointer exception and program crashes.


Expected results: It should error out and reconcile again.

Comment 3 umanga 2022-02-03 05:24:31 UTC
This is a known corner case that causes pod to terminate when incorrect MirrorPeer CR is created. Adding devel_ack+ .

Comment 11 errata-xmlrpc 2022-04-13 18:52:48 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.10.0 enhancement, security & 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-2022:1372


Note You need to log in before you can comment on or make changes to this bug.