Bug 1043713

Summary: [RFE][horizon]: Heat Fix Status Column
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: python-django-horizonAssignee: RHOS Maint <rhos-maint>
Status: CLOSED ERRATA QA Contact: Amit Ugol <augol>
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: aberezin, aortega, augol, dnavale, jpichon, markmc, mrunge, yeylon
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/horizon/+spec/heat-fix-status-column
Whiteboard: upstream_milestone_icehouse-rc1 upstream_status_implemented upstream_definition_new
Fixed In Version: python-django-horizon-2014.1-5.el7ost Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-08 15:41:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RHOS Integration 2013-12-17 00:48:30 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/heat-fix-status-column.

Description:

The Status column in stacks or resources list sometimes shows the
progress bar for a status which is not in progress. The status code for
these columns needs to be fixed and refactored so that the heat topology
diagram uses the same code

Specification URL (additional information):

None

Comment 4 Amit Ugol 2014-06-08 04:35:14 UTC
I have been testing this for a while. The column seems to be much more responsive.
I have yet to encounter a normal case where stack manipulation is not visualy responsive.

Comment 6 errata-xmlrpc 2014-07-08 15:41:01 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.

http://rhn.redhat.com/errata/RHEA-2014-0855.html