Bug 1510483 - Infinite Heat stacks request by GUI
Summary: Infinite Heat stacks request by GUI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 12.0 (Pike)
Assignee: Jason E. Rist
QA Contact: Ola Pavlenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-07 14:20 UTC by Jason E. Rist
Modified: 2018-02-05 19:15 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-ui-7.4.3-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 22:19:18 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1729382 0 None None None 2017-11-07 14:20:26 UTC
OpenStack gerrit 517024 0 None None None 2017-11-07 14:22:16 UTC
OpenStack gerrit 518346 0 None None None 2017-11-07 15:00:37 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Jason E. Rist 2017-11-07 14:20:23 UTC 
Cloned from launchpad bug 1729382.

Description:

At certain cases GUI starts to infinitely fetch Heat stacks. This eventually causes Heat to crash.

This is caused by fetchStacks() being called in componentWillReceiveProps in CurrentPlan component.

fetchStacks should be called only when current plan name changes

Specification URL (additional information):

https://bugs.launchpad.net/tripleo/+bug/1729382
Comment 1 Jason E. Rist 2017-11-07 14:22:17 UTC 
Bug fixed upstream, awaiting merge
https://review.openstack.org/517024
Comment 2 Jason E. Rist 2017-11-07 15:00:37 UTC 
Merged upstream, backport here: https://review.openstack.org/518346
Comment 5 Udi Kalifon 2017-11-20 14:59:29 UTC 
Verified: openstack-tripleo-ui-7.4.3-2.el7ost.noarch
Comment 8 errata-xmlrpc 2017-12-13 22:19:18 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-2017:3462
Note You need to log in before you can comment on or make changes to this bug.