Bug 802879

Summary: network bridge after upgrade from 12.3 Beta 1 to RC 1 broken
Product: [openSUSE] openSUSE 12.3 Reporter: Lars Müller <lmuelle>
Component: NetworkAssignee: Marius Tomaschewski <mt>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: coolo, kkaempf, sboyce
Version: RC 1   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: No
Marketing QA Status: --- IT Deployment: ---

Description Lars Müller 2013-02-08 18:48:48 UTC
The bridged device worked well with openSUSE 12.3 Beta 1.

After upgrading via zypper dup to the RC 1 level an IP address was configured for the ethernet device and the bridge.

broken:

ip r s

default via 192.168.178.1 dev eth0  proto static 
127.0.0.0/8 dev lo  scope link 
192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.21 
192.168.178.0/24 dev br0  proto kernel  scope link  src 192.168.178.48 


ip a s

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP qlen 1000
    link/ether 2c:27:d7:1c:a3:c0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.21/24 brd 192.168.178.255 scope global eth0
    inet6 fe80::2e27:d7ff:fe1c:a3c0/64 scope link 
       valid_lft forever preferred_lft forever
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 2c:27:d7:1c:a3:c0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.48/24 brd 192.168.178.255 scope global br0
    inet6 2001:470:1f0b:2c7:2e27:d7ff:fe1c:a3c0/64 scope global dynamic 
       valid_lft 7146sec preferred_lft 3546sec
    inet6 fe80::2e27:d7ff:fe1c:a3c0/64 scope link 
       valid_lft forever preferred_lft forever


working after moving /etc/sysconfig/network/ifcfg-br0 to /etc/sysconfig/network/ifcfg-eth0 and prefixing all BRIDGE* lines with a # char.

ip r s

default via 192.168.178.1 dev eth0  proto static 
192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.48 
192.168.178.1 dev eth0  proto static  scope link 

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 2c:27:d7:1c:a3:c0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.48/24 brd 192.168.178.255 scope global eth0
    inet6 2001:470:1f0b:2c7:2e27:d7ff:fe1c:a3c0/64 scope global dynamic
       valid_lft 7045sec preferred_lft 3445sec
    inet6 fe80::2e27:d7ff:fe1c:a3c0/64 scope link
       valid_lft forever preferred_lft forever

As a bridged device isn't the default network interface configuration I don't consider this as a blocking issue.
Comment 1 Lars Müller 2013-02-08 18:52:34 UTC
Passing to Marius as sysconfig maintainer and adding Coolo to cc to check if this might be a blocker for the 12.3 release.
Comment 2 Klaus Kämpf 2013-02-11 08:18:56 UTC
Might be related to https://bugzilla.novell.com/show_bug.cgi?id=803019 (Default route missing for bridge interface (br0))
Comment 3 Sid Boyce 2013-02-11 14:11:12 UTC
I saw the similar here.
Some way through the zypper dup network stopped working.
Rebooted and completed the upgrade.

Network stopped again, br0 which uses eth0 had the expected static IP address.
It also brought up eth0 with a dhcp assigned address.

Yast2 network launched, deleted br0 and set eth0 to static IP address.
Yast2 network set up ifcfg-eth0 as shown.
sabre:~ # cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='192.168.10.21/24'
MTU=''
NAME='RTL8111/8168B PCI Express Gigabit Ethernet controller'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'

I did "ifconfig eth0 192.168.10.21" as restarting the network resulted in a dhcp assigned IP address.
It still changed eth0 via dhcp sometime later.
I have moved /sbin/dhclient and killed it and I also had to set up the default route manually.
Comment 4 Marius Tomaschewski 2013-02-18 14:12:39 UTC
sysconfig and most other packages has been changed to not use NETWORKMANAGER
variable any more, but a network.service alias link.

See also release notes bug #800771 and - still unfixed - bug #798348, to
adopt switching between NetworkManager and /etc/init.d/network in yast2.
[/etc/init.d/network is currently active only while miminal installation,
 in all other cases NetworkManager because yast2 is unable to switch it
 as needed.]

To enable NetworkManager, use:

  systemctl stop network.service
  systemctl --force enable NetworkManager.service
  systemctl start network.service

to disable NetworkManager, use:

  systemctl stop network.service
  systemctl --force disable NetworkManager.service
  systemctl start network.service

This command:
   systemctl --no-pager -p Id show network.service

reports "Id=NetworkManager.service" when NetworkManager acts as the network
service, "Id=network.service" means /etc/init.d/network.

I guess the dhclient on eth0 is started by NetworkManager... while you've
tried to set it up on br0.

Please use above commands to enable/disable NetworkManager as needed and
reboot. Does it work as expected after?
When not, and you are using /etc/init.d/network, please call "supportconfig"
(supportutils package) and attach the archive it creates.

But I guess, this is also a duplicate of bnc#798348 -- yast2 is unable to
switch between rcnetwork and NetworkManager. See also bnc#803058.
Comment 5 Marius Tomaschewski 2013-02-19 15:06:33 UTC
See also bug #803058. I'm resolving it as duplicate of it, because this
were an "zypper dup" update [while bug #798348 is about new installs].

*** This bug has been marked as a duplicate of bug 803058 ***
Comment 6 Marius Tomaschewski 2013-02-19 15:12:47 UTC
OK, update in NETWORKMANAGER=no case with sysconfig package with fix for
bug #803058 from home:mtomaschewski:tests/sysconfig finished / worked for
me, the "ifup network" with bridge on top of the physical interface were
still alive after "zypper dup" and it also came up again after a reboot.