Bug 1030298 - Invalid parameter quantum_metadata_proxy_shared_secret while installing with packstack
Summary: Invalid parameter quantum_metadata_proxy_shared_secret while installing with ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: z3
: 3.0
Assignee: Martin Magr
QA Contact: Nir Magnezi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-14 10:06 UTC by Attila Darazs
Modified: 2014-01-09 19:40 UTC (History)
9 users (show)

Fixed In Version: openstack-packstack-2013.1.1-0.37.dev705.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-18 15:20:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 56366 0 None None None Never
Red Hat Product Errata RHBA-2013:1510 0 normal SHIPPED_LIVE Red Hat OpenStack 3.0 bug fix and enhancement advisory 2013-11-18 20:11:18 UTC

Description Attila Darazs 2013-11-14 10:06:47 UTC 
Description of problem:
The installation fails on a packstack error:

ERROR : Error during puppet run : Error: Invalid parameter
quantum_metadata_proxy_shared_secret at
/var/tmp/packstack/9e09ecdc2750465592f062da88fb5843/manifests/192.168.0.133_api_nova.pp:9
on node jenkins-rhos-3.openstacklocal

Version-Release number of selected component (if applicable):
openstack-packstack-2013.1.1-0.35.dev699.el6ost.noarch (in OpenStack-Grizzly Puddle: 2013-11-13.1)

How reproducible:
Always

Steps to Reproduce:
I think it's enough if you install with the quantum install disabled (CONFIG_QUANTUM_INSTALL=n), but we have a test reproducer if it's necessary.
Comment 2 Rami Vaknin 2013-11-14 10:18:02 UTC 
I've tested it, it reproduces also with CONFIG_QUANTUM_INSTALL=y
Comment 7 Rami Vaknin 2013-11-16 20:32:35 UTC 
Verified on rhos Grizzly puddle 2013-11-14.2.
Comment 8 errata-xmlrpc 2013-11-18 15:20:07 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.

http://rhn.redhat.com/errata/RHBA-2013-1510.html
Note You need to log in before you can comment on or make changes to this bug.