schwupp
Contributor
Contributor

same issue here. Cluster with 2x ESX 6.5 Host. MM of single host works perfect with full auto DRS, Remediation of the cluster (checked options disabling DPM, FT, HA) breaks at 30%.

Looked into /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-log4cpp.log and saw

[2017-08-18 12:25:13:842 'VciTaskBase.VciClusterJobDispatcherTask{204}' 140259801110272 ERROR]  [vciClusterJobSchedulerTask, 1035] DRS API returned faults

[2017-08-18 12:25:13:842 'VciTaskBase.VciClusterJobDispatcherTask{204}' 140259801110272 ERROR]  [vciClusterJobSchedulerTask, 1040] No current remediation is going on so address the faults

[2017-08-18 12:25:13:842 'VciTaskBase.VciClusterJobDispatcherTask{204}' 140259801110272 ERROR]  [vciClusterJobSchedulerTask, 1044] No of returned faults : 27

[2017-08-18 12:25:13:844 'VciTaskBase.VciClusterJobDispatcherTask{204}' 140259801110272 ERROR]  [vciClusterJobSchedulerTask, 1053] Name of VM that caused fault : <Name of all running VMs>

[2017-08-18 12:30:14:109 'VciTaskBase.VciClusterJobDispatcherTask{204}' 140259801110272 INFO]  [vciClusterJobSchedulerTask, 1071] DRS API indicates no active host available in cluster. Discarding fault.

[2017-08-18 12:30:14:181 'VciTaskBase.VciClusterJobDispatcherTask{204}' 140259801110272 ERROR]  [vciClusterJobSchedulerTask, 1666] Skipping host from remediation as DRS API did not recommend host host-270 to go into mmode

Don't know what should be wrong here?

Reply
0 Kudos