The issue is resolved in vCenter Server 7.0 Update 3 (build number 18700403)
Workaround:
To workaround this issue, apply any of the below workaround.
- This alarm is harmless so you can potentially acknowledge and ignore it since NTP server is same across all hosts.
- Take a snapshot of VC before executing the below steps
For the clusters that have their NTP Configs changed post configuration
UPDATE VPX_HCI_CONFIG_INFO
WHERE cluster_id = ? <-- note that this is a number, a cluster_id of cluster domain-c4003 is 4003.
SET datetime_config=NULL;Cluster_id can be obtained by clicking the Cluster Name in VC Inventory.