Description of problem: AWS EBS CSI Driver doesn’t support “csi.storage.k8s.io/fsTyps” parameter 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.yaml apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: gp2-test parameters: type: gp2 csi.storage.k8s.io/fsType: ext4 provisioner: ebs.csi.aws.com reclaimPolicy: Delete volumeBindingMode: WaitForFirstConsumer Create a PVC with this storageclass $ cat pvc.yaml kind: PersistentVolumeClaim apiVersion: v1 metadata: name: test-pvc-5 spec: storageClassName: gp2-test accessModes: - ReadWriteOnce resources: requests: storage: 5Gi Create a Pod using this PVC Actual results: PV is not provisioned successfully. Check the event: $ oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE test-pvc-5 Pending gp2-test 6m11s Warning ProvisioningFailed 98s (x9 over 5m53s) ebs.csi.aws.com_ip-10-0-158-46_2aa28a47-d1e8-4570-9a4d-c4b35ea9f5cf failed to provision volume with StorageClass "gp2-test": failed to strip CSI Parameters of prefixed keys: found unknown parameter key "csi.storage.k8s.io/fsType" with reserved namespace csi.storage.k8s.io/ From the doc: https://github.com/openshift/aws-ebs-csi-driver, this parameter should be supported. Expected results: PV is provisioned successfully. Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
The provisioner accepts only "csi.storage.k8s.io/fstype" (i.e. all lowercase). I asked upstream if it's intended.
Yes, in doc: https://github.com/openshift/aws-ebs-csi-driver#createvolume-parameters, there is a note: The parameters are case insensitive.
Submitted PR upstream: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/807
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