Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1494265 - Dracut can not use jumbo frames for interfaces on a bond.
Dracut can not use jumbo frames for interfaces on a bond.
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dracut (Show other bugs)
7.4
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Lukáš Nykrýn
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-21 17:28 EDT by Robert LeBlanc
Modified: 2018-04-10 14:11 EDT (History)
3 users (show)

See Also:
Fixed In Version: dracut-033-520.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 14:11:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Adds MTU parameter to dracut bond= and configures the bond with the MTU. (2.43 KB, patch)
2017-09-21 17:28 EDT, Robert LeBlanc
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0964 None None None 2018-04-10 14:11 EDT

  None (edit)
Description Robert LeBlanc 2017-09-21 17:28:59 EDT
Created attachment 1329216 [details]
Adds MTU parameter to dracut bond= and configures the bond with the MTU.

Description of problem:
When configuring an interface on a bond to use jumbo frames in dracut, the interfaces are all set to 1500.

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

How reproducible:
Always

Steps to Reproduce:
1. Add ip=10.4.64.21::10.4.64.1:255.255.192.0::br0.1000:none:9000 bond=bond0:eth0:mode=1 bridge=br0:bond0 vlan=br0.1000:br0 to the command line (may also need rd.neednet=1 if not booting over network).
2. Clear out /etc/sysconfig/network-scripts/ifcfg-*
3. Reboot

Actual results:
# ip link
...
4: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
...
11: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000
12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
13: br0.1000@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000

Expected results:
Add ip=10.4.64.21::10.4.64.1:255.255.192.0::br0.1000:none:9000 bond=bond0:eth0:mode=1:9000 bridge=br0:bond0 vlan=br0.1000:br0 to the command line

ip link:
...
4: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
...
11: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000
12: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
13: br0.1000@br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000

Additional info:
Upstream dracut almost has it right with commit 292548be6ec8e701dab1a532ca072707e890b12e, but there is an error in ifup.sh where $netif should be $bondname. I submitted https://github.com/dracutdevs/dracut/pull/286 to fix that. I'm attaching a good patch that works correctly.
Comment 2 Lukáš Nykrýn 2017-09-22 03:32:41 EDT
Patch looks good to me, let's just wait for the upstream review.
Comment 3 Robert LeBlanc 2017-10-09 12:00:32 EDT
Upstream merged the patch.
Comment 9 errata-xmlrpc 2018-04-10 14:11:08 EDT
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://access.redhat.com/errata/RHBA-2018:0964

Note You need to log in before you can comment on or make changes to this bug.