Skip to main content
NetApp Knowledge Base

Trident doesn't match a StorageClass to a CVO or ONTAP Select storage

  1. Last updated
  2. Save as PDF
Views:
192
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident for Openshift and Kubernetes
  • Cloud Volumes ONTAP (CVO)
  • ONTAP Select

Issue

When setting up a StorageClass with the definition of the media type (ontap-nas, ontap-san, and their -economy drivers, support ssd, hdd and hybrid),
the StorageClass doesn't match a Trident backend defined for CVO or ONTAP Select:
 
time="2022-07-12T12:04:02Z" level=info msg="no backend pools support the requisite protocol" requestID=<REQUEST_UUID>
requestSource=CSI
time="2022-07-12T12:04:02Z" level=info msg="no backend pools support any requisite topologies" requestID=<REQUEST_UUID>
requestSource=CSI
time="2022-07-12T12:04:02Z" level=error msg="GRPC error: rpc error: code = Unknown
desc = no available backends for storage class <STORAGECLASS_NAME>" requestID=<REQUEST_UUID> requestSource=CSI

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.