Cohesity Backup Fails Due to Trident Snapshot Deletion Issues in Kubernetes Environments
Applies to
- NetApp Trident 26.2.0 and later
- Kubernetes clusters with CSI/Trident provisioned volumes
- Cohesity backup integration with Kubernetes PVCs
- Customers using volume cloning and snapshot-based backup workflows
Issue
Cohesity backup operations in Kubernetes environments using NetApp Trident fail due to snapshot deletion errors. The following log output is observed:
time="2026-04-09T16:49:16Z" level=debug msg="Could not delete the snapshot, going to check if it's busy; error was: APIState: failure, Message: Snapshot \\"snapshot-134a21a1-fd99-433a-817d-b9c553acb2ad\\" of volume \\"<ONTAP volume name>\\" in Vserver \\"<vserver name>\\" has not expired or is locked. Use the \\"snapshot show -fields owners, expiry-time, snaplock-expiry-time\\" command to view the expiry and lock status of the snapshot., Code:1638555" logLayer=core requestID=fc03abe3-8cc6-4189-b2ec-2d80ca782498 requestSource=CSI workflow="snapshot=delete"
Symptoms include:
- Snapshot deletion requests fail with “snapshot is locked or has not expired”
- Snapshots remain in a “busy” state due to backing clone volumes (PVCs from snapshots)
- Trident retries snapshot deletions, leading to delayed or stalled backup and snapshot operations
- Additional provisioning or cleanup operations are delayed or stalled
