vCenter instance missing from Web UI after configuring vCenter linking in VCF Operations

Products

• VMware vCenter Server

Issue/Introduction

• After configuring vCenter linking in VMware Cloud Foundation (VCF) Operations 9.1 and adding two vCenters with embedded vIDB from two different VCF instances, both vCenters display an 'Active' status. However, upon logging into the vCenter Web GUI of either instance, only one vCenter is visible. 
  
  
• The following errors are observed in var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log:
  

  YYYY-MM-DDThh:mm:ss.026Z ERROR vsphere-ui 23313 [vc@4413 threadName="data-notifications-worker-12817" logger="c.v.vise.mvc.notifications.AnnouncementsNotificationProvider"  ] Can't read announcements from vCenter with xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx guid com.vmware.vcenter.apigw.api.sso.tokenmgmt.TokenException: Failed to acquire token for domain <vCenter_2_FQDN>(xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx)
        at java.base/java.lang.Thread.getStackTrace(Unknown Source)
        at com.vmware.vapi.bindings.client.AsyncCallbackSyncAdapter.get_aroundBody1$advice(AsyncCallbackSyncAdapter.java:49)
        at com.vmware.vapi.bindings.client.AsyncCallbackSyncAdapter.get(AsyncCallbackSyncAdapter.java:1)
        at com.vmware.vapi.internal.bindings.Stub.invokeMethod(Stub.java:186)
        at com.vmware.vcenter.system.AnnouncementsStub.list(AnnouncementsStub.java:47)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.base/java.lang.reflect.Method.invoke(Unknown Source)

  Caused by: com.vmware.vcenter.apigw.api.sso.tokenmgmt.TokenException: Failed to acquire token for domain <vCenter_2_FQDN>(xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx)
        at com.vmware.vcenter.apigw.sso.tokenmgmt.impl.AsyncTokenProvider.acquireForeignTokenFromSsoAndScheduleRenewal(Unknown Source)
        at com.vmware.vcenter.apigw.sso.tokenmgmt.impl.AsyncTokenProvider.lambda$createAndRegisterForeignTokenAcquisitionUnit$7(Unknown Source)
        at java.base/java.util.concurrent.CompletableFuture.biApply(Unknown Source)
        at java.base/java.util.concurrent.CompletableFuture$BiApply.tryFire(Unknown Source)
        at java.base/java.util.concurrent.CompletableFuture$Completion.run(Unknown Source)
        at io.opentelemetry.context.Context.lambda$wrap$1(Context.java:212)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        ... 1 common frames omitted

 

Environment

VMware Cloud Foundation (VCF) Operations 9.1
VMware vCenter Server 9.1 with embedded vIDB

Cause

vCenter linking is unsupported for instances utilizing embedded identity brokers. 

Resolution

 

1. Deploy the standalone VCF Identity Broker appliance if connecting more than one VCF Instance to the VCF Identity Broker.

2. Ensure that a common Identity Provider (IDP) is configured across all vCenter systems.

 

Additional Information

Linking vCenter instances in VCF Operations

Deployment Modes of the VCF Identity Broker