Description of problem: IF bond type device is to be part of bridge device, the bond device is not initializing, and therefore inoperative Version-Release number of selected component (if applicable): How reproducible: configure bond device and make it part of bridge device Steps to Reproduce: /etc/sysconfig/network-scripts/ifcfg-br0 DEVICE=br0 TYPE=Bridge BOOTPROTO=none IPADDR=192.168.1.1 NETMASK=255.255.255.0 ONBOOT=yes USERCTL=no DELAY=0 STP=off /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE=bond0 TYPE=Bonding BRIDGE=br0 ONBOOT=yes BOOTPROTO=none USERCTL=no the bond0 device is not initialized(slaves are not enslaved). the bond0 device is not added to the br0 device (cause it's added prematurly - before enslaving slaves) Actual results: neither bond0 nor br0 is properly configured by /sbin/ifup Expected results: All OK Additional info: /sbin/ifup:192 brctl addif statement fails becaouse no enslaved devices in bond0 /sbin/ifup:196 exit 0 statement makes bond0 to exit without enslaving slaves.
is there anybody out there ?
This does look like an issue. No patch available as of yet.
I also noticed, that even I initialize such config by hand, then during system shutdown bridge device can't take itself down, as not all subdevices were shut down.
It's going to be 7 months on Xmas ;)
Created attachment 220341 [details] ifup patch to handle bondX devices This hasn't been fixed in over a year, which is really lame for a so-called "Enterprise-grade" distribution. Here's a 5 minutes patch. I'm sure you can do better.
It's over two years now! Wow, great speed fixing easy things! Surely RHEL gains my trust here.
*** This bug has been marked as a duplicate of bug 463014 ***