-----Original Message----- From: Basil Chupin To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] oh crap.... Date: Wed, 13 Mar 2013 15:27:39 +1100 On 13/03/13 12:13, Robert Schweikert wrote:

Well,

Still a few hours to the release, thus I'll take the liberty to post to factory ;)

After switching my repos to 12.3 from 12.2, running "zypper in zypper" and then "zypper dup" I ended up with a weird network state.

I thought that the command (as root) is zypper refresh followed by zypper dup [pruned] BC -----Original Message----- Sometimes, when (expecting) drastic changed happen to zypper & Co, it is safer to update the updater itself first, followed by the rest (dup) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 13/03/13 18:51, Hans Witvliet wrote:

-----Original Message----- From: Basil Chupin To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] oh crap.... Date: Wed, 13 Mar 2013 15:27:39 +1100

On 13/03/13 12:13, Robert Schweikert wrote:

...

Well,

Still a few hours to the release, thus I'll take the liberty to post to factory ;)

After switching my repos to 12.3 from 12.2, running "zypper in zypper" and then "zypper dup" I ended up with a weird network state. I thought that the command (as root) is

zypper refresh

followed by

zypper dup

[pruned]

BC

-----Original Message-----

Sometimes, when (expecting) drastic changed happen to zypper & Co, it is safer to update the updater itself first, followed by the rest (dup)

Never been told that. I have always used = without any problems - the commands I mentioned above. The commands would also upgrade zypper - if it needed upgrading to begin with. And, of course, the next time you did run zypper <whatever> the upgraded zypper would find any anomalies and download and install the latest files anyway. zypper is not just a pretty face you know :-) . BC -- Using openSUSE 12.3 x86_64 with KDE 4.10.1 & kernel 3.8.2-1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 03/13/2013 07:47 AM, Robert Schweikert wrote:

On 03/13/2013 04:01 AM, Klaus Kaempf wrote:

...

* Robert Schweikert [Mar 13. 2013 02:14]:

...

Well,

Still a few hours to the release, thus I'll take the liberty to post to factory ;)

After switching my repos to 12.3 from 12.2, running "zypper in zypper" and then "zypper dup" I ended up with a weird network state.

The network has a bridge configured and there is one ethernet card. [...]

Yeah, know bug, reported here:

https://bugzilla.novell.com/show_bug.cgi?id=803019

Thanks for the pointer, although I would hardly call the bug resolved as it is obviously still happening.

OK, now I get it. The root cause is really that NetworkManager is running after the upgrade to 12.3 although it was disabled prior to the upgrade. Disabling NetworkManager, then stopping it and restarting the network puts everything back the way it is supposed to be. Thus somehwre in the upgrade process we forgot to check whether NetworkManager was enable or disabled on tha machine and we just turn it on by default :( Well, everything is release, too late..... Thanks again for the help. Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 03/13/2013 02:17 PM, Christian Boltz wrote:

Hello,

Am Mittwoch, 13. März 2013 schrieb Robert Schweikert:

...

On 03/13/2013 07:47 AM, Robert Schweikert wrote:

...

On 03/13/2013 04:01 AM, Klaus Kaempf wrote:

...

https://bugzilla.novell.com/show_bug.cgi?id=803019

Thanks for the pointer, although I would hardly call the bug resolved as it is obviously still happening.

OK, now I get it. The root cause is really that NetworkManager is running after the upgrade to 12.3 although it was disabled prior to the upgrade.

Disabling NetworkManager, then stopping it and restarting the network puts everything back the way it is supposed to be. Thus somehwre in the upgrade process we forgot to check whether NetworkManager was enable or disabled on tha machine and we just turn it on by default :(

Well, everything is release, too late.....

AFAIK the switch (dropping NETWORKMANAGER variable in sysconfig and enabling NetworkManager.service or network.service) is done in a %post script (don't ask of which package).

This also means we can still release an update to fix it at least for all the people who enable the update repo while upgrading.

If all the bugs about this are already closed as fixed, please open a new one ;-)

Not all bugs were closed, but I couldn't figure out if the bugs that are still open would actually address this issue if fixed. Thus there is a new bug: 809233 Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org