Skip to main content
NetApp Knowledge Base

Trident CSI Blocked by “Unable to delete snapshot from backend” Errors During OpenShift Virtualization VM Provisioning

  1. Last updated
  2. Save as PDF
Views:
24
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
SNAPX
Last Updated:

Applies to

  • NetApp ONTAP 9.13.1 and later (including 9.16.1P9)
  • NetApp Trident CSI (all supported versions, including 25.x and 26.x)
  • OpenShift Virtualization clusters using Trident for dynamic PVC provisioning
  • ONTAP FlexClone and snapshot workflows

Issue

Trident CSI operations become blocked, causing delays or failures in VM provisioning and PVC operations. The following repeated error messages are observed in Trident controller logs:

level=error msg="Unable to delete snapshot from backend." error="snapshot...backing volume...is busy"
level=error msg="Could not begin splitting clone from snapshot." cloneVolumeName=trident_pvc_<uuid> error="error splitting clone; could not find volume with name trident_pvc_<uuid>"

Symptoms include:

  • VM creation is slow or blocked in OpenShift Virtualization.
  • Trident controller pod logs are flooded with snapshot deletion and clone split errors.
  • The issue is only resolved after manual deletion of the problematic PVC and its backend volume in ONTAP.

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.