Bug 1437562 - After a successful deployment, the credentials appear briefly and then disappear from the page
Summary: After a successful deployment, the credentials appear briefly and then disapp...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 12.0 (Pike)
Assignee: Florian Fuchs
QA Contact: Ola Pavlenko
Depends On:
TreeView+ depends on / blocked
Reported: 2017-03-30 14:31 UTC by Udi Kalifon
Modified: 2018-02-05 19:07 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-ui-7.2.1-0.20170805065336.ac9467f.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-12-13 21:20:39 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
OpenStack gerrit 408138 0 None None None 2017-08-18 15:05:07 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

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):

How reproducible:

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 

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.


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