Skip to main content
NetApp Knowledge Base

TRID-20775: TRID-20775: Managed Import Stuck in Pending After Controller Restart

Views:
1
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Issue

Managed import of an existing ONTAP volume persists an importVolume transaction beforevolConfig.InternalName is computed and before the backend rename completes. If the trident-controller is replaced or restarted after ONTAP has already renamed the volume to the new internal name, bootstrap recovery cannot rename it back: resetImportedVolumeName / concurrent handleFailedTransaction call RenameVolume with an empty InternalName, log only at Debug (or fail silently), delete the transaction, and every subsequent CSI CreateVolume / ImportVolume retry looks for ImportOriginalName, which no longer exists on the array. The PVC stays Pending until someone manually renames the ONTAP volume back.

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.