Bug 193236

Summary: /sbin/ifup fails for Type=Bonding and BRIDGE=br0
Product: Red Hat Enterprise Linux 4 Reporter: Rafal Wijata <wijata>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: djuran, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-23 19:14:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ifup patch to handle bondX devices none

Description Rafal Wijata 2006-05-26 14:18:25 UTC 
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.
Comment 1 Rafal Wijata 2006-07-12 08:44:28 UTC 
is there anybody out there ?
Comment 2 Bill Nottingham 2006-07-12 13:54:57 UTC 
This does look like an issue. No patch available as of yet.
Comment 3 Rafal Wijata 2006-07-20 08:25:14 UTC 
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.
Comment 4 Rafal Wijata 2006-12-15 10:54:27 UTC 
It's going to be 7 months on Xmas ;)
Comment 5 Kilian Cavalotti 2007-10-08 23:34:33 UTC 
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.
Comment 6 Rafal Wijata 2008-07-28 08:22:47 UTC 
It's over two years now! Wow, great speed fixing easy things! Surely RHEL gains
my trust here.
Comment 7 Bill Nottingham 2008-09-23 19:14:31 UTC 

*** This bug has been marked as a duplicate of bug 463014 ***