Skip to main content
NetApp Stage KB

PVCs are hanging in termination due to the PV's ONTAP volume not being deleted

Last Updated:

Applies to

Trident for Kubernetes/Openshift


After having created a Kubernetes/Trident Snapshot and from that, a Kubernetes PVC clone to be used for another pod,
terminating the original pod, and deleting its PVC does not fully clean up the PV information in trident.

The deletion fails due to the clone-busy Snapshot showing at least two errors:
  1. type: 'Warning' reason: 'VolumeFailedDelete' persistentvolume pvc-UUID is still attached to node WORKER_NODE
  2. API status: failed, Reason: Failed to delete volume \"trident_PREFIX_pvc_UUID\" in Vserver \"VSERVER\" because it has one or more clones.\n\nUse the \"volume clone show -parent-vserver VSERVER -parent-volume trident_PREFIX_pvc_UUID\" command to list clones, and either delete or split the clones and retry the operation.\n\nUse \"volume clone split start -vserver \u003cvserver name\u003e -flexclone \u003cclone name\u003e\" to split clones.\nUse \"volume delete -vserver \u003cvserver name\u003e -volume \u003cclone name\u003e\" to delete clones., Code 15894","level":"error","message":"Unable to delete volume from backend."

Additionally, the PVCs show as released in the output "oc|kubectl get pvc -o wide".

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.