/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log
YYYY:MM:DDTHH:MM:SS info vmware-vum-server[09428] [Originator@6876 sub=Telemetry] [TelemetryManager 423] Sending telemetry data: {"@type":"pman_effective_coordinator_policy","taskId":"TASK_ID","entityId":"ENTITY-ID|domain-c8","failureAction":"RETRY","failureActionRetryDelay":300,"failureActionRetryCount":3,"preRemediationPowerAction":"DO_NOT_CHANGE_VMS_POWER_STATE","enableQuickBoot":true,"disableDpm":true,"disableHac":false,"evacuateOfflineVms":false,"enforceHclValidation":false,
"parallelRemediationEnabled":true,"maxHostsForParallelRemediation":0}
This is an expected behavior.
Parallel remediation reduces the time needed for patching or upgrading the hosts in your environment. The remediation in parallel only applies for ESXi hosts that are already in maintenance mode. During parallel remediation, hosts do not enter or exit maintenance mode automatically. To remediate hosts in parallel, host must be set to enter and exit maintenance mode manually. If parallel remedation is enabled, vSphere Lifecycle Manager does not remediate the ESXi hosts that are not in maintenance mode.
For additional information, refer to Remediating ESXi Hosts Against vSphere Lifecycle Manager Baselines and Baseline Groups
To resolve the issue, implement either of the below steps
OR
To disable parallel remediation, please follow the steps below