This issue occurs when an ESX host is removed from an Enhanced VMotion Compatibility (EVC) cluster with powered on virtual machines still running on the ESX host.
To resolve the issue:
-
Add the ESX host back to the vCenter inventory outside of the EVC cluster.
-
VMotion the virtual machines from the ESX host, which is now outside to the EVC cluster, to ESX hosts which are in the EVC cluster. This ensures that there are no running virtual machines on the ESX host. For more information on VMotion, see the product documentation. -
When all the virtual machines are moved from the ESX host, add it back to the EVC cluster.
Note: This does not work to add virtual machines or an ESX host that was not part of the EVC cluster previously or if the virtual machines have been rebooted since being removed from the EVC cluster.