Bug 1607431 - the GUI doesnt show that the stack deletion is in progress
Summary: the GUI doesnt show that the stack deletion is in progress
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: Upstream M3
: 14.0 (Rocky)
Assignee: Jason E. Rist
QA Contact: grozov
URL:
Whiteboard:
Depends On: 1608506
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-23 14:11 UTC by grozov
Modified: 2019-01-11 11:51 UTC (History)
8 users (show)

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:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:50:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:51:03 UTC

Description grozov 2018-07-23 14:11:42 UTC 
Description of problem:
when you press the Delete Deployment button it doesnt show delete in progress but when i go to the cli in enter "openstack stack list" it shows "delete in progress". after the deletion is completed it shows "Deployment succeeded
Ansible passed."

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.press the Delete Deployment button
2.
3.
Comment 1 Jason E. Rist 2018-07-25 16:41:31 UTC 
openstack-tripleo-ui-9.1.1-0.20180702224622.d3d7221.el7ost.noarch
Comment 5 Udi Kalifon 2018-11-14 11:59:58 UTC 
Verified: openstack-tripleo-ui-9.3.1-0.20180921180342.df30b55.el7ost.noarch
Comment 7 errata-xmlrpc 2019-01-11 11:50:46 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.