Bug 2319131

Summary:	Possible race when key rotation lock time out is reached
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Niraj Yadav <niryadav>
Component:	csi-driver	Assignee:	Niraj Yadav <niryadav>
Status:	ASSIGNED ---	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.17	CC:	odf-bz-bot
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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: