This behavior may occur when the "parallelRemediationEnabled" setting is set to 'true'.
In such cases, the remediation task may complete without any errors. However, hosts not already in Maintenance Mode will be skipped during the remediation process.
To address this issue, the following options are available:
Option 1: Disable parallel remediation by setting parallelRemediationEnabled to false.
Note: Disabling the "parallelRemediation" option within the remediation settings triggers a standard remediation workflow where hosts are automatically placed into maintenance mode and then remediated sequentially.
1. Steps to check Global Lifecycle manager settings for parallel remediation:
Settings".Cluster Lifecycle" select "Images".Note: Global vLCM settings are applicable for all vLCM clusters. Disabling the option here, will disable this setting on all clusters. However, these settings can be overridden individually on a per cluster basis.
2. Steps to disable global vLCM settings that are applicable to all clusters. Please validate the settings on each cluster:
Updates tab.Image section.Check Compliance" button.Edit Remediation Settings.Uncheck the Parallel remediation settings.Option 2: Manually place the hosts into maintenance mode before starting the remediation.
After performing the changes above, the remediation was successful.
Improved messaging and notifications regarding this behavior have been implemented in VCF 9.x.
Related issue: Remediation task using vSphere Lifecycle Manager (vlcm) of hosts in the cluster completes without patching the hosts