Incorrect MTU on ovs bridges with network template

Bug #1668541 reported by Aleksei Chekunov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Invalid
High
Alexey Stupnikov
9.x
Invalid
High
Alexey Stupnikov

Bug Description

MOS 9.2, network templates, VLAN segmentation
MTU 9000 was applied on bridges on compute and controller nodes, but ovs bridges were configured with MTU 1500.

in neutron.conf -
#global_physnet_mtu=1500
in ml2_conf.ini
#physical_network_mtus =physnet1:9000,physnet2:9000

Revision history for this message
Aleksei Chekunov (achekunov) wrote :
description: updated
Roman Rufanov (rrufanov)
tags: added: customer-found support
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

Closing this bug is Invalid, since there is a recommended way to set MTU on network interfaces [1]. Network templates can be used to configure OS networking, but they shouldn't be used to configure whole stack of software to use correct MTU. I have tested the paper [1] with and without network templates, I also successfully used Fuel UI to set MTU and had no problems.

[1] https://docs.mirantis.com/openstack/fuel/fuel-9.2/reference-architecture/ovs/0200-cli-adjust-network-config.html

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.