should it rather be network online target in the service file?

Bug #1746458 reported by Christian Ehrhardt  on 2018-01-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chrony (Debian)
Fix Released
Unknown
chrony (Ubuntu)
Medium
Christian Ehrhardt 

Bug Description

Currently the systemd service holds:
After=network.target

I think this should be the online target instead to be able to sync from/to anybody.

Need to check this.

Yes according to [1] the most direct translation to the old LSB $network would be:
Wants=network-online.target
After=network-online.target

And that is what chrony was and IMHO should be again.
That also would fix some rare cases where network comes up late and chrony starts in offline mode.
Relying on the hooks to online it isn't recommended btw (Only working for NetworkManager in 18.04 atm).

[1]: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

Changed in chrony (Ubuntu):
status: New → Triaged
assignee: nobody → ChristianEhrhardt (paelzer)
importance: Undecided → Medium

Note: in the sense of the link above chrony is not a classic server but a "client software that cannot operate without network" as it need to sync time from/to somewhere.

Changed in chrony (Debian):
status: Unknown → New
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package chrony - 3.2-2ubuntu2

---------------
chrony (3.2-2ubuntu2) bionic; urgency=medium

  * d/control: use to nss instead of tomcrypt (in main) (LP: #1744072)
  * d/chrony.conf: use ubuntu ntp pool and server (LP: #1744664)
  * d/chrony.default, d/chrony.service: support /etc/default/chrony
    DAEMON_OPTS in systemd environment (LP: #1746081)
  * d/chrony.service: properly start after networking (LP: #1746458)
  * d/usr.sbin.chronyd: allow to create /run/chrony on demand (LP: #1746444)

 -- Christian Ehrhardt <email address hidden> Fri, 19 Jan 2018 09:45:38 +0100

Changed in chrony (Ubuntu):
status: Triaged → Fix Released
Changed in chrony (Debian):
status: New → Incomplete

After a discussion with the Debian maintainer I agree to revert this change.
I uploaded chrony_3.2-2ubuntu3_source.changes [1] with that change.

[1]: https://launchpad.net/ubuntu/+source/chrony/3.2-2ubuntu3

Changed in chrony (Debian):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.