Bug 1365617

Summary: Calculate MTU on every network fetch instead of on create
Product: Red Hat OpenStack Reporter: Nir Yechiel <nyechiel>
Component: openstack-neutronAssignee: Ihar Hrachyshka <ihrachys>
Status: CLOSED ERRATA QA Contact: Toni Freger <tfreger>
Severity: high Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: amuller, chrisw, jjoyce, jschluet, nyechiel, sclewis, srevivo, tvignaud
Target Milestone: gaKeywords: ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: openstack-neutron-8.1.2-3.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-24 12:56:50 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:
Bug Depends On:    
Bug Blocks: 1365153    

Description Nir Yechiel 2016-08-09 17:23:39 UTC
Description of problem:

Today, existing networks may not reflect MTU configured for neutron-server, if they were created when neutron-server was using different MTU setup for its infrastructure, or when it was using bad default values for network MTUs (specifically, before Mitaka, all networks were getting MTU = 0 by default, disabling both advertisement and data path MTU size enforcement). 

Expected results:

This fix stops persisting MTU in the database on network create and instead calculate it on every network resource fetch.

Comment 4 Toni Freger 2016-08-23 11:23:47 UTC
Code tested on the latest puddle openstack-neutron-8.1.2-3.el7ost

Comment 6 errata-xmlrpc 2016-08-24 12:56:50 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.