Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAlexander Todorov
2013-09-18 10:15:17 UTC
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.
Comment 1Alexander Todorov
2013-09-18 10:17:37 UTC
*** Bug 1003864 has been marked as a duplicate of this bug. ***
Comment 9RHEL Program Management
2013-10-14 02:05:59 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
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.
http://rhn.redhat.com/errata/RHBA-2014-1380.html
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.