Description of problem:
If an interface belongs to a bridge ifup will try to add it to the bridge
_before_ it checks if the interface is a bond (and takes the apropriate steps to
bring the bond up). So adding the interface to the bridge will fail.

Version-Release number of selected component (if applicable):
initscripts-8.76.2-1.x86_64

How reproducible:
Every time

Steps to Reproduce:

[root@red network-scripts]# cat ifcfg-eth0 
DEVICE=eth0
HWADDR=00:17:08:4c:7e:e2
ONBOOT=yes
NM_CONTROLLED=no
MASTER=bond0
SLAVE=yes

[root@red network-scripts]# cat ifcfg-eth1 
DEVICE=eth1
HWADDR=00:17:08:4c:7e:e1
ONBOOT=yes
NM_CONTROLLED=no
MASTER=bond0
SLAVE=yes

[root@red network-scripts]# cat ifcfg-bond0 
DEVICE=bond0
TYPE=bonding
BRIDGE=br0
ONBOOT=yes

[root@red network-scripts]# cat ifcfg-br0 
DEVICE=br0
BOOTPROTO=static
IPADDR=10.9.224.200
NETMASK=255.255.240.0
TYPE=bridge
ONBOOT=yes

service network start

Actual results:
can't add bond0 to bridge br0: Invalid argument

Expected results:
bond0 up and connected to br0

Additional info:
Bringing the bond up before adding it to the bridge seems to solve the problem.
Patch for /etc/sysconfig/network-scripts/ifup-eth attached.

The problem also exists in RHEL.