Config drift fails at persist active uplinks from vCenter Server

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

Config drift fails with following error:

2022-11-03T13:14:04.516+0000 ERROR [vcf_migration,0000000000000000,0000] [c.v.e.s.o.model.error.ErrorFactory,pool-5-thread-18] [CL5BGP] PERSIST_ACTIVE_UPLINKS_IN_SDDC_MANAGER_INVENTORY_FAILED Failed to persist active uplinks data from vCenter Server <vCenter Server name goes here> to the SDDC Manager Inventory.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to persist active uplinks data from vCenter Server <vCenter Server name goes here> to the SDDC Manager Inventory.
...
Caused by: java.lang.IllegalArgumentException: Expect 1 but 0 found for DistributedVirtualSwitch:<VDS name goes here>
 at com.vmware.evo.sddc.common.client.vmware.vsphere.InventoryService.getUniqueByName(InventoryService.java:315)
 at com.vmware.evo.sddc.common.client.vmware.vsphere.VcManagerBase.getMorByTypeAndName(VcManagerBase.java:6132)
 at com.vmware.evo.sddc.common.client.vmware.vsphere.VcManagerBase.getDvsMor(VcManagerBase.java:6153)

 

Cause

This issue is seen when a VMware vSphere Distributed Switch (VDS) has been renamed outside of VCF from vCenter and after such rename the config drift is run.

Resolution

The issue will be resolved in future releases.

To workaround the issue, change the VDS name in the vCenter Server to match the original value from the SDDC Manager. The name of the VDS is part of the exception message where we can see "Expect 1 but 0 found for DistributedVirtualSwitch:<the expected and original VDS name will be here>". Once the original VDS name has been copied  please refer to Renaming a VMware VDS/dvPortGroup while virtual machines are connected to change the VDS name in the vCenter Server.