Bug 2246526

Summary:	[4.13.z clone] ocs-operator crashes due to a panic cause by Nil pointer dereference
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Nikhil Ladha <nladha>
Component:	ocs-operator	Assignee:	Nikhil Ladha <nladha>
Status:	CLOSED ERRATA	QA Contact:	Elad <ebenahar>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	ebenahar, kramdoss, muagarwa, nigoyal, odf-bz-bot, uchapaga
Target Milestone:	---
Target Release:	ODF 4.13.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.13.8-1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2231076	Environment:
Last Closed:	2024-04-03 07:03:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2231076, 2246527
Bug Blocks:

Description Nikhil Ladha 2023-10-27 07:19:54 UTC

+++ This bug was initially created as a clone 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:09:57 UTC

Fix should land in 4.14.1 first before backporting to 4.13.z 
Moving to 4.13.6

Comment 4 krishnaram Karthick 2023-12-19 07:27:49 UTC

Moving the bug to 4.13.8 as we have reached the threshold for 4.13.7 and this is a low severity bug.

Comment 5 Mudit Agarwal 2024-01-25 04:12:35 UTC

This will be covered in regression only, we should take it in the next z-stream.

Comment 10 krishnaram Karthick 2024-04-02 07:57:09 UTC

Moving to verified based on regression run results for 4.13.8
No new issues were observed.

Comment 14 errata-xmlrpc 2024-04-03 07:03:07 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.13.8 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:1657