Can't access the deployed overcloud, the overcloudrc file is not generated
Bug #1583656 reported by
Udi Kalifon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiri Tomasek |
Bug Description
There is no way to know the AUTH_URL or admin password of the overcloud. The GUI doesn't show the needed details after a successful deployment, and no overcloudrc file is generated.
We have to generate an rc file as well as provide this information in the GUI.
Changed in tripleo-ui: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in tripleo-ui: | |
assignee: | nobody → Honza Pokorny (hpokorny) |
Changed in tripleo-ui: | |
milestone: | none → rc1 |
affects: | tripleo-ui → tripleo |
Changed in tripleo: | |
milestone: | rc1 → none |
tags: | added: ui |
Changed in tripleo: | |
status: | Triaged → In Progress |
Changed in tripleo: | |
assignee: | Honza Pokorny (hpokorny) → Jiri Tomasek (jtomasek) |
To post a comment you must log in.
I have gone through the old API code, and the new mistral-based deployment workflow, and to the best of my knowledge this has never been implemented. The "openstack overcloud deploy" command in python- tripleoclient contains the code to generate the overcloudrc file, but not the other places.
The mistral deployment workflow simply calls heatclient. stacks. create( ) and then waits for it to finish. It is my understanding that we need another step in that workflow that will create this file once the overcloud is deployed.