[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
** 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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
** 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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
On Mon, Feb 19, 2018 at 9:33 AM, Dimitri John Ledkovwrote: > 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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
"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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs