Bug 1437562

Summary:	After a successful deployment, the credentials appear briefly and then disappear from the page
Product:	Red Hat OpenStack	Reporter:	Udi Kalifon <ukalifon>
Component:	openstack-tripleo-ui	Assignee:	Florian Fuchs <flfuchs>
Status:	CLOSED ERRATA	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	high	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	beth.white, dtrainor, flfuchs, jjoyce, jschluet, slinaber, tvignaud
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-ui-7.2.1-0.20170805065336.ac9467f.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-13 21:20:39 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 Udi Kalifon 2017-03-30 14:31:28 UTC

Description of problem:
In the GUI, after a plan deployment ends with success, the credentials (the cloud's endpoint and the username/password) are only shown briefly on the page and then they disappear. This seems to happen consistently after each new deployment. 

You can press F5 to workaround this (and randomly you'd also need to press F5 again, but there is another bug that from a long time ago).


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-3.1.0-4.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Make a successful deployment via the GUI.
2. After deployment, wait a few seconds and see if the credentials disappear.

Comment 1 Ola Pavlenko 2017-05-28 15:10:57 UTC

Still happens 
openstack-tripleo-ui-3.1.0-9.el7ost.noarch

Comment 6 Dan Trainor 2017-11-10 00:33:36 UTC

Did a deployment and saw the Overcloud credentials immediately appear and persist.

Comment 9 errata-xmlrpc 2017-12-13 21:20:39 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.

https://access.redhat.com/errata/RHEA-2017:3462