Bug 1199072 - packstack does not set ironic password
Summary: packstack does not set ironic password
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 6.0 (Juno)
Assignee: Lukas Bezdicka
QA Contact: Toure Dunnon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-05 12:45 UTC by Lukas Bezdicka
Modified: 2023-02-22 23:02 UTC (History)
6 users (show)

Fixed In Version: openstack-packstack-2014.2-0.17.dev1462.gbb05296.el7ost
Doc Type: Bug Fix
Doc Text:
Packstack set Ironic password to value "PW_PLACEHOLDER" instead of real generated or user provided default password. This was fixed by ensuring packstack has USE_DEFAULT set to false at password option. Now packstack should configure ironic with the predefined password.
Clone Of:
Environment:
Last Closed: 2015-04-07 15:10:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1423035 0 None None None Never
OpenStack gerrit 148839 0 None None None Never
OpenStack gerrit 160855 0 None None None Never
Red Hat Product Errata RHSA-2015:0789 0 normal SHIPPED_LIVE Important: openstack-packstack and openstack-puppet-modules security and bug fix update 2015-04-07 19:08:02 UTC

Description Lukas Bezdicka 2015-03-05 12:45:26 UTC 
When generating answer file by following command.
packstack --gen-answer-file=test.txt

In the answer file Ironic section PW is not replaced by auto generated password.

# The password to use for the Ironic DB access
CONFIG_IRONIC_DB_PW=PW_PLACEHOLDER

# The password to use for Ironic to authenticate with Keystone
CONFIG_IRONIC_KS_PW=PW_PLACEHOLDER
Comment 5 Ami Jeain 2015-03-19 07:07:38 UTC 
FailedQA...back to Dev
Comment 20 Ami Jeain 2015-04-06 08:50:49 UTC 
marking as verified after packstack verification and note from PM
Comment 22 errata-xmlrpc 2015-04-07 15:10:39 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/RHSA-2015-0789.html
Note You need to log in before you can comment on or make changes to this bug.