Bug 669110

+++ This bug was initially created as a clone of Bug #651450 +++

Description of problem:
If a bonded interface is created and the slave interface includes the setting MASTER="bond0" (where bond0 is the bonded interface) the slave will not start.  If the double quotes are removed the slave interface will come up (ie; MASTER=bond0)

Version-Release number of selected component (if applicable):
kernel-2.6.35.6-45.fc14.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a bond0 interface in the normal manner. Eg sample config:
/etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE="bond0"
USERCTL="no"
BOOTPROTO="none"
ONBOOT="yes"
NETMASK="255.255.255.0"
IPADDR="172.16.98.12"
GATEWAY="172.16.98.2"

Next enslave an interface for bond0. Eg sample config:
/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
HWADDR="00:0C:29:5F:91:BF"
ONBOOT="yes"
BOOTPROTO="none"
USERCTL="no"
MASTER="bond0"
SLAVE="yes"

2. Load the bonding module for the bonded interface. Eg sample config:
/etc/modprobe.d/bonding.conf
alias bond0 bonding
options bond0 miimon=100 primary=eth0 mode=1

3. Reboot or modprobe bonding and restart the network service.  
  
Actual results:
The bonded interface will come up but will not have a slave and therefore is unable to communicate.

Expected results:
The bonded interface should bring up the slave interface and communicate as expected.

Additional info:
Removing the double quotes around the MASTER setting in the slave interface will allow the slave to start normally.  Eg; sample config:
/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE="eth0"
HWADDR="00:0C:29:5F:91:BF"
ONBOOT="yes"
BOOTPROTO="none"
USERCTL="no"
MASTER=bond0
SLAVE="yes"

--- Additional comment from gfidente on 2011-01-12 08:03:56 EST ---

Created attachment 473014 [details]
patches the ifup-eth and ifdown-eth scripts to make them parse the MASTER value correctly if in quotes

I'm experiencing the same issue, the error seems to be in the if{up,down}-eth scripts which incorrectly parse the ifcfg-eth* files. I'm attaching a proposed fix, which works for me.

--- Additional comment from gfidente on 2011-01-12 08:06:59 EST ---

this bug affects Red Hat Enterprise Linux 6 too

--- Additional comment from notting on 2011-01-12 12:21:01 EST ---

http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=abd88b50196806ef92f3daadd277420190c2d955

Will be in some future F-14 update.