On an VCP enabled cluster, certain DRS related workfklows update some advanced options on the host. This change in configuration will be reported as compliance drift by VCP platform.
The following ESX advanced options are reported as drift:
esx/advanced_options/mem/VM_overhead_growth_limitesx/advanced_options/misc/heartbeat_panic_timeoutvSphere 9.0 with VCP enabled
In a VCP enabled cluster, the source of truth for ESX configurations is captured in desired configuration document. DRS workflows use Host APIs to configure certain host settings causing host configurations to drift from the desired configuration. This drift in host configuration is flagged by VCP Check Compliance API.
To resolve the drift, these advanced options need to be added to the cluster desired configuration document.
"Configure tab → Configuration → Draft → Create Draft" option on the UI. VM_overhead_growth_limit setting, select "Draft tab → esx → advanced_options → mem → Configure Settings". In the edit tab, update the VM_overhead_growth_limit with the 'Host value' from Compliance drift.heartbeat_panic_timeout setting, select "Draft tab → esx → advanced_options → misc → Configure Settings". In the edit tab, update the heartbeat_panic_timeout with the 'Host value' from Compliance drift.Configure tab → Configuration → Draft → Show Changes". This will show changes present in the draft.Configure tab → Configuration → Draft → Check Compliance". This will start a check compliance task to verify the hosts are not in drift after editing. Configure tab → Configuration → Draft → Apply Changes". This will commit the draft as the new desired configuration for the cluster and start remediation task on the cluster. Since the hosts are already compliant, there will be no action taken on the host.