Deploy and power on failures occur when a host is upgraded or added to the vCenter Server
search cancel

Deploy and power on failures occur when a host is upgraded or added to the vCenter Server

book

Article ID: 337257

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:
  • Deploy and power on failures occur when a host is added to the vCenter Server or is upgraded after being added to the vCenter Server.
  • One or more of these errors may occur:
    • DRS failed to find hosts to deploy the virtual machines on the resource pool (resource pool ID). DRS failed to find host for virtual machine (machine name). vCenter reported: No host is compatible with the virtual machine. Unable to find host for virtual machine "NoCompatibleHost"

    • DRS failed to find hosts to deploy the virtual machines on the resource pool (resource pool ID). DRS failed to find host for virtual machine (machine name). vCenter reported: DRS cannot find a host to power on or migrate the virtual machine. Insufficient capacity on host (hostname of the ESX server)

    • VirtualMachine.powerOn task on PowerOnVM_Task failed: The operation is not supported on the object.

  • Virtual machines may all deploy to a particular host or set of hosts when other hosts are available.


Environment

VMware vCenter Lab Manager 4.0.x

Cause

This issue occurs if the vCenter Server database sends incorrect ESX release information to vCenter Lab Manager.

Resolution

To fix the database and work around this issue, remove the host from Lab Manager and vCenter and then add it back.
Perform these steps for each ESX host, one at a time:
  1. In Lab Manager Global Organization, click Resources, then click the Hosts tab.
  2. If host spanning is enabled on the host, go to the host properties and disable it.
  3. From the Resources/Hosts page, disable the host.
  4. Either un-deploy all virtual machines on the host or put the host into maintenance mode so that all of the virtual machines vMotion to another host.
  5. When all of the virtual machines are off of the host, un-prepare the host in Lab Manager.
  6. Edit the cluster settings in VMware Infrastructure (VI) Client, and in the VMware DRS change the automation level to Manual.
  7. Disconnect the host from the cluster.
  8. When the host is disconnected from the cluster, remove the host from the cluster.
  9. Re-add the host to the cluster and take it out of maintenance mode.
  10. In Lab Manager, prepare the host on the Resources/Hosts page.
  11. After completing this process for all ESX hosts in the cluster, set the DRS settings back to automated (if it was previously set to automated).

Note: You cannot migrate a virtual machine from an ESX 4.0 host to an ESX 3.5 host. For information about configuring Lab Manager in a mixed ESX 3.5 and 4.0 environment, see the Lab Manager Installation and Upgrade Guide and Lab Manager User's Guide.


Additional Information

This issue is resolved in vCenter Lab Manager 4.0.1, vCenter Server 4.0 Update 1, ESX/ESXi 4.0 Update 1 and later revisions. Upgrade to the latest version in order to correct this issue, without having to perform the above workaround.