Red Hat Bugzilla – Bug 853666
Can't enable network time from anaconda (date & time spoke)
Last modified: 2012-11-22 20:23:13 EST
Description of problem:
When running anaconda from Fedora-18-Alpha-TC5-x86_64-DVD.iso I can not enable network time with the switch in the date & time spoke.
The error messages I see in the program-log tty are a chronyd.service status telling me that chronyd.service is loaded but disabled and inactive (dead).
The other message is:
Failed to issue method call: Unit systemd-timedated-ntp.target failed to load: No such file or directory. ...
I can successfully run
# systemctl start systemd-timedated
after which systemctl status shows that it's active (running), but I don't know if that is what anaconda is supposed to do.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot from Fedora-18-Alpha-TC5-x86_64-DVD.iso
2. Start installation, select English language
3. Go to Date & Time spoke and click on the Network Time switch
Nothing happens, the switch stays off
The switch should start some kind of network time service
I have no idea if that's an anaconda issue, as I'm lost in the chaos about chronyd/ntp/systemd-timedated and systemd; there are various bugs around. I'm just filing this one for the sake of the Fedora 18 alpha TC5.
Anaconda starts chronyd.service which fails because it is bound to systemd-timedated-ntp.target, which was removed from systemd .
Is systemd-timedated.service  the new thing to use (instead of chronyd.service)?
Lennart, could you please share some information about what's going on here? Should anaconda use systemd-timedated instead of chronyd? If yes, what configuration files systemd-timedated uses?
This issue is still present in Alpha-RC2-i386
Enabling chronyd.service manually or via timedated should be equivalent. timedated simply enables the first service it finds that is listed in /usr/lib/systemd/ntp-units.d/*.list.
NTP has been updated correctly, but chronyd misses the file. WHich is probably my fault, because I forgot to ping the chrony maintainer about it. Will file a bug now.
(In reply to comment #4)
> NTP has been updated correctly, but chronyd misses the file. WHich is
> probably my fault, because I forgot to ping the chrony maintainer about it.
> Will file a bug now.
Filed a bug about this now to get this corrected:
I have just tested the chrony-1.27-0.5.pre1.git1ca844.fc18 build and everything works as expected. We just have to wait for some post-alpha compose.
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.
(ref comment #6)