After upgrading your Virtual Center (vCenter) Server you may find that one or more of your ESX hosts in an HA cluster display the error message:

“An error occurred during configuration of the HA Agent on the host”.

When you look further into the ‘Task Details’ (assuming that you’ve already tried to ‘Reconfigure for VMware HA’ or similar in trying to resolve the issue) you may see the error:

“cmd addnode failed for primary node: /opt/vmware/aam/bin/ft_startup failed”

This is a known issue with VMware Virtual Center 2.5 Update 3 – see the U3 release notes here for confirmation. 

To resolve this error remove the HA from the cluster and then re-apply HA to it again.  When all ESX hosts in the cluster have had HA re-enabled you should see that the HA error previously seen has now gone.

This issue is still present with the recent Virtual Center 2.5 U4 release so you may still see it even after updating to this latest release.

Related posts:

1. VMware ESX – Prevented Migration due to “Device SCSI Controller is a SCSI controller engaged in bus-sharing” error When going to vMotion a server either manually, via...
2. HP ML110 G5 – Upgrading to VMware ESX/ESXi U4 and getting error: “The VMware ESX Server does not have persistent storage” VMware ESX/ESXi Update 4 (U4) has brought good and...
3. VMware vCenter agent service does not install or upgrade on ESXi 4.0 hosts – “Cannot install the vCenter agent service. Unknown Installer error” Here’s one for all you VMware ESXi users out...
4. VMware vSphere ESX 4 Error During Install – Booting: MBI=0×000100d8, entry=0×00100212   Maybe you’ve dug out that old server that...
5. VMware vSphere – Update Manager: “There are errors during the remediation operation” and Inaccessible VMs I recently went to upgrade one of my VMware...