Default autoconnections are created by NM for devices without ifcfg config (that would be created based on boot configuration or kickstart). Changing the value to False is causing that the device is not autoactivated at the beginning of the installation due to race when anaconda is starting faster then NM. --- pyanaconda/network.py | 2 -- 1 file changed, 2 deletions(-)
diff --git a/pyanaconda/network.py b/pyanaconda/network.py index 51f29d9..c7ba0cd 100644 --- a/pyanaconda/network.py +++ b/pyanaconda/network.py @@ -281,8 +281,6 @@ def dumpMissingDefaultIfcfgs(): try: nm.nm_update_settings_of_device(devname, [['connection', 'id', devname, None]]) log.debug("network: dumping ifcfg file for default autoconnection on %s", devname) - nm.nm_update_settings_of_device(devname, [['connection', 'autoconnect', False, None]]) - log.debug("network: setting autoconnect of %s to False", devname) except nm.SettingsNotFoundError: log.debug("network: no ifcfg file for %s", devname) rv.append(devname)
Default autoconnections are created by NM for devices without ifcfg config (that would be created based on boot configuration or kickstart). Changing the value to False is causing that the device is not autoactivated at the beginning of the installation due to race when anaconda is starting faster then NM.
Looks good.
- Chris
anaconda-patches@lists.fedorahosted.org