-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
2.9.0
-
Quality / Stability / Reliability
-
False
-
-
True
-
-
...After renaming a VM using the vSphere UI, the storage-offload process fails with the error:
"Failed to find VM <old-vm-name>" and "Failed to find the VMDK file".
W0611 09:11:36.980050 1 client_config.go:618] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work. I0611 09:11:37.050909 1 vsphere-xcopy-volume-populator.go:162] the volume name is not found on the claim "500gb-1vm-500gb-70usage-b95c238b". Trying the prime pvc "prime-fdb31a02-6547-4196-a2c9-e12ae6bd98e0" I0611 09:11:37.054278 1 vsphere-xcopy-volume-populator.go:179] target volume pvc-7180f834-cf38-466c-bf53-a6c1f62047f9 volumeHandle pvc-7180f834-cf38-466c-bf53-a6c1f62047f9 I0611 09:11:37.330836 1 remote_esxcli.go:70] Starting to populate using remote esxcli vmkfstools, source vmdk [v2v_general_porpuse_ISCSI_DC] 500gb-70usage_1/500gb-70usage_3.vmdk target LUN pvc-7180f834-cf38-466c-bf53-a6c1f62047f9 I0611 09:11:37.331215 1 vsphere-xcopy-volume-populator.go:273] Starting metrics server I0611 09:11:37.370052 1 vsphere-xcopy-volume-populator.go:127] channel quit Failed to find VM 500gb-70usage_1: vm '500gb-70usage_1' not found F0611 09:11:37.370073 1 vsphere-xcopy-volume-populator.go:129] Failed to find VM 500gb-70usage_1: vm '500gb-70usage_1' not found .
Expected Behavior:
The storage-offload process should locate and handle the VM/VMDK file correctly, even after the VM name is changed in the vSphere UI.
Current Behavior:
The operation fails because the process looks for the VM using the old name, which no longer exists in vSphere after manual renaming.
Recommendation / Suggested Fix:
The tool should use the VM's UUID or MOID (Managed Object ID) instead of relying solely on the VM name, as names are mutable and subject to change by users.
