Bug 1446705 - OSP11 Duplicate declaration in puppet manifests causes packstack all-in-one to fail install
Summary: OSP11 Duplicate declaration in puppet manifests causes packstack all-in-one t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 11.0 (Ocata)
Assignee: Alfredo Moralejo
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1447811
TreeView+ depends on / blocked
 
Reported: 2017-04-28 16:20 UTC by Steve Linabery
Modified: 2017-05-17 20:24 UTC (History)
3 users (show)

Fixed In Version: openstack-packstack-10.0.0-4.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1447811 (view as bug list)
Environment:
Last Closed: 2017-05-17 20:24:02 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1245 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 Bug Fix and Enhancement Advisory 2017-05-17 23:01:50 UTC
OpenStack gerrit 457939 None None None 2017-04-28 16:43:07 UTC

Description Steve Linabery 2017-04-28 16:20:45 UTC
Using the latest OSP11 puddle, attempt to install packstack all-in-one, neutron, rabbitmq, fails with the following error:

15:08:13 ERROR : Error appeared during Puppet run: 192.168.1.13_compute.pp
15:08:13 Error: Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: Nova_config[libvirt/live_migration_uri] is already declared in file /var/tmp/packstack/52feb3a090054dfb83e9a532c95989ad/modules/packstack/manifests/nova/compute.pp:29; cannot redeclare at /var/tmp/packstack/52feb3a090054dfb83e9a532c95989ad/modules/nova/manifests/migration/libvirt.pp:150 at /var/tmp/packstack/52feb3a090054dfb83e9a532c95989ad/modules/nova/manifests/migration/libvirt.pp:150:5 on node f4f0f508687b8bf4d1f3d6cb2fb1d6b9aio-1.openstacklocal

Comment 3 errata-xmlrpc 2017-05-17 20:24:02 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/RHEA-2017:1245


Note You need to log in before you can comment on or make changes to this bug.