...
What were you trying to do that didn't work? Migrate newly created ifcfg-br0 and ifcfg-br1 files to the new NetworkManager format using nmcli connection migrate without rebooting my system. How reproducible: nmcli connection migrate The above command doesn't pick up on recently created /etc/sysconfig/network-scripts/ scripts such as ifcfg-br0 that my own bash script creates when setting up kvm. However, if you reboot Red Hat, if you run the migration command again nmcli connection migrate, this time it picks up on the existence of the ifcfg-br0 and ifcfg-br1 files and migrates them properly. Why does it take a reboot for the migrate command to detect the new files in /etc/sysconfig/network-scripts/? Neither running nmcli connection reload{{ or }}systemctl restart NetworkManager{{ causes nmcli connection migrate to refresh the list of network-scripts to migrate newly configured interfaces in the old format.}} https://forums.rockylinux.org/t/nmcli-connection-migrate-doesnt-know-about-recently-added-ifcfg-br0-in-etc-sysconfig-network-scripts-until-reboot/12437 Steps to reproduce Create and configure a new ifcfg-br0 interface file in /etc/sysconfig/network-scripts/ using the old format. Run nmcli connection migrate ifcfg-br0 is not migrated. Reboot Run nmcli connection migrate ifcfg-br0 is migrated now. Expected results nmcli connection migrate should not rely on a cache and scan for newly created old style interface files. I shouldn't have to reboot to migrate newly created network scripts (in the old format). Actual results Nothing is migrated properly until reboot. Maybe provide a command / way to rescan for old interface files / configured connections?
Cannot Reproduce
Click on a version to see all relevant bugs
Red Hat Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.