Bug 602185
| Summary: | Fedora 13 minimal installation lacks network configuration | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Panos Kavalagios <Panos.Kavalagios> | |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | 16 | CC: | dcbw, harald, jmoskovc, jpopelka, maurizio.antillon | |
| Target Milestone: | --- | Keywords: | Reopened | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 824808 824809 (view as bug list) | Environment: | ||
| Last Closed: | 2013-02-14 02:39:44 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 824808, 824809 | |||
|
Description
Panos Kavalagios
2010-06-09 10:36:05 UTC
I think this is similar problem as in bug #557112 (network not set up after media install in F-12). Please read David Cantrell's comment there https://bugzilla.redhat.com/show_bug.cgi?id=557112#c9 Bug #557112 is now assigned to NetworkManager, so I'm passing this one there too. Dan, if you consider this one as duplicate, close it so. According to Mr. David Cantrell's comment, there is a third workaround to set up network during media installation for repositories, so that the network settings will be copied later over the new installation. Indeed, that well hidden information could serve as a resolution to the inconvenience reported on the present report. I cannot see it as a duplicate of bug 557112, since that reports problems setting up network, which I didn't face. To sum up the two new workarounds: c. On the software set and repositories installer's screen, click on the Fedora 13 repository. A network configuration screen will be popped up. Network configuration set on this screen is migrated to the new installation. After booting the new system, issue "service network start" to access Internet. d. Wait for Fedora 14 where network configuration details will be given by the users during installation. I think I'm satisfied with the above workaround and future installer's changes. You may close the ticket with a fixed in F14 resolution. Ok, I don't think this is actually an NM thing since it deals with network setup in the installer stages, which is where network setup is usually initially configured until the full install, at which point you can use ifcfg files or nm-connection-editor to do the setup. Well, that's exactly problem. The script nm-connection-editor or the NetworkManager-gnome package is not included in the minimal installation. But I agree, the overall inconvenience looks that it can be charged to anaconda or to the software set of the minimal installation. Anaconda future changes will work fine on the network configuration issue anyway. Nothing was done yet. Even though I have set-up my network correctly a minimal system installation of F16 ended up with a system having no properly working network. Only the loopback interface was up and after manually issuing "systemctl start network.service" my ethernet interface was enabled, but unfortunately with no gateway, even though it was correctly set in the ifcfg script. The issue was for static ethernet configuration and the problem was that gateway was declared as GATEWAY0 in the following file: /etc/sysconfig/network-scripts/ifcfg-p5p1 I have removed the trailing zero and the route information was corrected and defaulted to the declarared gateway. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed. |