Bug 1603208

Summary:	cant delete the deployment when pushing the "Delete Deployment" button
Product:	Red Hat OpenStack	Reporter:	grozov
Component:	openstack-tripleo-ui	Assignee:	Jason E. Rist <jrist>
Status:	CLOSED ERRATA	QA Contact:	grozov
Severity:	urgent	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	augol, jjoyce, jrist, jschluet, jtomasek, slinaber, tvignaud, ukalifon
Target Milestone:	Upstream M3	Keywords:	Triaged
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch.rpm	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-11 11:50:43 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:
Bug Depends On:	1608506
Bug Blocks:

Description grozov 2018-07-19 13:05:49 UTC

Description of problem:
when clicking on the "Delete Deployment" button and clicking on the confirmation 
button, the stack delete doesnt start. in the console it shows DELETE_STACK_SUCCESS in just one second.

Version-Release number of selected component (if applicable):
openstack-tripleo-ui-9.1.1-0.20180702224622.d3d7221.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1.installed OSP 14 with infrared
2.logged in to the GUI 
3.tried to delete the overcloud

Actual results:
nothing happend

Comment 1 Jason E. Rist 2018-07-25 16:43:07 UTC

openstack-tripleo-ui-9.1.1-0.20180702224622.d3d7221.el7ost.noarch

Comment 5 Udi Kalifon 2018-11-14 12:02:03 UTC

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

Comment 7 errata-xmlrpc 2019-01-11 11:50:43 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