#25.10 NAS Import Volume with --no-rename

1 messages · Page 1 of 1 (latest)

gloomy wadi
#

We use latest Trident 25.10 and trying to import volume in "managed" mode but with "--no-rename" flag. Trident is still trying to rename volume.

we run:

tridentctl -n trident-operator import volume trident-backend-jaspershared iaa_pvc_test_jaspershared -f /tmp/pvc.yaml --debug --output wide --no-rename

trident does:

kubectl exec trident-controller-7c94ff558-rc8sv -n trident-operator -c trident-main -- tridentctl --debug --output wide import volume --base64 eyJhcGlWZXJzaW9uIjoidjEiLCJraW5kIjoiUGVyc2lzdGVudFZvbHVtZUNsYWltIiwibWV0YWRhdGEiOnsiYW5ub3RhdGlvbnMiOnsidHJpZGVudC5uZXRhcHAuaW8vc2hhcmVUb05hbWVzcGFjZSI6IioifSwibmFtZSI6InB2Yy1qYXNwZXJzaGFyZWQiLCJuYW1lc3BhY2UiOiJqYXNwZXJzaGFyZWQtdm9sdW1lIn0sInNwZWMiOnsiYWNjZXNzTW9kZXMiOlsiUmVhZFdyaXRlTWFueSJdLCJzdG9yYWdlQ2xhc3NOYW1lIjoidHJpZGVudC1iYWNrZW5kLWphc3BlcnNoYXJlZC1oZGQifX0= --no-rename trident-backend-jaspershared iaa_pvc_test_jaspershared

but then it is still trying to rename volume:

error attempting to rename volume iaa_pvc_test_jaspershared on backend trident-backend-jaspershared: volume iaa_pvc_test_jaspershared rename failed: API status: failed,

see more in attached rename.log

any ideas on what is going sideways here?

📎 rename.log
gloomy wadi
#

seems like a bug in the code. wondering how it was tested.

The --no-rename flag is not implemented in the CLI (cli/cmd/import_volume.go), even though:

The ImportVolumeRequest struct has NoRename field (storage/volume.go:233)
The VolumeConfig has ImportNoRename field (storage/volume.go:56)
The Kubernetes helper reads AnnImportNoRename annotation
The tests expect a 5-parameter volumeImport(... noManage, noRename, ...) function
But the actual CLI code:

Missing: importNoRename variable declaration
Missing: --no-rename flag registration in init()
Missing: noRename parameter in volumeImport() function
Missing: NoRename field assignment in the request
Missing: Tunneling --no-rename flag to the controller pod