Skip to main content
NetApp Knowledge Base

PVC Provisioning Fails in OpenShift with Trident: “could not find aggregate, cannot check aggregate provisioning limits” After Aggregate Removal

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

Applies to

  • NetApp ONTAP 9.x (Cluster Mode)
  • NetApp AFF-A900
  • NetApp Trident (v22.01.x and similar)
  • OpenShift or Kubernetes clusters using Trident for dynamic provisioning

Issue

New Persistent Volume Claims (PVCs) remain in Pending state and fail to provision with errors similar to:

Warning  ProvisioningFailed  m  csi.trident.netapp.io  failed to provision volume with StorageClass "sc_name": rpc error: code = Unknown desc = encountered error(s) in creating the volume: [Failed to create volume pvc-xxxxxxxx on storage pool aggr_01 from backend backend_name: backend cannot satisfy create request for volume ... (ONTAP-NAS-QTREE pool aggr_01/aggr_02; error: could not find aggregate, cannot check aggregate provisioning limits for aggr_02)]
  • All new volume creation requests fail.
  • Existing volumes and already-bound PVCs are unaffected.
  • Trident logs indicate missing aggregates referenced in backend configuration.
  • ONTAP cluster recently had aggregates (e.g., aggr_01, aggr_02) removed after volume migration.

 

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.