Created attachment 774929 [details] initial_setup timezone spoke patch When run from the Fedora arm images initial-setup will show a timezone spoke as no timezone has been selected yet. But currently it does not matter if the uses goes into the spoke and actually makes changes there as the settings are never written to the system. I've 2 patch fixing this (note these apply on top of the patches from bug 972362): initial_setup-timezone.patch: Actually call the execute method of the timezone kickstart object anaconda-ntp.patch: anaconda was using a write to a /tmp/foo file, then mv file to /etc/chrony,conf, but this results in a /tmp file selinux context, and then chronyd fails to start as it cannot read files with such an selinux context, this patch fixes this in a simple matter by copying the file from /tmp/foo to /etc/chrony,conf, which keeps the existing /etc/chrony,conf's selinux context (or will use the proper default context for the new file if the file does not yet exist).
Created attachment 774932 [details] anaconda ntp patch
Thanks. I'll forward those patches to anaconda-patches.
Thanks, can you also take a look at bug 972362 and 985572 please ?
(In reply to Hans de Goede from comment #3) > Thanks, can you also take a look at bug 972362 and 985572 please ? Absolutely, going through them one after another.
anaconda-20.12-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.12-1.fc20
Package anaconda-20.12-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-20.12-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16040/anaconda-20.12-1.fc20 then log in and leave karma (feedback).
anaconda-20.13-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.13-1.fc20
initial-setup-0.3.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/initial-setup-0.3.8-1.fc20
anaconda-20.14-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.14-1.fc20
anaconda-20.15-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.15-1.fc20
anaconda-20.16-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.16-1.fc20
anaconda-20.17-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.17-1.fc20
anaconda-20.17-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
initial-setup-0.3.9-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/initial-setup-0.3.9-1.fc20
initial-setup-0.3.10-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/initial-setup-0.3.10-1.fc20
Package initial-setup-0.3.10-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing initial-setup-0.3.10-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20701/initial-setup-0.3.10-1.fc20 then log in and leave karma (feedback).
initial-setup-0.3.10-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.