Trident is Unable to delete snapshot from backend, causing PVC to hang in terminating
Applies to
- Trident for Kubernetes/Openshift up to 21.07.1
- Astra Trident for Kubernetes/Openshift 21.10.0 and higher
- CommVault for Kubernetes
- VSERVER-DR or MCC (Metrocluster)
Issue
The following errors occur while Trident is attempting to delete the snapshots on the PV volume, so the volume can be deleted:
time="<DATETIME>" level=info msg="Determined topology labels for node: map[]" node=<K8S_NODE_N> requestID=<UUID> requestSource=REST
time="<DATETIME>" level=error msg="Could not begin splitting clone from snapshot."
cloneVolumeName=<FLEXCLONE_PVC_NAME>
error="error splitting clone: API status: failed,
Reason: This volume cannot be split as it is configured for protection using Vserver level snapmirror.
Change the protection type using \"volume modify\" command to make it unprotected., Code: 13001"
parentVolumeName=<VOLUME_PVC_NAME> requestID=<UUID>
requestSource=CSI snapshotName=snapshot-<UUID>
time="<DATETIME>" level=error msg="Unable to delete snapshot from backend." backend=<BACKEND_NAME>
error="snapshot snapshot-<UUID> backing volume <VOLUME_PVC_NAME> is busy" requestID=<UUID>
requestSource=CSI snapshot=snapshot-<UUID> volume=<PVC-NAME>