Skip to main content
NetApp Knowledge Base

Unlike new PVs created, imported volume do not create an InternalID reference

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

Applies to

Trident for Kubernetes and Openshift 25.06.0 and 25.06.1

Issue

When using a backend to create new PVs for ONTAP based volumes and LUNs, the main definition of the PV contains an InternalID in the volumeAttributes.
This contains information about the SVM, VOlume, and if used, the LUN or qtree.
 
However, if this was a Retain type PV, and the PVC and PV are deleted, the remaining volume can be re-imported into the backend, in which case there is no InternalID in that section.
 
Note: the creation of an internalID was added from version 25.06.0 on due to a customer request.

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.