[BUG] - Unable to provision VFS

[okdas]

Describe the bug

Unable to provision ReadWriteMany VFS PVC.

To Reproduce
Steps to reproduce the behavior (might not be easy since the cluster has been arond for a bit):

1. Bumped VKE cluster to the latest (v1.31.1+1 -> v1.32.1+1) - might not be related, but I wanted to make sure I got latest controllers;
2. Made sure csi-vultr-plugin is on vultr/vultr-csi:v0.14.0 image tag (csi-vultr-controller pod)
3. Added VFS storageclasses
4. Followed vultr documentation.

Expected behavior

PVC to provision and the volume mounted to the correct container.

csi-vultr-controller Logs

csi-provisioner I0304 00:08:21.313849       1 controller.go:1337] provision "ns420/pvc-69-rwx" class "vultr-block-storage": started
csi-provisioner I0304 00:08:21.313998       1 connection.go:183] GRPC call: /csi.v1.Controller/CreateVolume
csi-provisioner I0304 00:08:21.314163       1 event.go:285] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"ns420", Name:"pvc-69-rwx", UID:"e8455ffb-c903-428c-b0a9-19f99f9d7725", APIVersion:"v1", ResourceVersion:"33216320", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "ns420/pvc-69-rwx"
csi-provisioner I0304 00:08:21.314008       1 connection.go:184] GRPC request: {"capacity_range":{"required_bytes":214748364800},"name":"pvc-e8455ffbc903428c","parameters":{"block_type":"high_perf"},"volume_capabilities":[{"AccessType":{"Mount":{"fs_type":"ext4"}},"access_mode":{"mode":5}}]}
csi-vultr-plugin time="2025-03-04T00:08:21Z" level=error msg="GRPC error: rpc error: code = InvalidArgument desc = CreateVolume: requested capability is not compatible: requested capability access mode is not supported" GRPC.call=/csi.v1.Controller/CreateVolume GRPC.request="name:\"pvc-e8455ffbc903428c\"  capacity_range:{required_bytes:214748364800}  volume_capabilities:{mount:{fs_type:\"ext4\"}  access_mode:{mode:MULTI_NODE_MULTI_WRITER}}  parameters:{key:\"block_type\"  value:\"high_perf\"}"
csi-provisioner I0304 00:08:21.315580       1 connection.go:186] GRPC response: {}
csi-provisioner I0304 00:08:21.315645       1 connection.go:187] GRPC error: rpc error: code = InvalidArgument desc = CreateVolume: requested capability is not compatible: requested capability access mode is not supported
csi-provisioner I0304 00:08:21.315721       1 controller.go:816] CreateVolume failed, supports topology = false, node selected false => may reschedule = false => state = Finished: rpc error: code = InvalidArgument desc = CreateVolume: requested capability is not compatible: requested capability access mode is not supported
csi-provisioner I0304 00:08:21.315992       1 controller.go:1075] Final error received, removing PVC e8455ffb-c903-428c-b0a9-19f99f9d7725 from claims in progress
csi-provisioner W0304 00:08:21.316204       1 controller.go:934] Retrying syncing claim "e8455ffb-c903-428c-b0a9-19f99f9d7725", failure 9
csi-provisioner E0304 00:08:21.316275       1 controller.go:957] error syncing claim "e8455ffb-c903-428c-b0a9-19f99f9d7725": failed to provision volume with StorageClass "vultr-block-storage": rpc error: code = InvalidArgument desc = CreateVolume: requested capability is not compatible: requested capability access mode is not supported
csi-provisioner I0304 00:08:21.316058       1 event.go:285] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"ns420", Name:"pvc-69-rwx", UID:"e8455ffb-c903-428c-b0a9-19f99f9d7725", APIVersion:"v1", ResourceVersion:"33216320", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "vultr-block-storage": rpc error: code = InvalidArgument desc = CreateVolume: requested capability is not compatible: requested capability access mode is not supported

Given I'm running the latest csi, what else should I look at? Thanks!

[happytreees]

Hello @okdas ,

Can you share the PVC spec? It looks like you are using the incorrect storage class for VFS.