Trident PVC can't be properly created and bound, when using the parameter "csi.storage.k8s.io/fstype" in a storage class
- Views:
- 308
- Visibility:
- Public
- Votes:
- 0
- Category:
- trident-kubernetes
- Specialty:
- snapx
- Last Updated:
- 9/3/2024, 7:50:56 AM
Applies to
- NetApp Astra Trident 24.X
- NetApp ONTAP 9.X
Issue
When a storage class has been defined the parameter csi.storage.k8s.io/fstype
, the PVC creation gets stuck and the PV is not properly created
Normal ExternalProvisioning 11s (x2 over 13s) persistentvolume-controller Waiting for a volume to be created either by the external provisioner 'csi.trident.netapp.io' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
Normal Provisioning 5s (x2 over 13s) csi.trident.netapp.io_trident-controller-xxyyxxyyxx-xxyy_yzyzyzyz-xyxy-zyzy-xzxz-zyxyyzzyxzzx External provisioner is provisioning volume for claim "namespace1/pvc1"
Warning ProvisioningFailed 5s (x2 over 13s) csi.trident.netapp.io_trident-controller-xxyyxxyyxx-xxyy_yzyzyzyz-xyxy-zyzy-xzxz-zyxyyzzyxzzx failed to provision volume with StorageClass "myclass": failed to strip CSI Parameters of prefixed keys: found unknown parameter key "csi.storage.k8s.io/fstype" with reserved namespace csi.storage.k8s.io/