Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1365949

Summary: obsolete network_device_mtu configuration persists in configuration files
Product: Red Hat OpenStack Reporter: Brent Eagles <beagles>
Component: openstack-tripleo-heat-templatesAssignee: Brent Eagles <beagles>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: high Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: achernet, ihrachys, jguiditt, mburns, nlevinki, nyechiel, rhel-osp-director-maint, srevivo, tvignaud
Target Milestone: gaKeywords: ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-2.0.0-33.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1365678 Environment:
Last Closed: 2016-08-24 13:31:37 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: 1365678    
Bug Blocks: 1365153, 1365892    

Comment 1 Brent Eagles 2016-08-10 14:57:20 UTC 
TripleO heat templates should enable configuration purging.
Comment 2 Thierry Vignaud 2016-08-16 09:15:42 UTC 
The downstream code review sstill needs to be completed, then the patch must be cherry-picked into the rhos/rhos-9.0-patches branch
Comment 4 Ofer Blaut 2016-08-23 14:11:18 UTC 
openstack-tripleo-heat-templates-2.0.0-33.el7ost.noarch


Check Purge is enabled 


/usr/share/openstack-tripleo-heat-templates/puppet/controller.yam
  EnableConfigPurge:
    default: true

grep -ir purge_config /usr/share/openstack-tripleo-heat-templates/puppet/controller.yaml
        purge_config: {get_param: EnableConfigPurge}
                neutron::purge_config: {get_input: purge_config}
                nova::purge_config: {get_input: purge_config}
Comment 6 errata-xmlrpc 2016-08-24 13:31:37 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.

https://rhn.redhat.com/errata/RHBA-2016-1766.html