Trident: OCP 3.11 - unrecognized volume type by Kubernetes

[leemmcc]

I'm sure I'm missing something simple here, but I'm trying to get Trident working with Azure Netapp Files. So far following the examples I've been able to get it to the point where trident is installed and able to create the volumes, however I get the following once they are created, and it will go into a loop deleting and creating them each time.

On the pv:

Normal ProvisioningFailed 8s (x2 over 41s) netapp.io/trident unrecognized volume type by Kubernetes

In trident logs:

time="2019-08-21T19:54:27Z" level=info msg="Filesystem created." creationToken=anf-156da6c408af43f9bfc5882361d830da name=trident-basic-79dd7
time="2019-08-21T19:54:27Z" level=info msg="Waiting for volume state." desiredState=Succeeded
time="2019-08-21T19:54:53Z" level=error msg="Kubernetes frontend doesn't recognize this type of volume; deleting the provisioned volume." driver=azure-netapp-files type= volume=trident-basic-79dd7
time="2019-08-21T19:54:53Z" level=info msg="Filesystem deleted." volume=anf-156da6c408af43f9bfc5882361d830da

[leemmcc]

My sc:

oc get sc netapp -o yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
creationTimestamp: 2019-08-21T19:52:03Z
name: netapp
resourceVersion: "215027343"
selfLink: /apis/storage.k8s.io/v1/storageclasses/netapp
uid: 258aac8d-c44d-11e9-b761-000d3a046b95
parameters:
backendType: azure-netapp-files
provisioner: netapp.io/trident
reclaimPolicy: Delete
volumeBindingMode: Immediate

created from

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: netapp
provisioner: netapp.io/trident
parameters:
backendType: "azure-netapp-files"

[bnaylor]

Hi, sorry to hear about your difficulties with the new driver.

@innergy figured out the problem. We developed the ANF driver as a CSI driver and unfortunately didn't manage to go back and tick the "non-CSI" box in the compatibility matrix. It won't work in non-CSI mode without some changes. Hold tight for those, it should be relatively easy to fix.

[leemmcc]

Appreciate it. With OCP 3.11 being maintained until 2022, I think a lot of enterprise folks will have clusters around for a while, while they figure out a migration to 4.x. Glad to hear this should work on it.

[bnaylor]

Fixed by 2ccb2cc27a063860f1173927a1f13a0a935a6ea1