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:
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