Unable to power on VMs from vCenter Server with error "All required agent virtual machines are not currently deployed on host 'hostname'"
Article ID: 393821
Updated On:
Products
Issue/Introduction
- Unable to power on virtual machines from vCenter Server
- You see an error similar to: All required agent virtual machines are not currently deployed on host hostname.
/var/log/vmware/vpxd.log on vCenter:
XX:XX:XXTXX:XX:XX info vpxd[09951] [Originator@6876 sub=vpxLro opID=########-######-####-####-##:########-##-##] [VpxLRO] -- BEGIN task-150241 -- VMName -- Datacenter.ExecuteVmPowerOnLRO --
XX:XX:XXTXX:XX:XX info vpxd[09951] [Originator@6876 sub=cdrsPlmt opID=########-######-####-####-##:########-##-##] Vm [vim.VirtualMachine:vm-###,VMName] failed constraint check true on host [vim.HostSystem:host-#####,esxifqdn] with <obj xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xml
ns="urn:vim25" versionId="7.0.3.0" xsi:type="LocalizedMethodFault"><fault xsi:type="InsufficientAgentVmsDeployed"><hostName>esxifqdn</hostName><requiredNumAgentVms>4</required
XX:XX:XXTXX:XX:XX info vpxd[09951] [Originator@6876 sub=cdrsPlmt opID=########-######-####-####-##:########-##-##] Dump section 1205596710441 created.
XX:XX:XXTXX:XX:XX error vpxd[09951] [Originator@6876 sub=vpxLro opID=########-######-####-####-##:########-##-##] [VpxLRO] Unexpected Exception: N3Vim5Fault28InsufficientAgentVmsDeployed9ExceptionE(Fault cause: vim.fault.InsufficientAgentVmsDeployed
--> )
--> [context]zKq7AVECAQAAAOIfcwEYdnB4ZAAAAto3bGlidm1hY29yZS5zbwAAmXksABdtLQAf6jKB88IHAWxpYnZpbS10eXBlcy5zbwCBndMHAYELfAgBAR+x6wKXHXN2cHhkAIIdYkABAj0N+wLG0vsCtdP7AqBmlIL1BGkBgjYGaQGCZBVpAYLHQmgBgpLsaAEA50kjAHWfIwDAZTcDh38AbGlicHRocmVhZC5zby4wAAS/Ng9saWJjLnNvLjYA[/context]
XX:XX:XXTXX:XX:XX info vpxd[09951] [Originator@6876 sub=vpxLro opID=########-######-####-####-##:########-##-##] [VpxLRO] -- FINISH task-150241
XX:XX:XXTXX:XX:XX info vpxd[09951] [Originator@6876 sub=Default opID=########-######-####-####-##:########-##-##] [VpxLRO] -- ERROR task-150241 -- VMName -- Datacente
r.ExecuteVmPowerOnLRO: vim.fault.InsufficientAgentVmsDeployed:
--> Result:
--> (vim.fault.InsufficientAgentVmsDeployed) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> hostName = "esxiname",
--> requiredNumAgentVms = 4,
--> currentNumAgentVms = 2
--> msg = ""
--> }
--> Args:Environment
VMware vCenter Server 7.x
Cause
The vSphere cluster lacks the required quorum of powered-on vSphere Cluster Services (vCLS) agent virtual machines. This configuration mismatch causes vCenter Server to block workload VM power-on operations despite EAM agencies reporting a green status.
Resolution
Validate that the ESX Agent Manager (EAM) agency status is green in the vSphere Client. (See here)
Navigate to the affected vSphere cluster and validate the number of deployed vCLS agent virtual machines.
Verify the power state of the deployed vCLS virtual machines.
If the required vCLS virtual machines are present but powered off, manually power them on to restore cluster quorum.
If fewer vCLS virtual machines are present than the cluster requires, enable vCLS Retreat Mode on the cluster to clean up the existing vCLS state.
Disable vCLS Retreat Mode to automatically recreate the missing vCLS agent virtual machines. (See here)
Workaround: If vCLS virtual machines cannot be immediately restored, navigate to the vCenter Server Managed Object Browser (MOB) and execute the updateComputeResourceAgentInfo method to force the cluster to require 0 agents. (This is a temporary workaround to bypass the power-on block.)
Take a offline snapshot of the vCenter Server before making any changes
- Browse to:
https://{vc-fqdn}/mob/?moid=EsxAgentConfigManager&vmodl=1 - Open: updateComputeResourceAgentInfo
- Paste this in the value VALUE field:
<computeResourceAgentInfo> <computeResource type="ComputeResource">CLUSTER MOID</computeResource> <numRequiredAgents>0</numRequiredAgents> </computeResourceAgentInfo> Click Invoke Method
NOTE: Replace CLUSTER MOID with the ID of the problematic cluster (On vCenter server select the affected cluster and look at the url. It should show as domain-c123, for example).
Additional Information
Feedback
