Comment # 1 on bug 963241 from
Some more info.

When debug wicked logging is !debug, and at least the eno1 interface shows up,
apparently wicked.service is up.  For some reason, adding the debug logging
causes it to fail.

Anyway with the the logging off I can see the bridge in brctl

 brctl show
  bridge name     bridge id               STP enabled     interfaces
  br0             8000.0cc47a489a7e       no              eno1

But in dmesg

 dmesg | grep -i br0
  [   98.484646] systemd[1]: sys-subsystem-net-devices-br0.device changed dead
-> plugged
  [   98.484654] systemd[1]: sys-devices-virtual-net-br0.device changed dead ->
plugged

and systemctl

 systemctl status wicked.service -l
 wicked.service - wicked managed network interfaces
   Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled)
   Active: active (exited) since Fri 2016-01-22 09:32:10 PST; 2h 10min ago
  Process: 1364 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited,
status=0/SUCCESS)
 Main PID: 1364 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/wicked.service

 Jan 22 09:39:43 aleph.homelan wicked[1364]: lo              up
 Jan 22 09:39:43 aleph.homelan wicked[1364]: eno1            enslaved
 Jan 22 09:39:43 aleph.homelan wicked[1364]: br0             device-not-running

 journalctl -xb | grep -i br0
  Jan 22 09:35:58 aleph.homelan systemd[1]:
sys-subsystem-net-devices-br0.device changed dead -> plugged
  Jan 22 09:35:58 aleph.homelan systemd[1]: sys-devices-virtual-net-br0.device
changed dead -> plugged
  Jan 22 09:32:08 aleph.homelan wickedd[1358]: Unable to set br0 attribute
bridge/ageing_time=0: Operation not permitted
  Jan 22 09:32:08 aleph.homelan wickedd[1358]: ni_system_bridge_setup: failed
to update sysfs attributes for br0
  Jan 22 09:32:08 aleph.homelan wickedd-nanny[1361]: device br0: call to
org.opensuse.Network.Bridge.changeDevice() failed: General failure
  Jan 22 09:39:43 aleph.homelan wicked[1364]: br0            
device-not-running


That

Unable to set br0 attribute bridge/ageing_time=0: Operation not permitted

looks like a problem.  Never heard of that attribute though.


You are receiving this mail because: