Skip to main content
NetApp Knowledge Base

Trident Pool Information Not Updated After ONTAP Volume Move

Views:
3
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Trident
  • Trident deployments using TridentBackendConfig (TBC)
  • Environments with multiple aggregates in SVM aggr-list

Issue

After moving a Trident-managed ONTAP volume to a different aggregate, the backend pool information in Trident does not reflect the new aggregate location. This results in:

  • tridentctl get volume -n trident -o yaml continues to show the old aggregate.
  • Provisioning a new PVC may cause Trident to create a new FlexVol on the source aggregate, even if the moved volume has available qtree slots.
  • Attempts to manually update the backend with tridentctl update backend fail with:

Error: could not update backend NAS-HC-615: cannot update backend 'NAS-HC-615' created using TridentBackendConfigCR; please update the TridentBackendConfigCR (400 Bad Request)

  • Editing the TBC does not update pool information for the moved volume.
  • Both source and destination aggregates remain in the SVM aggr-list.

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.