Bug 1547081 - Capacity & Utilization view is lost after clicking Refresh button
Summary: Capacity & Utilization view is lost after clicking Refresh button
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: GA
: 5.11.0
Assignee: Zita Nemeckova
QA Contact: Nandini Chandra
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-20 13:26 UTC by Jan Zmeskal
Modified: 2020-04-14 03:44 UTC (History)
8 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:33:51 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:34:11 UTC

Description Jan Zmeskal 2018-02-20 13:26:44 UTC
Description of problem:
When you are at Capacity & Utilization page (let's say for a VM) and click Refresh button, you are returned to the summary page of that VM. See attached video for reference.

Version-Release number of selected component (if applicable):
5.9.0.21

How reproducible:
100 %

Steps to Reproduce:
1. Have C&U activated and some data colleced
2. Go to some VMs summary page and click Monitoring -> Utilization
3. You can either stay at default view or choose any other (like Interval == Most Recent Hour)
4. Click Refresh button

Actual results:
You are returned to the VM's summary page

Expected results:
I would expect to stay at the C&U page (with selected Interval) and get updated values for C&U

Additional info:

Comment 12 Nandini Chandra 2019-05-08 18:09:05 UTC
Verified in 5.11.0.2

Comment 14 errata-xmlrpc 2019-12-12 13:33:51 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/RHBA-2019:4199


Note You need to log in before you can comment on or make changes to this bug.