On Fri, Jan 6, 2017 at 9:28 AM, Nobuto Murata <[email protected]> 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* ? Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1645644 > > Title: > ntp is not restarted after writing /etc/ntp.conf by cloud-init > > To manage notifications about this bug go to: > https://bugs.launchpad.net/cloud-init/+bug/1645644/+subscriptions > ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Summary changed: - ntp is not restarted after writing /etc/ntp.conf by cloud-init + ntp not using expected servers -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1645644 Title: ntp not using expected servers Status in cloud-init: New Status in cloud-init package in Ubuntu: Incomplete Status in maas package in Ubuntu: New Bug description: cloud-init: 0.7.8-49-g9e904bb-0ubuntu1~16.04.1 Expected NTP server address is written in /etc/ntp.conf by cloud-init through vendor-data. However, `ntpq -p` shows the default ntp pools, not my local NTP server written in /etc/ntp.conf. It looks like cloud-init needs to write /etc/ntp.conf before installing ntp package, or restart ntp after writing /etc/ntp.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1645644/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
