Bug 1130574

Summary: Password for horizon in the "Deployed" screen is shown wrong
Product: Red Hat OpenStack Reporter: Brad P. Crochet <brad>
Component: rubygem-staypuftAssignee: Scott Seago <sseago>
Status: CLOSED ERRATA QA Contact: Ami Jeain <ajeain>
Severity: medium Docs Contact:
Priority: medium    
Version: Foreman (RHEL 6)CC: aberezin, ajeain, mburns, mlopes, rhos-maint, yeylon
Target Milestone: z1   
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ruby193-rubygem-staypuft-0.3.2-1.el6ost Doc Type: Bug Fix
Doc Text:
Previously, Red Hat Enterprise Linux OpenStack Platform installer would display a randomly generated password, even though the user-provided password was used during configuration. The consequence was that the user would be informed of an incorrect password on the deployment summary screen. This update addresses this issue, and the correct password is now presented to the user.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-01 13:26:41 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:

Description Brad P. Crochet 2014-08-15 14:57:38 UTC
Description of problem:
If a password was set as the 'Password for all services' (and not left as random string), the deployed screen, where the horizon url, username, and password is displayed, shows a random password, instead of the one set in the deployment wizard.

Version-Release number of selected component (if applicable):
ruby193-rubygem-staypuft-0.2.5-1.el6ost.noarch

Comment 3 Mike Burns 2014-08-15 15:40:02 UTC
Just a clarification:

If a password is set by the user on the first wizard screen, that is used for the admin user.  We display an incorrect password, but the user provided one is correct.

Comment 4 Brad P. Crochet 2014-08-15 15:55:03 UTC
PR Submitted

https://github.com/theforeman/staypuft/pull/269

Comment 8 Ami Jeain 2014-09-16 12:47:15 UTC
verified in latest puddle

Comment 10 errata-xmlrpc 2014-10-01 13:26:41 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-2014-1350.html