Bug 1374509 - [RFE] OpenStack overcloud deploy from different locations
Summary: [RFE] OpenStack overcloud deploy from different locations
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: Alex Schultz
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks: 1442136
TreeView+ depends on / blocked
 
Reported: 2016-09-08 21:16 UTC by Andreas Karis
Modified: 2019-12-16 06:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-14 15:56:40 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1673485 0 None None None 2017-03-16 15:12:19 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.