Error: "The VMware Cloud Director Availability vSphere Client Plug-In was not installed successfully."

Products

• VMware Cloud Director

Issue/Introduction

• When configuring the Lookup Service address in a Cloud Director Availability On-Premises appliance, you see a message similar to:

The VMware Cloud Director Availability vSphere Client Plug-In was not installed successfully.

• In the /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log on the vCenter Server, you see entries similar to:

[2023-11-17T15:23:04.602Z] [INFO ] plugin-discovery-bus-thread com.vmware.vise.plugin.registry.VcExtensionRegistryImpl Associated plugin com.vmware.vcda.plugin:4.6.0.6869101 with VC vcenter.example.com with guid F5E75537-5326-43A3-A64D-E62DF931D700.
[2023-11-17T15:23:04.603Z] [INFO ] plugin-discovery-bus-thread com.vmware.vise.vim.extension.VcExtensionManager Updating plugin package com.vmware.vcda.plugin:4.6.0.6869101 to: name = VMware Cloud Director Availability On-Premises Plugin, description = DRaaS and Migration between vSphere and vCloud Director sites, vendor = VMware, Inc.
...
[2023-11-17T15:33:31.758Z] [INFO ] http-nio-5090-exec-1070 70115245 111694 201133 com.vmware.vise.mvc.controllers.PluginServiceController Fetching session for remote plugin with ref com.vmware.vcda.plugin:4.6.0.6869101:1700964757
[2023-11-17T15:33:31.832Z] [WARN ] http-nio-5090-exec-1090 com.vmware.vsphere.client.rest.VcSessionShimController Plugin packageRef = com.vmware.vcda.plugin:4.6.0.6869101, manifestUrl = https://192.0.2.10:443/ui/vsphere-signed-plugin.zip requested access to vCenter with GUID f5e75537-5326-43a3-a64d-e62df931d700 which is not permitted.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Director Availability 4.x

Cause

This issue is caused due to the vCenter Server having an uppercase GUID. The Cloud Director Availability vSphere Client Plug-In is unable to handle an uppercase GUID and instead attempts to create a cloning session for a lowercase GUID which is then rejected by the vCenter Server.

Resolution

This is a known issue affecting Cloud Director Availability 4.x.
Currently, there is no resolution.

Additional Information

To confirm if your vCenter Server has an uppercase GUID, navigate to the following address and review the instanceUuid property:
https://vcenter.example.com/mob/?moid=ServiceInstance&doPath=content.about