Network-scripts deprecation in Rocky Linux 9 affecting ifcfg persistence

Transition to NetworkManager

Rocky Linux 9 removes legacy network-scripts by default, shifting primary interface management to NetworkManager. In previous versions, manual edits to files in /etc/sysconfig/network-scripts/ were often sufficient to define static IP configurations that persisted across reboots via the network service.

Configuration Sync Uncertainty

When migrating environments to Rocky Linux 9, there is a risk that static configurations defined in ifcfg files are not automatically recognized by the NetworkManager daemon. This creates a discrepancy between the disk‑based configuration and the active runtime state if the profiles are not explicitly loaded into the manager.

What is the documented behavior for NetworkManager when encountering legacy ifcfg files without an associated active profile? Does nmcli connection reload guarantee the synchronization of all legacy script parameters into the current runtime state?