Comment 6 for bug 1749722

On Mon, Feb 19, 2018 at 9:33 AM, Dimitri John Ledkov <<email address hidden>
> 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
>