Only bootstrap nodes seem to be affected by this issue. Also, see admin node bug: https://bugs.launchpad.net/fuel/+bug/1314190
# grep ntpdate /var/log/remote/10.20.0.3/bootstrap/messages.log
2014-05-01T10:04:21.924839+00:00 notice: ntpdate-log: /usr/sbin/ntpdate -U ntp -s -b 10.20.0.2
2014-05-01T10:04:21.924950+00:00 notice: ntpdate-log: /usr/sbin/ntpdate -U ntp -s -b 10.20.0.2
2014-05-01T10:04:21.925061+00:00 notice: ntpdate[875]: ntpdate 4.2.6p5@1.2349-o Sat Nov 23 18:21:48 UTC 2013 (1)
2014-05-01T10:04:21.925172+00:00 err: ntpdate[875]: no server suitable for synchronization found
2014-05-01T10:04:21.925297+00:00 err: ntpdate[876]: no server suitable for synchronization found
2014-05-01T10:04:31.943615+00:00 err: ntpdate[878]: no server suitable for synchronization found
2014-05-01T10:04:51.982537+00:00 err: ntpdate[880]: no server suitable for synchronization found
# cat /etc/nailgun/version.yaml
VERSION:
mirantis: "yes"
production: "docker"
release: "5.0"
build_number: "27"
build_id: "2014-05-01_13-03-28"
astute_sha: "3cffebde1e5452f5dbf8f744c6525fc36c7afbf3"
api: "1.0"
fuellib_sha: "4b8748949f582aaf648903e9d76fb12f80c00e9c"
api: "1.0"
ostf_sha: "134765fcb5a07dce0cd1bb399b2290c988c3c63b"
api: "1.0"
nailgun_sha: "bdd8fa5ee19b5b19dc6412b844b4bd008491c792"
api: "1.0"
fuelmain_sha: "a4f301ea34cfeea7db203c3ea2cdf5ebd064941e"
I can't reproduce this bug. However we should switch to 'ntpd -q' command instead of 'ntpdate', because 'ntpdate' is depricated. askubuntu. com/questions/ 254826/ how-to- force-a- clock-update- using-ntp
Something like 'ping 10.20.0.2 && ntpd -q' in startup scripts.
http://