Neutron agents do not use network MTU

Bug #1557339 reported by Eugene Nikanorov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
High
Alexey Stupnikov
7.0.x
Won't Fix
High
Alexey Stupnikov
8.0.x
Won't Fix
High
Alexey Stupnikov
9.x
Invalid
High
Unassigned

Bug Description

Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Backport for version 7.0:
https://review.fuel-infra.org/18069

Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

IMO, this patch adds a feature to product, but besides that there are large concerns about its applicability to stable versions of MOS. There are a bunch of MTU-related fixes in community's master branch. I have spoken with Eugene Nikanorov and we agreed that we shouldn't port only one patch and all MTU-related patches are non-backportable. Hence, I will close this issue as Won't Fix (wontfix-risky).I ask those who will consider to re-open this bug, please check the links below first:
[1] https://specs.openstack.org/openstack/fuel-specs/specs/7.0/jumbo-frames-between-instances.html
[2] https://review.openstack.org/#/q/owner:%22Kevin+Benton%22+status:merged
[3] https://review.openstack.org/#/c/284814/ -- Add global_physnet_mtu and deprecate segment_mtu
[4] https://review.openstack.org/#/c/283798/ -- Deprecate network_device_mtu
[5] https://review.openstack.org/#/c/283847/ -- Use MTU value from Neutron in OVS/LB VIF wiring
[6] https://review.openstack.org/#/c/286449/ -- Set veth_mtu default to 9000

tags: added: wontfix-risky
Changed in mos:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.