Bug 1282679

Summary: Can't configure multiple bonds with dracut bond=
Product: Red Hat Enterprise Linux 7 Reporter: Derek Schrock <dereks>
Component: dracutAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: brendan.germain, dracut-maint-list, harald, jstodola, mosonkonrad, msvistun, pkotvan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 08:00:51 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: 1289485, 1313485    
Attachments:
Description Flags
Write bond.NAME.info files per bond= none

Description Derek Schrock 2015-11-17 04:45:38 UTC
Created attachment 1095219 [details]
Write bond.NAME.info files per bond=

Description of problem:

When you have multiple bond= options set only one bond is configured:

   ... rd.neednet=1 bond=bond0:ens1,ens3 bond=bond1:ens2,ens4 ip=bond0:dhcp ip=bond1:dhcp ...

During installation and after reboot only one of the bonds will be created.  I believe it will always be bond0 or depending on locale.

Version-Release number of selected component (if applicable):
RHEL 7.1 media dracut initrd.img


How reproducible:
Set the above boot options during installation.


Actual results:
Only one bond is created

Expected results:
Multiple bond interfaces to be created

Additional info:
See attached patch for dracut parse-bond.sh

Comment 2 Brendan Germain 2016-05-08 22:04:59 UTC
Also experiencing this problem and need the functionality of being able to create multiple bonds. Is there any update for this?

Thanks.

Comment 4 Peter Kotvan 2016-08-05 13:19:31 UTC
Verified on RHEL-7.3-20160729.1 with RHEL-7.3-20160729.1.

Comment 7 errata-xmlrpc 2016-11-04 08:00:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2530.html