Trident Pool Information Not Updated After ONTAP Volume Move
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.
