Bug 1365678
Summary: | obsolete network_device_mtu configuration persists in configuration files | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Brent Eagles <beagles> | |
Component: | openstack-puppet-modules | Assignee: | Brent Eagles <beagles> | |
Status: | CLOSED ERRATA | QA Contact: | Ofer Blaut <oblaut> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 9.0 (Mitaka) | CC: | ihrachys, jguiditt, mburns, nyechiel, srevivo | |
Target Milestone: | ga | Keywords: | ZStream | |
Target Release: | 9.0 (Mitaka) | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | openstack-puppet-modules-8.1.8-2.el7ost | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1365892 1365949 (view as bug list) | Environment: | ||
Last Closed: | 2016-08-24 13:10:30 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: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1365153, 1365892, 1365949 |
Description
Brent Eagles
2016-08-09 20:17:28 UTC
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 |