Bug 1281908

Summary:	Cannot set overcloud admin password only in deployment plan
Product:	Red Hat OpenStack	Reporter:	Stephen Herr <sherr>
Component:	instack-undercloud	Assignee:	James Slagle <jslagle>
Status:	CLOSED WONTFIX	QA Contact:	yeylon <yeylon>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	mburns, rhel-osp-director-maint, srevivo
Target Milestone:	---
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-13 19:11:10 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 Stephen Herr 2015-11-13 18:58:24 UTC

Description of problem:
If you change the overcloud admin password (Controller-1::AdminPassword) in the deployment plan you have to also change it in /home/stack/tripleo-overcloud-passwords.

Version-Release number of selected component (if applicable):
7

How reproducible:
Always

Steps to Reproduce:
1. Change the Controller-1::AdminPassword to something other than the default randomly-generated one, say 'password'.
2. Deploy the overcloud from the Director

Actual results:
You can log into Horizon with the set password, but you get an error about "compute resources are not available" and the "Hypervisors" tab does not work.

Expected results:
Everything should be aware of the correct admin password

Additional info:
If you also set the password in /home/stack/tripleo-overcloud-passwords then things work correctly.

Comment 2 Mike Burns 2015-11-13 19:11:10 UTC

At this point in OSP 7, we're fixing blocker issues only.  This issues appears to have a clear workaround (set the password in 2 places), so it's not blocker.

Since tuskar will not be shipped in OSP 8, this applies only to OSP 7.  

Given that this isn't a blocker and we're not fixing non-blockers, closing this bug.