Thank you for identifying this. I agree it makes sense to fix it in
Xenial. Though I wonder about how the change might adversely impact
existing users.
For example, if a DHCP user is receiving a broken set of NTP servers
that doesn't work, currently his NTP won't be broken because the default
set will be used
But with this fixed, the default set will stop being used, and his NTP
will appear to break. Though the root cause is that his DHCP or network
was misconfigured, it would be the SRU that causes the problem to
emerge.
In principle I think this is OK, but we should point it out in
"Regression Potential", and I appreciate more opinions.
** Also affects: ntp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: ntp (Ubuntu Xenial)
Status: New => Triaged
** Changed in: ntp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656801
Title:
ntp: changing the default config from server to pool broke the dhcp
hook
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
