https://bugzilla.novell.com/show_bug.cgi?id=809233
https://bugzilla.novell.com/show_bug.cgi?id=809233#c1
Marius Tomaschewski
On a system (openSUSE 12.2) where NetworkManager was disabled, the upgrade to openSUSE 12.3 causes NetworkManager to be enabled and running after reboot.
Depending on the network configuration this may leave the network in an inconsistent state and the user may be unable to have network connectivity.
Depending on which network configuration exactly? IMO it is a a duplicate of bnc#803058 and it were in fact not an update from 12.2 to 12.3 final, but 12.3-<some beta> to 12.3. sysconfig contains migration hooks from versions that were using the NETWORKMANAGER variable before and in case of disabled NetworkManager it stops and disables it: case $NETWORKMANAGER in no) # NetworkManager.service were always started before; stop # and disable it, so /etc/init.d/network isn't masked... /usr/bin/systemctl stop NetworkManager.service || : /usr/bin/systemctl --force disable NetworkManager.service || : rm -f /dev/.sysconfig/network/migrate_nm_variable || : ;; The migration is done only, when the previous sysconfig were using the NETWORKMANAGER variable, that is a NETWORKMANAGER=no added later to the /etc/sysconfig/network/config file, does not trigger the migration. When you think this issue still exists, remove the duplicate flag and provide complete description about the update scenario incl. sysconfig and NetworkManager package versions setting of the variable, how the update were done (CD boot + update?, zypper dup?). *** This bug has been marked as a duplicate of bug 803058 *** http://bugzilla.novell.com/show_bug.cgi?id=803058 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.