Skip to main content
NetApp Knowledge Base

Trident FSX failing to attach PVC to pod due to locked snapshots

Views:
153
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Amazon FSx for NetApp ONTAP (FSxN)
  • Astra Trident
  • FSx automatic backups
  • OADP/Velero

Issue

  • When restarting pods, Persistent Volume Claims (PVCs) fail to attach.
  • Error message in kubectl describe pod events:
    Warning FailedAttachVolume attachdetach-controller Volume attachment is being deleted
  • Trident controller logs show repeated errors:level=error msg="Unable to delete snapshot from backend." error="snapshot snapshotname backing volume trident_pvc_... is busy"level=error msg="Could not begin splitting clone from snapshot." error="errorsplittingclone;APIState:failure,Message:[JobID]Job failed: Volume has locked snapshots"
  • EMS logs on FSxN show clone split failures:wafl.vv.clone.splitBusySnap: Volume has locked snapshots, not splitting.mgmtgwd.jobmgr.jobcomplete.failure: Job "CloneSplit" completed unsuccessfully: Volume has locked snapshots.

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.