Bug 2046887

Summary:	use KMS_PROVIDER name for IBM key protect service as "ibmkeyprotect"
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Humble Chirammal <hchiramm>
Component:	csi-driver	Assignee:	Humble Chirammal <hchiramm>
Status:	CLOSED ERRATA	QA Contact:	akgunjal <akgunjal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	madam, muagarwa, ocs-bugs, odf-bz-bot
Target Milestone:	---
Target Release:	ODF 4.10.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	4.10.0-132	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-13 18:52:21 UTC	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 Humble Chirammal 2022-01-27 09:38:39 UTC

Description of problem (please be detailed as possible and provide log
snippests):

At present, the KMS_PROVIDER name is registered as "kp-metadata" , however on further discussion last week we decided to have it in parity across all the components nooba,rook, console and ceph csi that we will keep the KMS_PROVIDER name as "ibmkeyprotect". This issue tracks the change in ceph csi.


Version of all relevant components (if applicable):
odf release 4.10

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:


Expected results:


Additional info:

Comment 6 Humble Chirammal 2022-04-07 12:08:20 UTC

IBM team was helping us to test this feature and based on the update from them the feature was tested on ODF build  4.10.0-138 and storage class based encryption worked as expected. Based on the same feedback, I am moving this bugzilla to verified.

Comment 8 errata-xmlrpc 2022-04-13 18:52:21 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 (Important: Red Hat OpenShift Data Foundation 4.10.0 enhancement, security & 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/RHSA-2022:1372