Unable to remove existing identity broker AD over LDAP , fails with error:" Not able to initiate ApiClient for endpoint VC_IP"

Products

• VMware SDDC Manager

Issue/Introduction

• Removing identity broker fails with error 

Saving configuration settings failed with the following error:
Not able to initiate ApiClient for endpoint VC_IP

• /storage/log/vcops/log/license-usage-plugin.log from VCF Operations Manager reports below error

YYYY-MM-DDTHH:MM:SS.543Z INFO  license-usage-plugin 24116 [ops@4413 threadId="4624" threadName="ServerConnection on port 10000 Thread 13"] [com.vmware.vrops.license.usage.server.B.slu] - vui: VUI(vcHostname=VC_IP, vcAdapterName=VC_Adapter_Name, vcUUID=2ba9bce9-####-####-####-45d44e396e21, assetsWithoutLicensedCount=0, usage=[LU(usageType=ALLOCATION_ID, licenseName=null, productId=null, productName=null, usage=0, totalLimit=0, costUnitId=null, expirationDate=0, productFamilyName=vSAN, productFamilyVersion=9.0, allocationId=982426a6-####-4875-####-2b4f234e7239, allocationUsageByUnit={cpuPackage:32core=8, vm=0, TiB=5, cpuCore:16core=256}, assetsCount=1), LU(usageType=ALLOCATION_ID, licenseName=null, productId=null, productName=null, usage=0, totalLimit=0, costUnitId=null, expirationDate=0, productFamilyName=vSphere, productFamilyVersion=9.0, allocationId=8e4528fc-####-45d9-####-########, allocationUsageByUnit={cpuPackage:32core=8, cpuCore:8core=256, vm=6, TiB=8, cpuCore:16core=256}, assetsCount=4)], collectionTime=########, vcfAdapterName=null)

• Above log also reports presence of another registration for the same VC as below:

YYYY-MM-DDTHH:MM:SS.571Z INFO  license-usage-plugin 24116 [ops@4413 threadId="4624" threadName="ServerConnection on port 10000 Thread 13"] [com.vmware.vrops.license.usage.server.B.slu] - vui: VUI(vcHostname=VC_FQDN, vcAdapterName=VC_FQDN, vcUUID=2ba9bce9-####-########-####-45d44e396e21, assetsWithoutLicensedCount=0, usage=[LU(usageType=ALLOCATION_ID, licenseName=null, productId=null, productName=null, usage=0, totalLimit=0, costUnitId=null, expirationDate=0, productFamilyName=vSAN, productFamilyVersion=9.0, allocationId=982426a6-####-####-####-2b4f234e7239, allocationUsageByUnit={cpuPackage:32core=8, vm=0, TiB=5, cpuCore:16core=256}, assetsCount=1), LU(usageType=ALLOCATION_ID, licenseName=null, productId=null, productName=null, usage=0, totalLimit=0, costUnitId=null, expirationDate=0, productFamilyName=vSphere, productFamilyVersion=9.0, allocationId=8e4528fc-####-45d9-####-####, allocationUsageByUnit={cpuPackage:32core=8, cpuCore:8core=256, vm=6, TiB=8, cpuCore:16core=256}, assetsCount=4)], collectionTime=########, vcfAdapterName=VCF_Instance_name)

Environment

VMware Cloud Foundation 9.0.1

Cause

This issue occurs when both the VCF adapter and the vCenter adapter are redundantly registered for the same vCenter instances. In VCF deployments, the VCF adapter automatically discovers and manages the associated vCenter instances, so registering a separate vCenter adapter is unnecessary and may lead to configuration conflicts.

Resolution

To fix this remove the unnecessary registration. Login to VCF operations UI

1. Go to Administration -> Integration -> Accounts 
2. Delete vCenter Account with vcAdapterName 'Duplicate_name' (Enabling option - Delete related objects).
3. Delete (VMware Cloud Foundation) VCF account with vcfAdapterName 'VCF_Instance_name' (Enabling option - Delete related objects).
4. Delete vSAN Adapter, NSX, vCenter Adapter (if still exists) with enabling option - Delete related objects
5. Now the account page will not have any Adapters listed. 
6. Click Add -> VMware Cloud Foundation -> add vcf adapter and validate connection accepting the certificates -> save. 
7. Click on vcf adapter registered and start collecting all. Wait for few minutes.