Bug 1630987

Summary: openstack-puppet-modules-8.1.13-7.el7ost introduces duplicate puppet declaration conflicting with instack-undercloud
Product: Red Hat OpenStack Reporter: Steve Linabery <slinaber>
Component: instack-undercloudAssignee: Martin Schuppert <mschuppe>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: unspecified Docs Contact:
Priority: high    
Version: 9.0 (Mitaka)CC: jamsmith, mburns, mschuppe
Target Milestone: zstreamKeywords: Triaged, ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: instack-undercloud-4.0.0-20.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-02 18:44: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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1501567, 1629928    

Description Steve Linabery 2018-09-19 16:10:50 UTC
When deploying with openstack-puppet-modules-8.1.13-7.el7ost there is a duplicate declaration of Nova_config[DEFAULT/my_ip] that conflicts with instack-undercloud-4.0.0-19.el7ost

Comment 3 Martin Schuppert 2018-09-20 08:30:46 UTC
same as from BZ1630968 comment 2:

~~~
1629912 introduced my_ip to nova/manifests/init.pp which is required to fix  1552855 as a result we now have the dupe in openstack-puppet-modules:

 nova_config {
   'DEFAULT/my_ip':                     value => $ipaddress;
   'DEFAULT/linuxnet_interface_driver': value => 'nova.network.linux_net.LinuxOVSInterfaceDriver';
   'DEFAULT/rpc_response_timeout':      value => '600';
   'DEFAULT/sync_power_state_interval': value => hiera('nova_sync_power_state_interval');

I'll submit a patch to instack-undercloud to use the new my_ip from openstack-puppet-modules for OSP8/9 instead of the current nova_config.
~~~

Comment 13 errata-xmlrpc 2018-10-02 18:44: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.

https://access.redhat.com/errata/RHBA-2018:2848