Bug 2231076 - ocs-operator crashes due to a panic cause by Nil pointer dereference
Summary: ocs-operator crashes due to a panic cause by Nil pointer dereference
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Nikhil Ladha
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-10 13:31 UTC by umanga
Modified: 2023-08-11 15:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description umanga 2023-08-10 13:31:51 UTC
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:


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