Bug 2066813

Summary:	Issue in creating gp3 type-based volumes.
Product:	OpenShift Container Platform	Reporter:	Palash Khaire <pkhaire>
Component:	Storage	Assignee:	aos-storage-staff <aos-storage-staff>
Storage sub component:	Storage	QA Contact:	Wei Duan <wduan>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs, jsafrane
Version:	4.9
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-24 09:24:30 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 Palash Khaire 2022-03-22 14:21:01 UTC

Description of problem: Issue in creating gp3 type-based volumes.

The same does work with  gp2. The gp3 type volume should work well on 4.9.z CSI driver provisioned.

Will add the events in the Bug notes.

Comment 3 Jan Safranek 2022-03-24 09:24:30 UTC

This looks like OCP / the CSI driver does not have permissions to use the referenced KMS key. In that case, AWS cloud API CreateDisk call returns a valid volume ID and only after that it realizes that it does not have access to the encryption key and silently deletes the volume.
We're fixing it in 4.11 here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2049872

As a workaround in 4.9, the customer can grant required permissions to the AWS EBS CSI Driver IAM role manually, as shown in https://github.com/openshift/cluster-storage-operator/pull/263/files.

*** This bug has been marked as a duplicate of bug 2049872 ***