Trident StorageClass “netapp-default” Stuck in Terminating State Blocks Provisioning
Applies to
- Trident
- OpenShift / Kubernetes clusters
Issue
- Trident was unable to provision new volumes.
- The Trident backend was online and healthy, but no storage classes were bound to discovered pools.
- The following errors were observed in the Trident controller logs:
time="2026-06-09T15:06:14Z" level=warning msg="K8S helper could not upsert a storage class." error="object is being deleted: tridentstorageclasses.trident.netapp.io \\"netapp-default\\" already exists" logLayer=csi_frontend name=netapp-default parameters="map[backendType:ontap-nas storagePools:<backend_name>:<aggregate_name>]" provisioner=csi.trident.netapp.io requestID=a19f88e4-f041-4f73-b25c-7830362cd482 requestSource=Kubernetes workflow="storage_class=create"
time="2026-06-09T15:06:15Z" level=info msg="Newly added backend satisfies no storage classes." backend=netapp-backend crdControllerEvent=add logLayer=core requestID=f6f4633a-36d6-4a6d-bcec-69b40d388786 requestSource=CRD workflow="cr=reconcile"
- Kubernetes command output shows that the Trident storage class is in a
Terminatingstate (a deletion timestamp exists with a finalizer):
$ oc get tridentstorageclass -n trident netapp-default -o yaml
apiVersion: trident.netapp.io/v1kind: TridentStorageClassmetadata: name: netapp-default deletionTimestamp: "2026-06-09T13:51:26Z" finalizers: - trident.netapp.io
