Bug 2246525 - [4.12.z clone] ocs-operator crashes due to a panic cause by Nil pointer dereference
Summary: [4.12.z clone] ocs-operator crashes due to a panic cause by Nil pointer deref...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.12.12
Assignee: Nikhil Ladha
QA Contact: Elad
URL:
Whiteboard:
: 2266704 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-27 07:13 UTC by Nikhil Ladha
Modified: 2024-04-08 15:31 UTC (History)
7 users (show)

Fixed In Version: 4.12.12-2
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-04 06:27:56 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 2233 0 None Merged Bug 2246525:[release-4.12] Use context.TODO() instead of reconciler's context 2024-03-21 09:47:17 UTC
Red Hat Product Errata RHBA-2024:1673 0 None None None 2024-04-04 06:27:59 UTC

Description Nikhil Ladha 2023-10-27 07:13:49 UTC 
This bug was initially created as a copy of Bug #2231076


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

When upgrading from v4.12.z to v4.13.z, ocs-operator crashes. But, it eventually restarts and works fine. It might even be seen on fresh installs.

Version of all relevant components (if applicable):
v4.13.z

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No. It does not affect functionality.

Is there any workaround available to the best of your knowledge?
Not needed. It recovers automatically.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes.

Can this issue reproduce from the UI?
Yes.

If this is a regression, please provide more details to justify this:
Probably, but it does not affect functionality.

Steps to Reproduce:
1. Install ODF v4.12.z
2. Upgrade to ODF v4.13.z
3. Watch ocs-operator pod for restarts.
4. After it restarts, check it's previous logs `oc logs -p ocs-operator-`


Actual results:
ocs-operator crashes and restarts once.

Expected results:
ocs-operator should not crash and restart without reason.

Additional info:
Comment 3 krishnaram Karthick 2023-10-27 10:22:48 UTC 
Fix should land on 4.14.1 and 4.13.6 first. Moving this bug to 4.12.11.
Comment 4 krishnaram Karthick 2023-12-19 07:23:13 UTC 
Moving the bug to 4.12.12 as we have reached the threshold for 4.12.11 and this is a low severity issue.
Comment 5 krishnaram Karthick 2024-02-22 12:01:11 UTC 
Fix not yet available in previous releases. moving out.
Comment 6 Nikhil Ladha 2024-02-29 09:36:23 UTC 
*** Bug 2266704 has been marked as a duplicate of this bug. ***
Comment 7 Nikhil Ladha 2024-02-29 09:38:32 UTC 
We are good to take this bz for the next z-stream release. All the other latest release have this fix now.
Also, this bz doesn't require any explicit testing, just a regression run would do.
Comment 12 krishnaram Karthick 2024-04-02 07:56:18 UTC 
Moving to verified based on regression run results for 4.12.13. 
No new issues were observed.
Comment 16 errata-xmlrpc 2024-04-04 06:27:56 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 (Red Hat OpenShift Data Foundation 4.12.12 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/RHBA-2024:1673
Note You need to log in before you can comment on or make changes to this bug.