This is a known issue affecting VMware vCenter Server Appliance 6.5.
Currently, there is no resolution.
To work around this issue, use one of these below options.
- Change the file permission of /etc/vmware/.buildInfo to 444:
- Log in to vCenter Server Appliance as root.
- Change the file permission of /etc/vmware/.buildInfo from 640 back to 444 by running this command:
chmod 444 /etc/vmware/.buildInfo
- Replace the Machine SSL certificate.
- Disable the VMware Update Manger service and replace the certificates:
- Take a backup of your SSO domain (PSC(s), vCenter Server(s), etc.).
- Disable the VMware Update Manager Service.
- Log in to the vCenter Server using the vSphere Web Client.
- On the vSphere Web Client Home page, click System Configuration.
- Under System Configuration, click Services.
- From the Services list, right-click the VMware vSphere Update Manager service.
- Navigate to Start up Policy > Disabled.
- Re-try to replace the SSL certificates.
For more information, see Configuring the vSphere 6.0 U1b or later VMware Certificate Authority as a Subordinate Certificate Authority(2147542).
- Re-enable the VMware Update Manager Service.
- Log in to the vCenter Server using the vSphere Web Client.
- On the vSphere Web Client Home page, click System Configuration.
- Under System Configuration, click Services.
- From the Services list, right-click the VMware vSphere Update Manager service.
- Navigate to Start up Policy > Automatic
- Connect to the vCenter Server using SSH and run the following commands:
/usr/lib/vmware-updatemgr/bin/updatemgr-util refresh-certs
/usr/lib/vmware-updatemgr/bin/updatemgr-util register-vc
service-control --start vmware-updatemgr
-
Verify that VMware Update Manager is accessible in the vSphere Web Client.