Bug 1278780
Summary: | WiFi credentials are not written in a fresh XFCE Spin installation | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Laurentiu Pancescu <lpancescu> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 25 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, lpancescu, rvykydal, vanmeeuwen+fedora, vtrefny |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-12 11:10:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Laurentiu Pancescu
2015-11-06 11:52:24 UTC
Did you set the WiFi before or after the installation finished? Your steps to reproduce implies you did it after the installation. We don't modify the system after the installation finishes. I setup WiFi after starting Anaconda, but before clicking "Begin installation" in the second screen. To be more specific, here are the steps: 1. Select English > US English in the Anaconda welcome screen 2. Add the German keyboard layout and remove the US one (this makes it easier to type passwords correctly in the following steps) 3. Setup WiFi using Network Manager from the XFCE tray 4. Select Europe/Berlin as time zone, and check that the NTP servers are working 5. Select the installation drive and reclaim free space 6. Set the hostname and domain 7. Click on Begin installation 8. Configure root password 9. Configure first regular user (with admin rights) 10. Reboot after the installation finished These are actually the same steps I performed in F21 and F22 - I was pleasantly surprised that Anaconda had already configured WiFi for me, when I started the installed system for the first time. Not anymore in F23. I think Anaconda saves an installation log in ~root. Should I upload it here? I can also reproduce the problem with the Fedora 24 XFCE Spin (fresh installation). The WiFi configuration files /etc/sysconfig/network-scripts/{ifcfg,keys}-MySSID were copied, but the SELinux user context is unconfined_u instead of system_u, like all the other files, including ifcfg-lo0. I used chcon from the Live CD, after the installation was complete, to set the user context of the two files to system_u; this didn't help after rebooting, same problem, so the user context might not make any difference in this case. However, I found the line "USERS=liveuser" at the end of ifcfg-MySSID. If I change liveuser into my user name, or simply remove the line completely, the WiFi works as expected, without having to do anything else. Probably Anaconda should either remove that line, or adapt it to specify the user created during the installation, instead of simply copying the file generated by Network Manager. The USERS option doesn't seem to be documented in /usr/share/doc/initscripts-version/sysconfig.txt, as the F24 Networking Guide implies (see 1.8. Additional Resources). This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |