Trident Volumes Remain in Released State and Aggregate Volume Count Reaches Maximum Limit on NetApp ONTAP
Applies to
- Kubernetes/OpenShift environments using Trident for dynamic provisioning
- Commvault backup workflows integrated with Trident
Issue
Trident-provisioned volumes used for Commvault backups remain in the “Released” state in OpenShift and are not deleted from ONTAP backend storage, causing the aggregate to reach the maximum volume limit (e.g., 2,500 volumes). As a result, new volume provisioning fails with errors similar to:
Warning ProvisioningFailed csi.trident.netapp.io_trident-controller-XXXX failed to provision volume with StorageClass "ontap-nas-cb": rpc error: code=Unknown desc=failed to create cloned volume pvc-XXXXX on backend ontapnas_XX.XX.XX.XX: error creating clone: API status: failed, Reason: Failed to create the clone volume. Reason: Maximum number of volumes reached on node "csntap03ka".., Code: 13114
or
Warning ProvisioningFailed csi.trident.netapp.io_trident-controller-XXXX failed to provision volume with StorageClass "ontap-nas": rpc error: code=Unknown desc=clone volume pvc-XXXXX from source volume pvc-YYYYY with different storage classes is not allowed
