(In reply to Till Maas from comment #0)
> Description of problem:
> In RHEL 9, NM defaults to storing profiles as keyfiles. To reduce confusion
> for users looking into /etc/sysconfig/network-scripts/ add a README or
> similar there to mention that profiles might now be stored at
> /etc/NetworkManager/system-connections/
> 
> Acceptance Criteria
> 
> Given a RHEL 9+ or Fedora 36+ system
> When listing the content of /etc/sysconfig/network-scripts/
> Then there will be a hint that network configuration is now in
> /etc/NetworkManager/system-connections/
> 
> 
> TBD:
> This could be a README.txt with a text like:
> 
> 
> Please check /etc/NetworkManager/system-connections/ for network
> configuration files. More information is available at https://...  [Do we
> have a URL that we can use here?]
> 

I think we could add the link for the NetworkManager migration tool blog post.. I assume this blog post will have an explanation about where are the configuration files now.

> The file name could also be more explicit, such as
> 
> "Note: Network configuration moved other directory.txt"

*** Bug 2074742 has been marked as a duplicate of this bug. ***

What do you think about the following text for the README file:

--------------------------------------------------
NetworkManager stores new network profiles in keyfile format in the
/etc/NetworkManager/system-connections/ directory.

Previously, NetworkManager stored network profiles in ifcfg format
in this directory (/etc/sysconfig/network-scripts/). However, the ifcfg
format is deprecated. By default, NetworkManager no longer creates
new profiles in this format.

Connection profiles in keyfile format have many benefits. For example,
this format is INI file-based and can easily be parsed and generated.

Each section in NetworkManager keyfiles corresponds to a NetworkManager
setting name as described in the nm-settings(5) and nm-settings-keyfile(5)
man pages. Each key-value-pair in a section is one of the properties
listed in the settings specification of the man page.

If you still use network profiles in ifcfg format, consider migrating
them to keyfile format. To migrate all profiles at once, enter: 

# nmcli connection migrate

This command migrates all profiles from ifcfg format to keyfile
format and stores them in /etc/NetworkManager/system-connections/.

Alternatively, to migrate only a specific profile, enter:

# nmcli connection migrate <profile_name|UUID|D-Bus_path>

For further details, see:
* nm-settings-keyfile(5)
* nmcli(1)
--------------------------------------------------

This text provides some background information, lists benefits, and mentions the relevant man pages.

If you add the README in 9.0, skip the paragraphs about migration and append them in 9.1.




> The file name could also be more explicit, such as
> "Note: Network configuration moved other directory.txt"

I would not use such a file name. It's too long and it contains spaces, which requires to use quotes or escape the spaces to display the file.
Let's call it simply README - same as the file systemd devels put into /var/log/ to inform about Journal.
(just my opinion)

(In reply to Marc Muehlfeld from comment #3)
> What do you think about the following text for the README file:
> 
> --------------------------------------------------
> NetworkManager stores new network profiles in keyfile format in the
> /etc/NetworkManager/system-connections/ directory.
> 
> Previously, NetworkManager stored network profiles in ifcfg format
> in this directory (/etc/sysconfig/network-scripts/). However, the ifcfg
> format is deprecated. By default, NetworkManager no longer creates
> new profiles in this format.
> 
> Connection profiles in keyfile format have many benefits. For example,
> this format is INI file-based and can easily be parsed and generated.
> 
> Each section in NetworkManager keyfiles corresponds to a NetworkManager
> setting name as described in the nm-settings(5) and nm-settings-keyfile(5)
> man pages. Each key-value-pair in a section is one of the properties
> listed in the settings specification of the man page.
> 
> If you still use network profiles in ifcfg format, consider migrating
> them to keyfile format. To migrate all profiles at once, enter: 
> 
> # nmcli connection migrate
> 
> This command migrates all profiles from ifcfg format to keyfile
> format and stores them in /etc/NetworkManager/system-connections/.
> 
> Alternatively, to migrate only a specific profile, enter:
> 
> # nmcli connection migrate <profile_name|UUID|D-Bus_path>
> 
> For further details, see:
> * nm-settings-keyfile(5)
> * nmcli(1)
> --------------------------------------------------
> 
> This text provides some background information, lists benefits, and mentions
> the relevant man pages.
> 
> If you add the README in 9.0, skip the paragraphs about migration and append
> them in 9.1.
> 
> 
> 
> 
> > The file name could also be more explicit, such as
> > "Note: Network configuration moved other directory.txt"
> 
> I would not use such a file name. It's too long and it contains spaces,
> which requires to use quotes or escape the spaces to display the file.
> Let's call it simply README - same as the file systemd devels put into
> /var/log/ to inform about Journal.
> (just my opinion)

Thank you very much Marc, I included this text.

Fedora MR link: https://src.fedoraproject.org/rpms/NetworkManager/pull-request/11

The /etc/sysconfig/network-scripts/readme-ifcfg-rh.txt file is present on system with NetworkManager-1.39.6-1.el9 → VERIFIED.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8265