vSphere HA not enabling after vCenter upgrade
search cancel

vSphere HA not enabling after vCenter upgrade

book

Article ID: 412229

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • After vCenter has been updated either by patching a minor build or a full version upgrade the FDM (Fault Domain Manager) Agent will also get updated and will need to be pushed down to the ESXi hosts where vSphere HA is enabled.
  • If the cluster is being managed by a single image, the cluster will need to successfully pass a compliance check first before the new FDM Agent is added to add-on components to the image.

Cause

If there are compliance check issues on the cluster the FDM Agent will not get installed, one issue could be an inaccessible update depot.

 

As seen in the /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log file, we can no longer access hostupdate.vmware.com as it has been decommised and outlined in here: VCF authenticated downloads configuration update instructions

YYYY-MM-DDTHH:MM:SS.SSSZ warning vmware-vum-server[241568] [Originator@6876 sub=VumVapi::Lib::Utils] [EmbeddedPyServiceProvider 472] Connecting to https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/vmw-depot-index.xml failed, err: curl_easy_perform() failed: cURL Error: Couldn't resolve host name, Could not resolve host: hostupdate.vmware.com
YYYY-MM-DDTHH:MM:SS.SSSZ warning vmware-vum-server[241568] [Originator@6876 sub=VumVapi::Lib::Utils] [EmbeddedPyServiceProvider 425] Failed 10 times when connecting online depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/vmw-depot-index.xml
YYYY-MM-DDTHH:MM:SS.SSSZ error vmware-vum-server[241568] [Originator@6876 sub=ServiceProvider] [EmbeddedPyServiceProvider 1570] At least one online depot is not accessible: https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/vmw-depot-index.xml, https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml, https://hostupdate.vmware.com/software/VUM/PRODUCTION
/iovp-main/vmw-depot-index.xml, https://hostupdate.vmware.com/software/VUM/PRODUCTION/vmtools-main/vmw-depot-index.xml
YYYY-MM-DDTHH:MM:SS.SSSZ error vmware-vum-server[241568] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SyncDepotsTask] [SyncDepotsTask 221] Failed to sync depots. Merged depot content is invalid: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError<A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot.>
-->

Resolution

  1. Disable the hostupdate.vmware.com depots as outlined here: How to disable the hostupdate.vmware.com depots
  2. Perform an Updates Sync
  3. Go to the cluster(s) in question > Updates
  4. Run a Compliance Check and verify it passes now
  5. Go to Configure > vSphere Availability > vSphere HA > Edit
    1. If enabled, disabled it and wait for all tasks to finish
    2. Enable vSphere HA

After enabling vSphere HA the updated FDM Agent should now be listed in the Add-on Components of the update image.