Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1637947

Summary:	Deployment never finishing in the GUI
Product:	Red Hat OpenStack	Reporter:	Andrey Fiodorov <afiodoro>
Component:	openstack-tripleo-ui	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Andrey Fiodorov <afiodoro>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	14.0 (Rocky)	CC:	afiodoro, beth.white, jjoyce, jschluet, slinaber, tvignaud, ukalifon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-13 13:28:50 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 Andrey Fiodorov 2018-10-10 11:31:22 UTC

Description of problem:
The status of deployment "in process" and does not changing even after 4 hours. 
Although status of stack in CLI is CREATE_FINISHED.
 
Version-Release number of selected component (if applicable):
openstack-tripleo-ui-9.3.1-0.20180921180340.df30b55.el7ost.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1. Install OSP14 (undercloud)
2. Go to Plans in the GUI and click on button "validate and deploy"

Actual results:
The Deployment never finishing

Expected results:
It should finish with status failed/successes

Additional info:

Comment 4 Udi Kalifon 2018-10-31 16:41:35 UTC

I got this:

tripleo_ui.js:1 WebSocket is already in CLOSING or CLOSED state.
(anonymous) @ tripleo_ui.js:1

The progress bar never showed up, the "stop" button never appeared... Until I pressed F5 and saw the failure message.

Comment 5 Andrey Fiodorov 2018-11-07 21:57:35 UTC

It was corrected in another BUG which was affects status of deploy in the GUI:
https://bugzilla.redhat.com/show_bug.cgi?id=1637966

Comment 6 Beth White 2018-11-13 13:28:50 UTC


*** This bug has been marked as a duplicate of bug 1637966 ***