Skip to main content
NetApp Knowledge Base

Trident PVC deployment fails with topology set on worker nodes

  1. Last updated
  2. Save as PDF
Views:
29
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

Trident for Kubernetes and Openshift

Issue

Despite having setup topology on the worker nodes, when attempting to provision a POD or PVC (even if they do not use topology), the following error occurs on the PVC:

csi.trident.netapp.io_trident-controller-<POD_IDENTIFIER> failed to provision volume with StorageClass "<STORAGE_CLASS>": error generating accessibility requirements: no available topology found

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.