Bug 809233

Summary:	NetworkManager setting is not respected during system upgrade
Product:	[openSUSE] openSUSE 12.3	Reporter:	Robert Schweikert <rjschwei>
Component:	Update Problems	Assignee:	Marius Tomaschewski <mt>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Robert Schweikert 2013-03-13 18:36:07 UTC

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.

If the system in question uses NIS one has to login as root from the login manager or at the console.

The user may address the problem by disabling network manager, stopping the running service, and restarting the network

# systemctl -f disable NetworkManager.service
# systemctl stop NetworkManager.service
# rcnetwork restart

This may be related to 

803019
798348
802879
802761
800771

Comment 1 Marius Tomaschewski 2013-03-18 15:38:19 UTC

(In reply to comment #0)
> 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 ***

Comment 2 Robert Schweikert 2013-03-27 16:02:55 UTC

This issue doe no longer exist.

Installed from 12.2 media and applied all upgrades, then changed the repos to 12.3 and ran "zypper dup". After the upgrade NM is not running as expected.

One comment about the previous entry. Please do not assume that I do not know what distribution I am running on my system. I did upgrade from 12.2 to 12.3 when I encountered the issue and not from, as was stated "12.3-<some beta> to 12.3"

Comment 3 Marius Tomaschewski 2013-03-27 16:47:55 UTC

(In reply to comment #2)
> This issue doe no longer exist.
> 
> Installed from 12.2 media and applied all upgrades, then changed the repos to
> 12.3 and ran "zypper dup". After the upgrade NM is not running as expected.

OK, thank you very much for the verification!