Description of problem: Affects Upgrades! MTU configuration was changed in mitaka. While the TripleO templates and puppet modules removed support, puppet controlled neutron configuration files are not being "purged" after an upgrade, leaving values that are no longer managed by puppet behind - including old network_device_mtu settings. While it is not the preferred mechanism for controlling MTU settings, neutron still contains code that will read and use this value. How reproducible: Currently 100% on existing nodes after an upgrade.
Adding tracker for upstream patch pending CI/merging that can be employed to purge the neutron configs.
Do we have a similar patch for Nova? I think network_device_mtu should be removed from nova.conf too, otherwise Nova will still attempt to use it for its side of data path (tap and qbr).
I suspect the needed Nova backport is: https://review.openstack.org/#/c/353292/
Upstream is merged for both patches
Pulling back to on_dev due to new patch needed. Brent, do we think this is the last one before I rebuild (once it merges)?
Adding mitaka patch (not yet merged) ref for puppet-openstacklib
openstack-puppet-modules-8.1.8-2.el7ost.noarch test upgrade and tempest network scenario tests Code it there as well
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://rhn.redhat.com/errata/RHBA-2016-1764.html