One of our test cases uses bonding configuration and the resulting ks.cfg is not the same as the one passed to anaconda.

Version-Release number of selected component (if applicable):
anaconda-13.21.206-1.el6.x86_64
RHEL6.5-20130913.0

Steps to Reproduce: 
 1. Obtain a machine with two Ethernet ports connected to an Ethernet switch


 1. Start kickstart installation of the system 
 2. Ensure that kickstart contains
      + network --bootproto=dhcp --device=bond0 --bondslaves=eth0,eth1 --bondopts=mode=balance-rr,arp_interval=100,arp_ip_target=ddd.ddd.ddd.ddd


where ddd.ddd.ddd.ddd is the IP address of the default GW for the network. 

 3. Ensure that bond has been set up properly during installation in %post

 4. Also check bond setup on  the installed system



Expected results:
 1. Installation should pass without errors
 2. Bond has been properly set up either during the installation and on the
    installed system

 3. After system is installed check network statement in /root/anaconda-ks.cfg,
    it should contain all channel bonding specific options specified in the
    original ks.


This contains:
 
network --onboot yes --device bond0 --mtu=1500 --bootproto dhcp
network --onboot yes --device eth0 --noipv4 --noipv6
network --onboot yes --device eth1 --noipv4 --noipv6



You can check above mentioned setup by inspecting:

  * /sys/class/net/bond0/bonding/slaves - should contain

    eth0,eth1

  * /sys/class/net/bond0/bonding/mode should contain
    balance-rr and/or 0

  * /sys/class/net/bond0/bonding/arp_interval should contain 100
  * /sys/class/net/bond0/bonding/arp_ip_target should contain ddd.ddd.ddd.ddd


^^^^ this was all correct on the installed system.