"Unable to apply DRS resource settings on host" warning in summary tab of the ESXi host
book
Article ID: 318644
calendar_today
Updated On:
Products
VMware vCenter ServerVMware vSphere ESXi
Issue/Introduction
To correct the error message.
Symptoms:
The Summary tab of the ESXi/ESX host reports the warning:
Unable to apply DRS resource settings on host. A general system error occurred: vim.fault.InvalidState. This can significantly reduce the effectiveness of DRS. Unable to apply DRS resource settings on host. There were too many consecutive overrides of the resource settings pushed from the cluster.. This can significantly reduce the effectiveness of DRS.
In the vCenter vpxd.log
2018-10-20T01:00:23.781Z info vpxd[7F93F4C1D700] [Originator@6876 sub=vpxLro opID=HB-SpecSync-host-64@53767-1a461c7e] [VpxLRO] -- BEGIN lro-83952540 -- -- SpecSyncLRO.Synchronize -- 2018-10-20T01:00:28.075Z warning vpxd[7F93EFB7D700] [Originator@6876 sub=MoResGroup opID=4345eb86-575fd9be] Receive ConfigIssue when processing RP updates from host [vim.HostSystem:host-64,<hostname>] type vmodl.fault.ManagedObjectNotFound on ManagedObject vim.ResourcePool:resgroup-59392 for method vim.ResourcePool.updateConfig 2018-10-20T01:00:28.075Z warning vpxd[7F93EFB7D700] [Originator@6876 sub=MoResGroup opID=4345eb86-575fd9be] Receive ConfigIssue when processing RP updates from host [vim.HostSystem:host-64,<hostname>] type vmodl.fault.ManagedObjectNotFound on ManagedObject vim.ResourcePool:resgroup-60336 for method vim.ResourcePool.updateConfig
In ESXi vpxa.log
2018-10-20T01:00:23.802Z info vpxa[C18EB70] [Originator@6876 sub=vpxLro opID=HB-SpecSync-host-64@53767-1a461c7e-ea] [VpxLRO] -- BEGIN lro-406870 -- vpxa -- vpxapi.VpxaService.setConfig -- 525e0823-74e1-2a99-6dcc-04f8ca3a06d9 2018-10-20T01:00:23.815Z error vpxa[C18EB70] [Originator@6876 sub=vpxaVmomi opID=HB-SpecSync-host-64@53767-1a461c7e-ea] [VpxaClientAdapter::InvokeCommon] Re-throwing method-fault 'N5Vmomi5Fault21ManagedObjectNotFound9ExceptionE(vmodl.fault.ManagedObjectNotFound)--> [context]zKq7AUoCAgAAAGeTeQAsdnB4YQAAr8UtbGlidm1hY29yZS5zbwAAMloSAA/QDQEGeQxsaWJ2bW9taS5zbwABAfQaAX5NDQHcUg0C4J4VdnB4YQACM6EVATCNDwNJUMRsaWJ2aW0tdHlwZXMuc28AAvpOJQLxUCUC8VAlAsJVJQLrViUClR8lAnOqJQLTtCUCGrwfAufRGgIW/hoCm/4aBGGYCGxpYnZweGFwaS10eXBlcy5zbwAB9ygMAZpODAJG6igC0o4VAsniJwLpkicCEVkWAvLXJwJT9CcCkZInAs+ZJwLKTCgC/XsTAhFZFgBTNyAAfjsgAHWCIAC0Qi4FymwAbGlicHRocmVhZC5zby4wAAZOSQ1saWJjLnNvLjYA[/context]' received while invoking GetName on vim.ResourcePool:pool34
Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment
Environment
VMware vCenter Server 5.5.x VMware vSphere ESXi 6.0 VMware vCenter Server Appliance 6.0.x VMware vCenter Server 6.0.x VMware vCenter Server Appliance 6.5.x VMware vCenter Server 6.5.x VMware vSphere ESXi 5.5 VMware vCenter Server Appliance 5.5.x VMware vSphere ESXi 6.5
Cause
From vpxa perspective the removal failed and pool34 still exists. From hostd perspective also exist, but the actual object is unregistered, so any attempt to call anything on it results in ManagedObjectNotFound.
Resolution
This issue is resolved in VMware vSphere ESXi 6.5 U2. To download go to VMware Downloads