Skip to main content
NetApp Knowledge Base

Trident Volume Cloning Fails Across Different Storage Classes After Upgrade

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

Applies to

  • NetApp Trident CSI (Kubernetes/OpenShift environments)
  • Trident versions 25.06.1 and later
  • ONTAP storage backends
  • Kasten backup integration
  • Environments using multiple storage classes with different reclaim policies

Issue

After upgrading Trident from version 23.04.0 to 25.06.2, attempts to clone a PVC (Persistent Volume Claim) from a source volume to a destination volume with a different storage class fail. This impacts workflows such as Kasten backups that create temporary volumes using a different storage class (e.g., for different reclaim policies).

Log Output Example:

Warning ProvisioningFailed 20s (x12 over 5m48s) csi.trident.netapp.io_trident-controller-xxxx failed to provision volume with StorageClass "<StorageClass name>": rpc error: code=Unknown desc=clone volume pvc-xxx from source volume pvc-yyy with different storage classes is not allowed.

 

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.