Symptoms
When you navigate to the Cloud Director Availability vSphere Client Plug-In, it fails to load and you see an error similar to:
no healthy upstream
This issue occurs when you are using the Cloud Director Availability vSphere Client Plug-In for a vSphere DR and migration deployment of Cloud Director Availability.This issue occurs when you have multiple vCenter Replication Management Appliances registered in the same site.
Cause
This issue occurs when the initially registered vCenter Replication Management Appliance becomes unavailable causing all Cloud Director Availability vSphere Client Plug-Ins registered in the same site inaccessible.
Resolution
This is a known issue affecting the Cloud Director Availability vSphere Client Plug-In.Currently, there is no resolution.
Workaround
To work around this issue, ensure that the initially registered vCenter Replication Management Appliance is powered on and operational.If the initially vCenter Replication Management Appliance no longer exists in the site, you can work around this by unregistering the Cloud Director Availability vSphere Client Plug-In and re-registering it with the existing vCenter Replication Management Appliances.
Log into the Manage Object Browser using vSphere administrator credentials:
https://vc_address/mob/?moid=ExtensionManager&method=unregisterExtension
Enter com.vmware.vcda.plugin into the extensionKey parameter value field.Click Invoke Method to unregister the VCDA extension.Log into the vCenter Replication Management Appliance Admin Portal as the root user.In the left pane click Settings.In the Service endpoints section, click Edit for the Lookup Service address field.In the new window, enter the vSphere administrator credentials and click Apply.Repeat steps 4-8 for all other active vCenter Replication Management Appliances.Navigate to the vSphere Client and confirm that the Cloud Director Availability vSphere Client Plug-In has been redeployed and is functional again.
