Comment 7 for bug 1645644

On Fri, Jan 6, 2017 at 10:13 AM, Nobuto Murata <email address hidden>
wrote:

> I don't have MAAS env right now at hand. But as I attached the log and
> the code above. /etc/ntp.conf and vendor data were correct. Just
> restarting the daemon by cloud-init was missing if I understand it
> correctly.
>

Ahh, interesting. I was initially confused about where the ntp.conf come
from but now
I can see the bug:

1) ntp is configured via vendor-data
2) cloud-init installs ntp
3) cloud-init moves default ntp.conf to ntp.conf.dist
4) cloud-init writes out the ntp.conf with values provided via ntp config
dictionary from vendor data

Running ntpq at this point will get results from ntpd which spawned after
package install. At the time
of package install, it used the packaged ntp.conf which did not have the
updated ntp.conf that was
rendered from config.

With that understanding, I agree that we should render the configuration
file before installing
the package so that ntpd will only use the servers/pools defined by the
vendor data.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1645644
>
> Title:
> ntp not using expected servers
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1645644/+subscriptions
>