On Fri, Jan 6, 2017 at 9:28 AM, Nobuto Murata <email address hidden>
wrote:
> @Ryan,
> I used MAAS 2.1 since it puts its IP address as a local NTP server into
> the vendor data for MAAS nodes by default. I believe just deploying one
> mode using MAAS 2.1 reproduces the problem.
>
OK, thanks, I'll follow up with MAAS.
If you have access could you attach the /etc/ntp.conf file that's written
out ?
Also /var/lib/cloud/instance/vendor-data* ?
On Fri, Jan 6, 2017 at 9:28 AM, Nobuto Murata <email address hidden>
wrote:
> @Ryan,
> I used MAAS 2.1 since it puts its IP address as a local NTP server into
> the vendor data for MAAS nodes by default. I believe just deploying one
> mode using MAAS 2.1 reproduces the problem.
>
OK, thanks, I'll follow up with MAAS.
If you have access could you attach the /etc/ntp.conf file that's written cloud/instance/ vendor- data* ?
out ?
Also /var/lib/
Thanks
> /bugs.launchpad .net/bugs/ 1645644 /bugs.launchpad .net/cloud- init/+bug/ 1645644/ +subscriptions
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> ntp is not restarted after writing /etc/ntp.conf by cloud-init
>
> To manage notifications about this bug go to:
> https:/
>