systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Debian) |
Fix Released
|
Unknown
|
|||
systemd (Ubuntu) |
Fix Released
|
High
|
Balint Reczey | ||
Eoan |
Won't Fix
|
High
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Balint Reczey |
Bug Description
Ubuntu 19.10's systemd package introduced /lib/systemd/
Possible workarounds:
- Uninstall ntp
- Disable systemd-
% lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
% apt-cache policy systemd
systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
*** 242-7ubuntu3 500
500 http://
100 /var/lib/
% apt-cache policy ntp
ntp:
Installed: 1:4.2.8p12+
Candidate: 1:4.2.8p12+
Version table:
*** 1:4.2.8p12+
500 http://
100 /var/lib/
% dpkg -S /lib/systemd/
systemd: /lib/systemd/
% sudo systemctl status ntp
● ntp.service - Network Time Service
Loaded: loaded (/lib/systemd/
Active: inactive (dead)
Docs: man:ntpd(8)
% sudo systemctl status systemd-
● systemd-
Loaded: loaded (/lib/systemd/
Drop-In: /lib/systemd/
Active: inactive (dead)
Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
Docs: man:systemd-
Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network Time Synchronization being skipped.
tags: | added: rls-ee-incoming |
Changed in systemd (Ubuntu): | |
assignee: | nobody → Balint Reczey (rbalint) |
Changed in ntp (Ubuntu): | |
assignee: | nobody → Balint Reczey (rbalint) |
tags: | removed: rls-ee-incoming |
tags: | added: id-5dbb33265d09bf5e5d2ca5df |
tags: | added: dist-upgrade |
no longer affects: | ntp (Ubuntu) |
no longer affects: | ntp (Ubuntu Eoan) |
no longer affects: | ntp (Ubuntu Focal) |
Changed in systemd (Ubuntu Eoan): | |
importance: | Undecided → High |
Changed in systemd (Ubuntu Focal): | |
importance: | Undecided → High |
Changed in systemd (Debian): | |
status: | Unknown → Fix Released |
I realize that the title makes it sound as though this is intended behavior. To be clear, in this scenario, neither systemd- timesyncd. service nor ntp.service start. It's not just systemd- timesyncd. service that doesn't start, as that would be intended behavior.