Bug 2217527

Summary: NetworkManager: communicate that ifcfg will not implement new features
Product: Red Hat Enterprise Linux 9 Reporter: Beniamino Galvani <bgalvani>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.3CC: bgalvani, lrintel, mmuehlfe, rkhan, sfaye, sukulkar, till
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-19 12:53:05 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 Beniamino Galvani 2023-06-26 14:41:02 UTC 
By default NetworkManager stores profiles in the keyfile format on RHEL9; in alternative, the old ifcfg format is still supported and will be used if the user manually sets 'plugins=ifcfg-rh' in the configuration and then creates a new profile.

The ifcfg settings plugin is now deprecated upstream [1]; this means that new properties will not be supported for profiles stored in ifcfg format. To inform users about the change, we are going to:

  1. update the documentation (man pages, etc.) to state that ifcfg is deprecated
  2. log a message at startup when a profile is found in ifcfg format
  3. report an error when updating a profile in ifcfg format and there are unsupported properties. At the moment the only unsupported properties are 'link.*'
  4. add an entry to release notes

[1] https://lists.freedesktop.org/archives/networkmanager/2023-May/000103.html