Error: "A specified parameter was not correct: relocateSpec.deviceChange.device" when performing NSX-V to NSX-T migration

Products

• VMware Cloud Director

Issue/Introduction

• Perform NSX-V to NSX-T migration using VMware NSX Migration for VMware Cloud Director.
• During migration, when migrating the vApp from the source Org VDC to the destination Org VDC the following error is seen

YYYY-MM-DD HH:MM:SS [threadUtils]:[_runThread]:79 [DEBUG] [Lelanet] | Traceback (most recent call last):

File "src\commonUtils\threadUtils.py", line 66, in _runThread

File "src\core\vcd\vcdValidations.py", line 53, in inner

File "src\core\vcd\vcdOperations.py", line 4987, in moveVappApiCall

File "src\core\vcd\vcdValidations.py", line 53, in inner

File "src\core\vcd\vcdValidations.py", line 4532, in _checkTaskStatus

Exception: [ UUID ] Internal Server Error

• From the VCD UI, you see the below error:

A specified parameter was not correct: relocateSpec.deviceChange.device Relocate operation for VM <VM_name> failed because modifying any property other than the network backing of device 4000 is not allowed via relocateSpec.

• From the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log, you see the below error:

com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Internal Server Error

at com.vmware.vcloud.common.future.FutureUtil.convertExecutionException(FutureUtil.java:233)

at com.vmware.vcloud.common.future.FutureUtil.convertExecutionException(FutureUtil.java:202)

...

Caused by: com.vmware.vcloud.vdc.impl.LinkVMsToTargetVAppActivity$LinkVMsToVAppException: VM <VM_name>(UUID) failed to update and has been rolled back. null Task failed, vc-id={UUID}, task-moref={ManagedObjectReference: type = Task, value = task-xxxxx, serverGuid = null}, error={A specified parameter was not correct: relocateSpec.deviceChange.device} 

at com.vmware.vcloud.vdc.impl.LinkVMsToTargetVAppActivity$DelinkVAppVMsToTargetVAppPhase.invoke(LinkVMsToTargetVAppActivity.java:619)

... 7 more

Environment

VMware Cloud Director 10.x

Cause

This is a known issue in Cloud Director caused when the MAC address is set to Automatic.

Resolution

To workaround this issue, change the MAC address type of the affected VMs' NICs from Automatic to Manual