-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCP 3.11 - unrecognized volume type by Kubernetes #274
Comments
My sc: oc get sc netapp -o yaml created from apiVersion: storage.k8s.io/v1 |
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. |
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. |
Fixed by 2ccb2cc |
* If an SVM has CHAP enabled, all 4 CHAP fields become required. * Adding more robust logic checks are CHAP configuration
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
The text was updated successfully, but these errors were encountered: