[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[James Falcon]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3119

** Bug watch added: github.com/canonical/cloud-init/issues #3119
   https://github.com/canonical/cloud-init/issues/3119

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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:
  Invalid

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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:
  Invalid

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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Scott Moser]

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 Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/343136

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  Fix Committed
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Scott Moser]

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=c6dff581


** Changed in: cloud-init
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  Fix Committed
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Ryan Harper]

** Merge proposal linked:
   https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Ryan Harper]

On Mon, Feb 19, 2018 at 9:33 AM, Dimitri John Ledkov  wrote:

> I think cloud-init is the oracle of information of which ntp daemon to
> use, and which ntp servers to use. Thus on bionic+ cloud-init, when
> configuring ntp, should also "disable systemd-timesyncd" if some
> alternative NTP server is to be used.
>

I'm not opposed to having cloud-init do that.  But systemd and ntp clients
are
installable outside of cloud images and they should behave consistently
there.
I think a combination of the override which prevents timesyncd from
starting if a client
is present *and* the Conflicts= that's present in Bionic should be in the
packaging.

Such a configuration would prevent timesyncd starting from stopping other
clients.


> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1749722
>
> Title:
>   NTP: take into account systemd-timesyncd where present
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Dimitri John Ledkov]

I think cloud-init is the oracle of information of which ntp daemon to
use, and which ntp servers to use. Thus on bionic+ cloud-init, when
configuring ntp, should also "disable systemd-timesyncd" if some
alternative NTP server is to be used.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Dimitri John Ledkov]

"if some alternative NTP server is to be used." should read "if some
alternative NTP client daemon is to be used." obviously =)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Ryan Harper]

Some further looking at the systemd side, Bionic no longer carries the
override conf (disable-with-time-daemon.conf) in favor of updating each
client's systemd unit to use:

Conflicts=systemd-timesyncd.service

Conflicts will ensure that the target service is stopped if the current
unit is started. So, if ntp or chrony unit were to start, it would stop
timesyncd.

This is roughly equivalent, however, it does leave timesyncd unit
enabled.  This means that if something starts systemd-timesyncd.service,
it would stop the ntp or chrony service.

There may be additional work on each of the time packages to *disable*
timesyncd unit when installed such that it won't start.  This may not be
possible to prevent users from starting timesyncd manually.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present

[Ryan Harper]

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749722

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp