Search the VMware Knowledge Base (KB)
View by Article ID

"No supported hosts found for remediate" error during an ESX/ESXi host remediation (1024331)

  • 50 Ratings

Symptoms

  • The ESX/ESXi host remediation using VMware vCenter Update Manager fails.
  • You see the error:
No supported hosts found for remediate

The operation is not supported on the selected Inventory objects.
Check the events for the objects selected for the operation.

  • In the C:\Documents and Settings\All Users\Application Data\VMware\Update Manager or C:\Users\All Users\VMware\VMware Update Manager\Logs\vmware-vum-server-log4cpp.log file, you see an entry similar to:

    "[DATE'VciHostRemediateTask.VciHostRemediateTask{14}' 2276 INFO] [vciHostRemediateTask, 1313] Skipping [HostName] as it is part of HAC enabled cluster"

  • When trying to remediate an ESX host, it may fail with the error:

    There are errors during the remediation operation. Check the Tasks and Events tab and log files for details.

  • Remediate entry in Events, you see the error:

    Cannot remediate host "hostname" because it is a part of a HA admission control enabled cluster.

Cause

This issue occurs because the admission control policy that is set is preventing vCenter Update Manager from remediating the host.

vCenter Server uses admission control to ensure that sufficient resources are available in a cluster to provide failover protection and to ensure that virtual machine resource reservations are respected. Admission control imposes constraints on resource usage and any action that would violate these constraints is not permitted. If an automated process needs to take actions, it may temporarily violate the failover constraints. For example, as part of an upgrade directed by VMware vCenter Update Manager.

Resolution

To resolve this issue, you can either disable strict admission control or disable VMware HA altogether, put the ESX/ESXi host in the maintenance mode, and then continue with the upgrade.
 
To disable strict admission control:
  1. Right-click the cluster and click Edit Settings.
  2. Under Cluster Features, click VMware HA.
  3. Under Admission Control, select Disable: Power on VMs that violate availability constraints.
  4. Click OK.
To disable VMware HA:
  1. Right-click the cluster and click Edit Settings.
  2. Under Cluster Features, select Turn off VMware HA.
  3. Click OK.

After the ESX/ESXi host is successfully remediated, re-enable VMware HA on the cluster in the event of future host failovers.

Additional Information

Note: If you do not want to disable the strict admission control or HA at the cluster level, use this alternative workaround to resolve the issue.
  1. Create a new Test Cluster in the Datacenter.
  2. Move the ESX host being remediated into the new Cluster.
  3. Remediate the host.
  4. If the remediation completes successfully, the ESX host can now be moved back into the original HA cluster.

Tags

host-fails-to-remediate  remediation-fails

See Also

Update History

7/6/2012 - I update the products adding VMware vCenter Update Manager 10/10/2011 - corrected spelling error under cause. 03/03/2014 - Added vCenter Update Manager 5.1 to list of products. 03/12/2015 - Added ESXi 6.0 to Products.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 50 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 50 Ratings
Actions
KB: