Julian: I disagree that this is dhclient's fault. The lease file clearly shows the NTP servers were received and the contents of /var/lib/ntpdate/default.dhcp are correctly set to the 3 NTP servers, showing the dhclient exit hook worked too. At this point it is up to the ntpclient to use these servers.
Scott: there is no /etc/ntp.conf file. It is not auto-generated by any script. I would expect the ntp client to honor the DHCP NTP servers if /etc/ntp.conf does not work. Robie: The ARM device we have uses a capacitor to store the state of the RTC. If the device is without power for a few days the RTC completely resets. We absolutely need NTP working to keep these nodes functioning properly in a MAAS cluster. I too wonder why ntpdate-debian completely ignores the DHCP generated file /var/lib/ntpdate/default.dhcp when /etc/ntp.conf doesn't exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257082 Title: MAAS does not use NTP servers specified in DHCPD options To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1257082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
