Bug 2319131 - Possible race when key rotation lock time out is reached
Summary: Possible race when key rotation lock time out is reached
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: csi-driver
Version: 4.17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Niraj Yadav
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-16 11:23 UTC by Niraj Yadav
Modified: 2024-10-23 06:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-9393 0 None None None 2024-10-16 11:24:09 UTC

Description Niraj Yadav 2024-10-16 11:23:02 UTC
Description of problem (please be detailed as possible and provide log
snippests):

If a key rotation operation takes longer than 3 minutes then the lock timeout is hit which releases the held lock.

In case of RWX volumes some another node can then attempt to rotate the key since there is no lock in place to prevent it.

In such cases, there is risk of the encryption passphrase being lost irrecoverably.

Version of all relevant components (if applicable):


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


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


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?


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:
The LUKS process continues executing post timeout.


Expected results:
There should be no dangling LUKS process if the timeout is reached.

Additional info:


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