Description of problem: During the last upstream development cycles, automatic MTU advertisement and configuration features were added into Neutron to ease OpenStack deployment and to allow the best MTU setting out-of-the-box. We want to ensure this is fully working and tested with OSP director.
Original Neutron spec: https://specs.openstack.org/openstack/neutron-specs/specs/kilo/mtu-selection-and-advertisement.html TripleO: https://review.openstack.org/#/c/280852/ Tempest: https://review.openstack.org/#/c/370804/ Fullstack: https://review.openstack.org/#/c/369470/
Hi Ihar can you please take a look on this test plan and write your comments : https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/wiki/Neutron/MTU
Pushing out to RHOSP 12.
This is mostly automation work (setting up jobs in downstream). I am happy to help with my knowledge, but I believe the major piece here is on QE. I reassign the bug to Eran to reflect that.
We see no point in tracking this as an RFE anymore. There is some test-only work items left so this can be tracked as a regular BZ.
As mentioned above by Assaf Fixed In Version: openstack-neutron-10.0.0-0.20170117115313.ada4237.el7ost
We will test it during OSP13 regression cycle.
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/RHEA-2018:2086