Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1468620

Summary: Nova cannot configure MTU for DPDK ports; sets to default MTU.
Product: Red Hat OpenStack Reporter: Vincent S. Cojot <vcojot>
Component: openstack-novaAssignee: Sahid Ferdjaoui <sferdjao>
Status: CLOSED ERRATA QA Contact: awaugama
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: awaugama, berrange, dasmith, eglynn, ihrachys, jthomas, kchamart, samccann, sbauza, sferdjao, sgordon, srevivo, vcojot, vromanso
Target Milestone: z4Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-nova-14.0.7-10.el7ost Doc Type: Bug Fix
Doc Text:
Cause: When using DPDK ports, the MTU passed by Neutron to Nova is not take into account. Consequence: The ports are configured to a default value which may not match what is expected (for example,jumbo frames).
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-06 17:04:57 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: 1447081    
Bug Blocks:    

Description Vincent S. Cojot 2017-07-07 14:50:31 UTC
Description of problem:

on OSP10 DPDK, VM instances on DPDK never get the MTU of the ovs bridge they get attached to.
3 backports were identified as being needed. This BZ is to track the openstack-nova backport ([2])

[0] 7a5eb34bd697b7e4cf5e0d5e48e3ec84ff11effa
[1] f3130fe8e23fb07532bb3d740fffaf07481c1e70
[2] 43565ffb9785f6e4848a001cc4be5cec91bfeab1

Comment 6 errata-xmlrpc 2017-09-06 17:04:57 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:2652