http://bugzilla.novell.com/show_bug.cgi?id=908375
Bug ID: 908375
Summary: since wicked in 13.2, bridges don't come up on boot
Classification: openSUSE
Product: openSUSE Distribution
Version: 13.2
Hardware: x86-64
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Network
Assignee: bnc-team-screening@forge.provo.novell.com
Reporter: peter.maloney@brockmann-consult.de
QA Contact: qa-bugs@suse.de
Found By: ---
Blocker: ---
Since wicked was added in openSUSE 13.2, bridges don't come up on boot. I have
used bridges for years with previous releases and distros, and they work fine.
But since 13.2, the boot is delayed by wicked saying "a startup job is running"
for 30s or so, and when the system is up, the bridges are "UP" but have no ip
address.
root@petervm:/etc/sysconfig/network # cat ifcfg-br0
BOOTPROTO='static'
BRIDGE='yes'
BRIDGE_PORTS=''
BRIDGE_STP='on'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='10.99.0.25/16'
MTU=''
NAME='Ethernet Card 0'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
root@petervm:/etc/sysconfig/network # cat ifcfg-eth0
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='10.3.0.25/16'
MTU=''
NAME='Ethernet Card 0'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
root@petervm:/etc/sysconfig/network # ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
link/ether 4e:30:18:31:ac:03 brd ff:ff:ff:ff:ff:ff
inet 10.3.0.25/16 brd 10.3.255.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::4c30:18ff:fe31:ac03/64 scope link
valid_lft forever preferred_lft forever
3: br0: mtu 1500 qdisc noqueue state DOWN
group default
link/ether 4e:59:1e:2b:84:02 brd ff:ff:ff:ff:ff:ff
root@petervm:/etc/sysconfig/network # ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: mtu 1500 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether 4e:30:18:31:ac:03 brd ff:ff:ff:ff:ff:ff
3: br0: mtu 1500 qdisc noqueue state DOWN
mode DEFAULT group default
link/ether 4e:59:1e:2b:84:02 brd ff:ff:ff:ff:ff:ff
The log is quite useless:
Dec 04 14:42:06 petervm wickedd[441]: lo: address 127.0.0.1 covered by a static
lease
Dec 04 14:42:06 petervm wickedd[441]: lo: address ::1 covered by a static lease
Dec 04 14:42:36 petervm wicked[443]: device br0 failed: operation timed out
Dec 04 14:42:36 petervm wicked[443]: lo up
Dec 04 14:42:36 petervm wicked[443]: eth0 up
Dec 04 14:42:36 petervm wicked[443]: br0 setup-in-progress
I have this problem on both of my tumbleweed desktops, and I have reproduced it
above for this bug report in a freshly upgraded 13.2 VM.
On my 2 desktops, if I run "ifup br0" after logging in, it takes long, but
works otherwise. In this 13.2 VM, it doesn't work.
root@petervm:/etc/sysconfig/network # ifup br0
wicked: device br0 failed: operation timed out
br0 setup-in-progress
root@petervm:/etc/sysconfig/network # ip a dev br0
Command "dev" is unknown, try "ip addr help".
Dec 04 14:50:51 petervm wickedd[441]: ni_process_reap: process 1312 has not
exited yet; now doing a blocking waitpid()
Dec 04 14:51:41 petervm wicked[1309]: device br0 failed: operation timed out
To fix the long boot time on my desktops, I ran "systemctl disable wicked" and
wrote a simple init script that works fine with VLANs and everything. (I don't
really see the point of ugly files instead and never did... on Debian at least
the file is short and in one place, in a file named where tab-completion works,
but still extra learning and lost flexibility due to reinventing the wheel).
--
You are receiving this mail because:
You are on the CC list for the bug.
