Bug 1414120

Summary: Bonded Interface is created wrong during kickstart
Product: Red Hat Enterprise Linux 7 Reporter: Josh Foots <jfoots>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: cww
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-19 17:05:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1420851    

Description Josh Foots 2017-01-17 19:57:56 UTC 
Description of problem:

Line from kickstart:

network --device=bond0 --bondslaves=en0,en1 --bondopts=mode=active-backup,miimon=100 --noipv6 --bootproto static --ip=192.168.0.22 --netmask=255.255.255.000 --gateway=192.168.0.254 --nameserver=192.168.0.255 --hostname test.example.com
network --device=en0 --activate
network --device=en1 --activate

after the build completes, bond0 is up and NIC ens224 is active. the other slave NIC is _ens192. When I failover to _ens192 using `ifenslave -c bond0 _ens192` the command succeeds but then bond0 is no longer reachable (can't even ping the gateway). 


Version-Release number of selected component (if applicable):


How reproducible:
Very

Steps to Reproduce:
1. Create a kickstart with the bonding options in  https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html#sect-kickstart-commands
2. Kickstart system
3.

Actual results:

bond0 is up and NIC ens224 is active. the other slave NIC is _ens192. When I failover to _ens192 using `ifenslave -c bond0 _ens192` the command succeeds but then bond0 is no longer reachable (can't even ping the gateway). 


Expected results:

For second nic to function properly.

Additional info: