Bug 2224493 - Panic when operator is fencing a node where pv is no provisioned by CSI
Summary: Panic when operator is fencing a node where pv is no provisioned by CSI
Keywords:
Status: ON_QA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.14.0
Assignee: Subham Rai
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-21 06:37 UTC by Subham Rai
Modified: 2023-08-09 17:03 UTC (History)
3 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rook rook issues 12558 0 None open Panic when operator is fencing a node 2023-07-21 06:37:46 UTC
Github rook rook pull 12563 0 None open rbd: node fencing, skip pv when pv is not backed by csi 2023-07-21 06:46:37 UTC

Description Subham Rai 2023-07-21 06:37:46 UTC
Description of problem (please be detailed as possible and provide log
snippets):


This is a negative case where a on deployment pod consuming pv not provisioned by csi and another deployment pod with rbd rwo are on the same node and node fencing is triggered.

In this case rook operator goes in a panic state. more details https://github.com/rook/rook/issues/12558


Version of all relevant components (if applicable):
4.14

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

yes

Is there any workaround available to the best of your knowledge?
No,


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?
Yes


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 4 Subham Rai 2023-08-01 15:06:27 UTC
Already in builds.


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