Bug 1441744

Summary: Add support for ethtool_opts option
Product: Red Hat OpenStack Reporter: Pierre Blanc <pblanc>
Component: os-net-configAssignee: Dan Sneddon <dsneddon>
Status: CLOSED ERRATA QA Contact: mlammon
Severity: medium Docs Contact:
Priority: medium    
Version: 10.0 (Newton)CC: bfournie, dsneddon, hbrock, jjoyce, jslagle, mburns, nlevinki, rhel-osp-director-maint, vcojot
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: os-net-config-5.2.0-3.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-06 17:09:30 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:

Description Pierre Blanc 2017-04-12 15:22:17 UTC 
Description of problem:

Currently it is not possible to configure with nic-config file the ethtool options for an interface.

It is complicate to find a workaround, network interface is a key of a operating system, it can't be changed easily.


Additional info:

The patch exists on master:
https://review.openstack.org/#/c/392697/
Comment 1 Vincent S. Cojot 2017-04-12 15:26:41 UTC 
This is a huge issue because:
if you happen to manually write ETHTOOL_OPTS to the ifcfg files, then during a scale-up os-net-config will noticed and tear down/rebuild the network LIVE.

so the only workaround we have is to:
1) add lines to run ethtool into /etc/rc.d/rc.local
2) re-run /etc/rc.d/rc.local if something changes network-wise.
This is unmaintainable. Please backport to OSP10.
Thanks,
Comment 3 Vincent S. Cojot 2017-04-12 15:36:14 UTC 
This is an example of the flags that'd be needed (RSS and buffer size):
/sbin/ethtool -N ${mynic} rx-flow-hash udp4 sdfn
/sbin/ethtool -G ${mynic} rx ${bufsz} tx ${bufsz}
Comment 7 errata-xmlrpc 2017-09-06 17:09:30 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://access.redhat.com/errata/RHBA-2017:2654