Description of problem:
I saw this in f20 final anaconda installer, after install 'chronyd' service is active/running, but I selected/switched to OFF network option in timezone settings. Now tested f21 alpha-tc5 workstation live image, same problem.
I see in /root/anaconda-ks.cfg
# System timezone
timezone <xxx>/<xxx> --isUtc --nontp
I don't know how it works, but looks like '--nontp' is selected, but doesn't work later after install
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Just want to confirm this on f20, I tested f20 final KDE live, after install, same problem 'chronyd' running and I switched network time option to OFF in anaconda
"# System timezone" options same to those of f21 install, so '--nontp' is there.
Can you attach the logs from the installation to this bug? --nontp is working fine for me in the f21 alpha-tc5 installer.
Sorry, I cannot test this anymore.
Please close this bug.
After install f21 workstation live image (alpha_rc1), I switched network time in installer to OFF, chronyd is running.
I'll attach anaconda-ks file, and log files.
Created attachment 940483 [details]
Created attachment 940484 [details]
Created attachment 940485 [details]
Created attachment 940487 [details]
Created attachment 940488 [details]
Created attachment 940489 [details]
Created attachment 940490 [details]
There was also ks-script-c06CvO.log in /var/log/anaconda, but it is empty 0b
I'm not sure how this work, but maybe this is not anaconda bug?
# systemctl status chronyd
● chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
Active: active (running) since Tue 2014-09-23 17:39:10 CEST; 4min 46s ago
Process: 584 ExecStartPost=/usr/libexec/chrony-helper add-dhclient-servers (code=exited, status=0/SUCCESS)
Process: 555 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 564 (chronyd)
Sep 23 17:39:09 localhost.localdomain chronyd: chronyd version 1.31-pre1 starting
Sep 23 17:39:09 localhost.localdomain chronyd: Generated key 1
Sep 23 17:39:29 localhost.localdomain chronyd: Selected source 18.104.22.168
Sep 23 17:39:29 localhost.localdomain chronyd: System clock wrong by 1.081258 seconds, adjustment started
When I disable it
# systemctl disable chronyd
Removed symlink /etc/systemd/system/multi-user.target.wants/chronyd.service.
Flipping the switch doesn't turn ntp off in the installer environment, it only controls whether ntp is enabled or disabled in the installed system. I suppose you could argue that we should turn it off in the installer as well.
This is all after install, when booted to installed system.
Gotcha. The live image is being created with chronyd enabled. Normally it is installed disabled and anaconda enables the service if --nontp is not specified, so this is a bug in the creation of the live payload.
Well, we aren't doing anything special in the live kickstarts... chrony is enabled by default as part of the preset. Additionally, don't we want chrony running in the live system?
Can't anaconda disable it if it does see --nontp?
anaconda-21.48.10-1.fc21 has been submitted as an update for Fedora 21.
Package anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-21.48.10-1.fc21 pykickstart-1.99.63-2.fc21 python-blivet-0.61.5-1.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-21.48.10-1.fc21, pykickstart-1.99.63-2.fc21, python-blivet-0.61.5-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.