Skip to main content
NetApp Stage KB

Kubernetes create PVC  with error "no available backends for storage class media sas"

Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

 

 

Applies to

  • ONTAP 9
  • Trident for Kubernetes
  • PersistentVolumeClaim (PVC)

Issue

Create PVC status stuck in pending with error below:
 
Example:

LINUX@master:~/trident/trident-installer$ kubectl get pvc
NAME           STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
sas-vol        Pending                                                                         ontap-sas      7s

...

Events:
  Type     Reason                Age                From                                        Message
  ----     ------                ----               -----                                        -------
  Normal   Provisioning          17s (x3 over 25s)  csi.trident.netapp.io_trident-csi-<UUID>  External provisioner is provisioning volume for claim "default/sas-vol"
  Normal   ProvisioningFailed    17s (x3 over 25s)  csi.trident.netapp.io     no available backends for storage class <SC_NAME>
  Warning  ProvisioningFailed    17s (x3 over 25s)  csi.trident.netapp.io_trident-csi-<UUID>  failed to provision volume with StorageClass "ontap-sas": rpc error: code = Unknown desc = no available backends for storage class <SC_NAME>
  Normal   ExternalProvisioning  2s (x3 over 25s)   persistentvolume-controller      waiting for a volume to be created, either by external provisioner "csi.trident.netapp.io" or manually created by system administrator

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.