This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1749722
Title:
NTP: take into account systemd-timesyncd where present
Status in cloud-init:
Fix Released
Status in systemd package in Ubuntu:
New
Bug description:
Currently, the NTP module configures ntpd during cloud-init install by
installing and configuring ntpd.
ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
Xenial.
Ideally the NTP module should configure systemd-timesyncd where
present, falling back to ntpd where not present.
This stops two separate daemons (ntpd and systemd-timesyncd) competing
with each other to set the time, where systemd-timesyncd (on Ubuntu at
least) has an internal hardcoded compiled in timeserver to fall back
on if no timeserver is configured (which is bad, but what can you do).
The competing timeserver behaviour is invisible when the machine can
see the net, but logs this error constantly when the machine cannot
see the net:
systemd-timesyncd[527]: Timed out waiting for reply from
91.189.94.4:123 (ntp.ubuntu.com).
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
