Bug 1525985

Summary: Too many times, the GUI user must press F5 to see that processes completed
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: openstack-tripleo-uiAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: Udi Kalifon <ukalifon>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: beth.white, jjoyce, jrist, jschluet, jtomasek, slinaber, tvignaud
Target Milestone: Upstream M2Keywords: Triaged
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-ui-9.1.1-0.20180710115855.7dd171e.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:48:37 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-12-14 14:28:41 UTC
Description of problem:
The GUI user is forced to refresh the app too often during the normal course of the use of the app. For example:

- When registering nodes
- When introspecting nodes
- When uploading plans
- When starting a deployment


How reproducible:
This is a random bug but easy to reproduce. It happens to all users during a normal course of using the GUI app.

Comment 6 Jiri Tomasek 2018-05-10 12:46:15 UTC
Moving to 14 release, backporting the patches could potentially cause more harm than good IMHO.

Comment 10 Udi Kalifon 2018-11-05 11:08:23 UTC
The problems that remain are:
1) When the token expires and logging back in, the page is blank (socket is still in CLOSING state)...
2) Right after logging in you see a zaqar disconnection error.

Other than that it seems like the user doesn't need to press F5, at least not as much as in previous versions, so we can close this bug.

Verified: openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch

Comment 14 errata-xmlrpc 2019-01-11 11:48:37 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-2019:0045