Description of problem: When “iopsPerGB” parameter is not set, event for AWS EBS CSI Driver provisioning is not clear Version-Release number of selected component (if applicable): 4.7.0-rc.3 How reproducible: Always Steps to Reproduce: Create a storageclass with the following yaml file $ cat sc-csi.yaml apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: io1-csi parameters: type: io1 provisioner: ebs.csi.aws.com reclaimPolicy: Delete volumeBindingMode: Immediate Create a PVC using this storageclass Actual results: PV is not provisioned. Check the events: Warning ProvisioningFailed 3s ebs.csi.aws.com_ip-10-0-158-46_2aa28a47-d1e8-4570-9a4d-c4b35ea9f5cf failed to provision volume with StorageClass "io1-csi": rpc error: code = Internal desc = Could not create volume "pvc-b64c726a-a494-4ce7-bbb1-72822526f160": could not create volume in EC2: InvalidParameterCombination: The parameter iops must be specified for io1 volumes. status code: 400, request id: 625e97aa-8238-4a80-92c4-36fde3561c1e The event said, parameter “iops” should be set here, per the doc: https://github.com/openshift/aws-ebs-csi-driver, seems parameter “iopsPerGB” should be set here. Create a storageclass with the following yaml file, PV is provisioned successfully: $ cat sc.yaml apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: io1-csi parameters: type: io1 iopsPerGB: "50" provisioner: ebs.csi.aws.com reclaimPolicy: Delete volumeBindingMode: Immediate Expected results: With a clearer event to indicate the “iopsPerGB” parameter needs to be set here. Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
Posted a fix upstream: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/767
Verified with: 4.8.0-0.nightly-2021-04-14-211524
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security 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-2021:2438