Closed mattsday closed 2 weeks ago
Do we understand why this error is happening?
https://vkernelblog.com/vcenter-failed-to-set-the-time-via-ntp-details/ suggests that port 123 may be blocked.
https://kb.vmware.com/s/article/59729 suggests that if the target NTP service does not respond to ICMP, the NTP "valid server" check will fail (prior to vCenter Server 6.7 Update 2).
I can confirm that time.nist.gov
does not respond to ICMP. This sounds like the likely cause.
Closed based on #120.
Reopening for @mattsday follow-up:
This is not a permanent fix, as ideally the deployment would fail at this stage instead of continuing until a timeout. I will also add a PR doing this.
It sounds like this problem could also be solved with a documentation update requiring vCenter Server 6.7 Update 2.
+1 on a documentation update, would be a much better long-term solution even if switching to time.google.com
works around the issue for now
When deploying the vCenter virtual appliance, it always fails with a message like this before timing out:
Details: vCenter ISO:
VMware-VCSA-all-6.7.0-15132721.iso
esxi_size =c3.medium.x86
I have worked around it by changing the VCVA appliance ntp to
time.google.com
:This is not a permanent fix, as ideally the deployment would fail at this stage instead of continuing until a timeout. I will also add a PR doing this.