Skip to main content
NetApp Knowledge Base

Unable to Provision GCNV Flex PVCs via Trident – “no GCNV storage pools found for Trident pool” Error

Views:
46
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident versions prior to 25.02
  •  Google Cloud NetApp Volumes (GCNV) Flex service level
  •  Kubernetes clusters (GKE) using Trident as a CSI provisioner
  •  StorageClass/TridentBackendConfig using zonal pools

Issue

Attempts to provision PersistentVolumeClaims (PVCs) from GCNV Flex zonal pools fail when using Astra Trident.

 Kubernetes events show provisioning failures:

Warning  ProvisioningFailed  csi.trident.netapp.io_trident-controller-xxxx  
failed to provision volume with StorageClass "trident-gcnv-flex":  
rpc error: code=Unknown desc=encountered error(s) in creating the volume:  
[Failed to create volume pvc-xxxx on storage pool gcp-gcnv-flex_pool_0 from backend <backend name>: no GCNV storage pools found for Trident pool gcp-gcnv-flex_pool_0]

  • Trident logs contain the same error string.
  • Creating Flex volumes via Google Cloud Console works without issue.
  • Standard (regional) GCNV pools provision successfully through Trident.
  • Only the Flex TridentBackendConfig specifies a zone; the standard config specifies a region.

 

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.