Skip to main content
NetApp Knowledge Base

Clone split does not complete in Trident

  1. Last updated
    May 12, 2025
  2. Save as PDF
Views:
19
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:
5/12/2025, 5:32:18 AM

Applies to

  • Astra Trident
  • NetApp ONTAP 9.x

Issue

Many split clone operations are stuck in Trident with the following traces:

time="YYYY-MM-DDThh:mm:ssZ" level=error msg="Could not begin splitting clone from snapshot." cloneVolumeName=trident_pvc_xxyyxxyy_xxyy_xxzz_zzyy_yyyyzzzzxxxx_xyxy error="error splitting clone: API status: failed, Reason: Volume trident_pvc_xxyyxxyy_xxyy_xxzz_zzyy_yyyyzzzzxxxx_xyxy is not online. It needs to be online for this operation. , Code: 13157" logLayer=core parentVolumeName=trident_pvc_7xxyyxxyy_xxyy_xxzz_zzyy_yyyyzzzzxxxx requestID=xxxxxxxx-yyyy-zzzz-xyxy-zxzxzxzxzxzx requestSource=CSI snapshotName=snapshot-zzyyzzyy-yyyy-xyxy-zxzx-yxyxzxzxxzxz workflow="snapshot=delete"

 

 

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.