| Summary: | Update ifup/ifdown NetworkManager interaction | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dan Winship <danw> | ||||
| Component: | initscripts | Assignee: | Lukáš Nykrýn <lnykryn> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | jonathan, lnykryn, vpavlin | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1036847 (view as bug list) | Environment: | |||||
| Last Closed: | 2015-06-29 13:18:54 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: | |||||
| Attachments: |
|
||||||
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. |
Created attachment 831577 [details] patch to initscripts git ifup and ifdown have one problem that's new in F20 and another that has always existed but might be more commonly seen in F20: 1. In its default configuration in F20, NetworkManager no longer automatically reloads ifcfg files when they change, so we need to reload them manually, so that, eg, creating/editing an ifcfg file and then using "ifup" on it has the expected behavior. 2. Just because an ifcfg file has a UUID= line doesn't mean that it's managed by NM. (In particular, if someone changes their default Ethernet connection from "TYPE=Ethernet" to "TYPE=OVSPort", but doesn't remove the UUID line, then ifup will currently hand it off to NM, but NM won't know what to do with it. Instead, ifup should be handling it itself.) The attached patch fixes both of these. Note that the "nmcli con load" part requires NetworkManager >= 0.9.9.0-18.git20131003. I tried building an initscripts package with "Conflicts: NetworkManager < 0.9.9.0-18.git20131003", but it doesn't seem to have any effect, and I can't figure out why. (Using just "0.9.9.0-18" for the version doesn't work either.) Anyway, if you can't make the conflict work, then you could just add "2>/dev/null" to the end of the "nmcli con load" line, and then people who hadn't updated NM yet would just not get that part of the bugfix.