In a DRS-enabled cluster, multiple ESXi hosts intermittently report the following alert:
"Unable to apply DRS resource settings on host. The operation is not allowed in the current state. This can significantly reduce the effectiveness of DRS.”
These warnings occur intermittently across hosts participating in a DRS-enabled cluster.
Sample log entries:
From vpxd.log:
XXXX-XX-XX warning vpxd[05685] [Originator@6876 sub=MoResGroup opID=HB-host-XX@27057-63e27c39] Receive ConfigIssue when processing RP updates from host [vim.HostSystem:host-01,host01.XX] type vim.fault.InvalidState on ManagedObject vim.ResourcePool:resgroup-11 for method vim.ResourcePool.updateChildResourceConfiguration
From hostd.log:
XXXX-XX-XXT2Z Er(163) Hostd[2099608]: [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/datastore/vmanme.vmx opID=HB-SpecSync-host-01@xxxxxxx user=vpxuser:<no user>] Invalid transition requested (VM_STATE_ON_SHUTTING_DOWN -> VM_STATE_RECONFIGURING): Invalid state
VMware vCenter Server 8.0
DRS performs a spec sync every minute, and if a VM powers off at the same time the sync is triggered, an InvalidState error is logged—this is expected behavior and has no impact on DRS operations.
This behavior is expected in environments where VMs are frequently powered on/off or rapidly created and deleted.
Spec sync operations occur every 1 minute.
If a VM powers off during a spec sync, the alert may temporarily appear.
The issue resolves automatically in the next sync cycle, during which the powered-off VM is skipped.
No action is required.
There is no impact on DRS functionality or overall cluster operations.
The alerts do not indicate a configuration issue.
The behavior is common in automated environments (VDI, Automation environiments).