Symptoms:
- Attempting a migration of an NSX-V backed Org VDC to an NSX-T backed Org VDC fails when using VMware NSX Migration for VMware Cloud Director.
- The migration attempt fails with an error in the VCD-NSX-Migrator-Main-<DATE>.log similar to the following:
2023-08-01 10:08:13,244 [vcdOperations]:[prepareTargetVDC]:3381 [ERROR] [<ORG_VDC_NAME>] | Traceback (most recent call last):
File "src\core\vcd\vcdOperations.py", line 3368, in prepareTargetVDC
File "src\core\vcd\vcdValidations.py", line 150, in wrapped
File "src\core\vcd\vcdValidations.py", line 90, in inner
File "src\core\vcd\vcdValidations.py", line 80, in inner
File "src\core\vcd\vcdOperations.py", line 5117, in getPromiscModeForgedTransmit
Exception: Failed to get dvportgroup properties of source Org VDC network <DVPG_NAME>
- The VCD-NSX-Migrator-Main-<DATE>.log shows a 500 None response to a GET /cloudapi/1.0.0/orgVdcNetworks/<NETWORK_UUID>/dvpgProperties API call from the VMware NSX Migration for VMware Cloud Director to the Cloud Director:
[connectionpool]:[_make_request]:452 [DEBUG] [<ORG_VDC_NAME>] | https://<VCD_URL>:443 "GET /cloudapi/1.0.0/orgVdcNetworks/<NETWORK_UUID>/dvpgProperties
- Performing the same API call to the Cloud Director outside of VMware NSX Migration for VMware Cloud Director results in "DV_PORTGROUP_DOES_NOT_EXIST" response:
Distributed virtual port group \"(moref: <DVPG_MOREF>)\" does not exist."
- When browsing https://<VC_URL>/mob/?moid=<DVPG_MOREF> in the vCenter Managed Object browser the page cannot be found for the <DVPG_MOREF> in the error.
- When checking in vCenter the Distributed Port Group name reported in the errors/logs is present but the Managed Object Reference (moref) is different from the one reported.