Bug 1374509

Summary:	[RFE] OpenStack overcloud deploy from different locations
Product:	Red Hat OpenStack	Reporter:	Andreas Karis <akaris>
Component:	openstack-tripleo	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED WONTFIX	QA Contact:	Gurenko Alex <agurenko>
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	8.0 (Liberty)	CC:	djuran, emacchi, jcoufal, mburns, rhel-osp-director-maint, sasha, sclewis, vcojot
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-14 15:56:40 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:
Bug Depends On:
Bug Blocks:	1442136

Description Andreas Karis 2016-09-08 21:16:07 UTC

Description of problem:
Currently, when `openstack overcloud deploy` is run from different locations, it will generate new passwords (tripleo-overcloud-passwords) and a new rc file. Authentication with the old passwords will fail

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

How reproducible:
all the time

Steps to Reproduce:
1. cd /home/stack; openstack overcloud deploy -e /home/stack/templates/...
2. wait for installation to finish
3. cd /home/stack/templates; openstack overcloud deploy -e /home/stack/templates/...

Actual results:
new passwords are genereated, new rc files as well

Expected results:
behavior should be consistent across reinstalls

Additional info:
it would be good to create ~/.instack_overcloud or a similar folder and save this information in there. At the very least, if the same user redeploys the overcloud, this should not happen. Ideally, though, this would even be consistent across users (e.g. root vs stack user).

Comment 3 Jaromir Coufal 2017-06-13 14:13:03 UTC

Due to missed milestone deadline, pushing dev target to early Queens M-1 and therefor productization of the feature to OSP13.

Development in the upstream master will continue through out the time of OSP12 cycle with lower priority than OSP12 feature.

Comment 7 Jaromir Coufal 2019-06-14 15:56:40 UTC

Obsolete RFE without enough of backed demand.