ntpdate-debian not working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ntp (Debian) |
Fix Released
|
Unknown
|
|||
ntp (Ubuntu) |
Fix Released
|
Medium
|
Christian Ehrhardt | ||
Xenial |
Fix Released
|
Medium
|
Christian Ehrhardt |
Bug Description
[Impact]
* ntpdate-debian fails to work if ntp is installed at the same time due to a conflict in the updated ntp config to the ntpdate-debian script.
[Test Case]
# e.g. spawn xenial container
# Note: only occurs when ntp is installed as well
$ apt-get install ntpdate ntp
$ ntpdate-debian
(Note for latter verification enable proposed in that container and re-update ntpdate)
[Regression Potential]
* There could exists a custom user conf that had a mixed server AND pool specified, that now will use the first of both types while instead formerly it would have used the first server entry. The chance for this is super-low IMHO, but this case exists.
--------
in 16.04 I get this
# ntpdate-debian
28 Apr 09:54:14 ntpdate[30747]: no servers can be used, exiting
The problem is that ntpdate-debian parse /etc/ntp.conf, searchin for the word "server",
but the format of the file as changed a bit
< server 0.ubuntu.
< server 1.ubuntu.
< server 2.ubuntu.
< server 3.ubuntu.
---
> pool 0.ubuntu.
> pool 1.ubuntu.
> pool 2.ubuntu.
> pool 3.ubuntu.
25c24
< server ntp.ubuntu.com
---
> pool ntp.ubuntu.com
the word server as been replaced by "pool"
Changed in ntp: | |
status: | Unknown → New |
Changed in ntp: | |
status: | New → Fix Released |
Changed in ntp: | |
status: | Fix Released → New |
affects: | ntp → ubuntu |
Changed in ubuntu: | |
importance: | Unknown → Undecided |
no longer affects: | ubuntu |
Changed in ntp (Debian): | |
status: | Unknown → New |
Changed in ntp (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in ntp (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in ntp (Ubuntu Xenial): | |
assignee: | nobody → ChristianEhrhardt (paelzer) |
Changed in ntp (Ubuntu Xenial): | |
status: | Triaged → In Progress |
status: | In Progress → Fix Committed |
Changed in ntp (Debian): | |
status: | New → Fix Released |
Changed in ntp (Debian): | |
status: | Fix Released → New |
Changed in ntp (Debian): | |
status: | New → Fix Released |
indeed, that's a debian bug and should be forwarded to their bts