Bug 1647038 - Deployment progress bar doesn't appear, user must press F5
Summary: Deployment progress bar doesn't appear, user must press F5
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: 14.0 (Rocky)
Assignee: RHOS Maint
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-06 15:08 UTC by Udi Kalifon
Modified: 2019-01-11 11:54 UTC (History)
7 users (show)

Fixed In Version: puppet-tripleo-9.3.1-0.20181010034750.157eaab.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:54:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1803422 0 None None None 2018-11-14 20:02:23 UTC
OpenStack gerrit 618019 0 None None None 2018-11-19 10:49:11 UTC
OpenStack gerrit 618732 0 None None None 2018-11-19 11:00:03 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:54:53 UTC

Description Udi Kalifon 2018-11-06 15:08:24 UTC 
Description of problem:
When starting a deployment, the deployment page doesn't update past the "initializing deployment". Te progress bar doesn't appear and the user doesn't see that the deployment started, and doesn't see if it failed.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch


How reproducible:
50%


Steps to Reproduce:
1. Start a deployment from the UI.


Actual results:
The progress bar never starts rolling.


Additional info:
The bug is not always reproducible. No error are visible in the console.
Comment 6 Udi Kalifon 2018-11-23 11:10:02 UTC 
Verified: openstack-tripleo-ui-9.3.1-0.20180921180343.df30b55.el7ost.noarch
Comment 8 errata-xmlrpc 2019-01-11 11:54:40 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
Note You need to log in before you can comment on or make changes to this bug.