Description of problem: packstack fails with: Error: Duplicate declaration: Nova_config[DEFAULT/auto_assign_floating_ip] is already declared in file /var/tmp/packstack/b4646346f5d94fbc8b73428a1c5b41f5/manifests/172.16.32.11_nova.pp:257 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. packstack install using attached config file 2. 3. Actual results: 00:13:26.122 172.16.32.11_nova.pp: [ ERROR ] 00:13:26.123 Applying Puppet manifests [ ERROR ] 00:13:26.124 00:13:26.125 ERROR : Error appeared during Puppet run: 172.16.32.11_nova.pp 00:13:26.125 Error: Duplicate declaration: Nova_config[DEFAULT/auto_assign_floating_ip] is already declared in file /var/tmp/packstack/b4646346f5d94fbc8b73428a1c5b41f5/manifests/172.16.32.11_nova.pp:257; cannot redeclare at /var/tmp/packstack/b4646346f5d94fbc8b73428a1c5b41f5/modules/nova/manifests/network.pp:123 on node uk1pr-rhos-ci-20-rh-pud-pksk-controller.novalocal 00:13:26.128 You will find full trace in log /var/tmp/packstack/20160113-010457-xmpT35/manifests/172.16.32.11_nova.pp.log 00:13:26.129 Expected results: Install completes Additional info: <mmagr> I my guess is that in the past when installing nova-network the puppet modules did not set auto_assign_floating_ip config, so we did workaround for this: https://github.com/openstack/packstack/blob/stable/liberty/packstack/puppet/templates/nova_network.pp#L4 <mmagr> unfortunately current implementation in modules is doing so: https://github.com/redhat-openstack/openstack-puppet-modules/blob/stable/liberty/nova/manifests/network.pp#L122 <mmagr> jschlueter, so we have duplicate declaration
Created attachment 1115170 [details] packstack answer file
verified on openstack-packstack-2015.1-0.16.dev1589.g1d6372f.el7ost.noarch
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-0636.html