Skip to main content
NetApp Knowledge Base

Trident controller pod stuck in crashloopbackoff due to error splitting clone

  1. Last updated
  2. Save as PDF
Views:
117
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

  • Trident
  • Rubrik

Issue

Trident controller pod is stuck restarting going into a crashloopbackoff state and from the trident controller the errors are seen.
 
GRPC error: rpc error: code = Unknown desc = snapshot backing volume  is busy 
metadata.finalizers: "trident.netapp.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers
level=error msg="Could not begin splitting clone from snapshot." cloneVolumeName=clonevolname error="error splitting clone; could not find volume with name "  parentVolumeName=volname requestSource=CSI snapshotName=snapname workflow="snapshot=delete"
level=warning msg="Retried locked snapshot delete, clone split failed, restarted timer." logLayer=core requestSource=CSI secondsBeforeSplit=10.00 snapshot=snapshotname workflow="snapshot=delete"
level=error msg="Unable to delete snapshot from backend." 

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.