Bug 1279760 - Gnome System Settings does not sync date/time with ntpd (only chrony)
Gnome System Settings does not sync date/time with ntpd (only chrony)
Product: Fedora
Classification: Fedora
Component: timedatex (Show other bugs)
Unspecified Linux
unspecified Severity low
: ---
: ---
Assigned To: Miroslav Lichvar
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-10 03:55 EST by Antonin
Modified: 2015-11-10 07:56 EST (History)
8 users (show)

See Also:
Fixed In Version: timedatex-0.4-1.fc24
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-10 07:56:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Antonin 2015-11-10 03:55:25 EST
Description of problem:

I have Fedora Workstation 23 with ntp package installed.
Fedora in base installation also include chrony package.
So I have 2 ntp packages.

I am not able to set preferred ntp client (chronyd vs. ntpd).
When I do "timedatectl set-ntp true"
or turn on NTP sync via
Gnome System Settings/Date and Time/Synchronize date and time over the network,
it is always used chronyd.

I can change the order by renumbering files in /lib/systemd/ntp-units.d :

But /lib/systemd directory should not be used for user configuration.
User configuration files are placed to /etc/systemd .
With this rule I am not able to set ntpd as preferred NTP client.

Steps to Reproduce:

1. dnf install ntp
2. timedatectl set-ntp false
3. timedatectl set-ntp true
4. systemctl status chronyd
5. systemctl status ntpd

Actual results:

chronyd.service is enabled and running
ntpd.service is disabled and stopped

Expected results:

chronyd.service is disabled and stopped
ntpd.service is enabled and running
Comment 1 Michal Sekletar 2015-11-10 04:12:23 EST
In Fedora we don't use systemd-timedated for controlling NTP setting. There is an drop-in replacement called timedatex which still supports configuring alternative NTP implementations. Reassigning.
Comment 2 Miroslav Lichvar 2015-11-10 05:17:27 EST
timedatex reads the unit names also from /etc/systemd/ntp-units.d. Unfortunately, duplicating an entry to increase the priority of a service doesn't work with the current code. The service will be started, but then it will be stopped immediately as the other entry of the service with lower priority is disabled.

I'll look into that.

As a workaround you can uninstall the chrony package.
Comment 3 Antonin 2015-11-10 05:45:54 EST
After my Fedora Workstation 23 installation there is a lot of dependencies for chrony package.
Removing is not possible.
Comment 4 Miroslav Lichvar 2015-11-10 05:59:15 EST
Hm, which packages depend on chrony? "repoquery --whatrequires chrony" on F23 prints an empty list for me.
Comment 5 Antonin 2015-11-10 06:32:46 EST
Now I am away from my pc. But I remember after "dnf remove chrony" there was a long list to remove - about 25 items, include anaconda-core, some python's, etc...
Comment 6 Miroslav Lichvar 2015-11-10 07:56:42 EST
Anaconda, initial-setup and revisor can be probably removed if you don't want to create Fedora images, etc.

Anyway, the issue with timedatex disabling ntpd when it's listed multiple times in the ntp-units.d directories should be now fixed in timedatex-0.4. You can copy /lib/systemd/ntp-units.d/60-ntpd.list to /etc/systemd/ntp-units.d/30-ntpd.list for instance.

Note You need to log in before you can comment on or make changes to this bug.