Cannot connect to Lookup Service at 'https://x.x.x.x:443/lookupservice/sdk'. Make sure the address is correct and accessible.
replicator.log
(/opt/vmware/h4/replicator/logs/replicator.log
):2024-10-18 17:52:24.217 ERROR - [UI-########-####-####-####-#############-##-##] [https-jsse-nio-8441-exec-6] c.v.h4.common.service.BaseConfigService : Failed to connect to lookup service at https://192.x.x.x:443/lookupservice/sdk.
com.vmware.exception.DnsResolutionException: xxxx.xxxxx.xxx: Temporary failure in name resolution
...
Caused by: com.vmware.vim.vmomi.client.exception.ConnectionException: https://xxxx.xxxxx.xxx/sso-adminserver/sdk/vsphere.local invocation failed with "java.net.UnknownHostException: xxxx.xxxxx.xxx: Temporary failure in name resolution"
at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:261)
... 144 common frames omitted
Caused by: java.net.UnknownHostException: xxxx.xxxxx.xxx: Temporary failure in name resolution
...
VMware Cloud Director Availability 4.x
VMware Cloud Director Availability is attempting to connect to the vCenter server, but is unable to resolve the address. In cases where the IP address is configured, the vCenter lookup service will provide the service locations for various services, which can include the fully qualified domain name and still require the correct name resolution.
Update the network configuration on the vCDA appliance so that it can resolve the vCenter address without issue.
If the environment uses the .local
top level domain (e.g., vsphere.local
), additional steps are required to enable resolution to work correctly, as noted in the following:
How to use local as a Top-Level Domain in vCloud Availability appliances