mNo edit summary |
(adding release notes tracker) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Remove ifcfg support in NetworkManager <!-- The name of your change proposal --> = | = Remove ifcfg support in NetworkManager <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
| Line 34: | Line 33: | ||
* [https://discussion.fedoraproject.org/t/f41-change-proposal-remove-ifcfg-support-in-networkmanager-system-wide/119455 Discussion thread] | * [https://discussion.fedoraproject.org/t/f41-change-proposal-remove-ifcfg-support-in-networkmanager-system-wide/119455 Discussion thread] | ||
* FESCo issue: [https://pagure.io/fesco/issue/3228 #3228] | * FESCo issue: [https://pagure.io/fesco/issue/3228 #3228] | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2296272 #2296272] | ||
* Release notes tracker: | * Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/96 #96] | ||
== Detailed Description == | == Detailed Description == | ||
Latest revision as of 15:20, 2 October 2024
Remove ifcfg support in NetworkManager
Summary
Remove support for connection profiles stored in ifcfg format in NetworkManager.
Owner
- Name: Beniamino Galvani, Fernando Fernández Mancera, Till Maas
- Email: <bgalvani@redhat.com>, <ferferna@redhat.com>, <till@fedoraproject.org>
Current status
- Targeted release: Fedora Linux 41
- Last updated: 2024-10-02
- Announced
- Discussion thread
- FESCo issue: #3228
- Tracker bug: #2296272
- Release notes tracker: #96
Detailed Description
NetworkManager supports different formats to persist connection profiles to disk. The two formats currently in use in Fedora are keyfile and ifcfg.
Keyfile is the native and preferred format. It supports all the connection types and all the features. Ifcfg is compatible with the old network-scripts. It only supports a limited set of connection types, and it is deprecated upstream.
This change proposal aims at removing NetworkManager support for ifcfg files in Fedora. This is the last step of a process started several releases ago:
- in Fedora 33, the default connection format was changed from ifcfg to keyfile;
- in Fedora 36, the plugin that handles ifcfg files was shipped in a separate package and was not included in new installations;
- since Fedora 39, the NetworkManager daemon automatically migrates ifcfg files to the keyfile format.
Benefit to Fedora
Since ifcfg support is going to be removed upstream, it must also be removed in Fedora. Keyfile is a valid and better replacement.
Scope
- Proposal owners: drop the following packages:
NetworkManager-initscripts-ifcfg-rhcontaining the ifcfg pluginNetworkManager-dispatcher-routing-rulescontaining a dispatcher script to apply routing rules in ifcfg formatNetworkManager-initscripts-updowncontaining alternative ifup/ifdown scripts compatible with initscripts commands, using NetworkManager.
- Other developers: N/A
- Release engineering: N/A
- Policies and guidelines: N/A
- Trademark approval: N/A
Upgrade/compatibility impact
At this point no users should have connection profiles stored in ifcfg format, as NetworkManager is automatically migrating them to keyfile since Fedora 39.
According to documentation , system upgrades are supported only over 2 releases at most (e.g. from 38 to 40); therefore, users upgrading to Fedora 41 must come from Fedora 39 or 40, which have the migration enabled.
If some users disabled the migration, they might still have ifcfg files in /etc/sysconfig/network-scripts. A “readme-ifcfg-rh.txt” file there warns users that the format is deprecated and is going to be removed.
How To Test
- Try to install the NetworkManager-initscripts-ifcfg-rh package
- The package is not available.
User Experience
See the “Upgrade/compatibility impact” section.
Dependencies
None
Contingency Plan
- Contingency mechanism: Revert the change, try again the next Fedora release.
- Contingency deadline: Beta freeze
- Blocks release? no
Documentation
No documentation change required.
Release Notes
The change needs to be mentioned in the Release Notes.