vCenter registered to vCenter Cloud Gateway without DNS fails in Check Pre-requisite in vSphere+
search cancel

vCenter registered to vCenter Cloud Gateway without DNS fails in Check Pre-requisite in vSphere+

book

Article ID: 304812

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

While performing vCenter upgrade in vSphere+ (via VMware Cloud Console) 'Check Pre-requisite' may fail if vCenter was registered in vCenter Cloud Gateway with vCenter IP and no DNS.


Symptoms:

Error message on UI: No history returned from VC patch history API.


Cause

This occurs due to lack of vCenter Cloud Gateway IP in SAN field of vCenter Cloud Gateway certificate.

Resolution

Follow the below mentioned steps:

1. Update /etc/hosts file in vCenter with vCenter Cloud Gateway IP and vCenter Cloud Gateway hostname.
Example:
GW IP: <IP>
GW FQDN: <FQDN>

Add above mapping in the hosts file and it should show entry as below:
root@localhost [ /etc ]# cat hosts
# Begin /etc/hosts
(network card version)

<IP> <FQDN>
127.0.0.1 localhost.localdomain
127.0.0.1 localhost


2. Login to vCenter cloud Gateway and copy vCenter Cloud Gateway certificate(server.crt) from path: /etc/applmgmt/appliance/server.crt to vCenter at path: /usr/lib/vmware-vmafd/bin

3. Run dir-cli command to publish the server.crt in vCenter (Reference: dir-cli Command Reference)

Example:
root@localhost [ /etc ]# /usr/lib/vmware-vmafd/bin/dir-cli trustedcert publish --cert /usr/lib/vmware-vmafd/bin/server.crt
Enter password for [email protected]:
Certificate published successfully.

4. Re-run check pre-requisite.