Bug 1547081

Summary: Capacity & Utilization view is lost after clicking Refresh button
Product: Red Hat CloudForms Management Engine Reporter: Jan Zmeskal <jzmeskal>
Component: UI - OPSAssignee: Zita Nemeckova <znemecko>
Status: CLOSED ERRATA QA Contact: Nandini Chandra <nachandr>
Severity: low Docs Contact:
Priority: low    
Version: 5.9.0CC: dmetzger, hkataria, jzmeskal, lavenel, mpovolny, obarenbo, simaishi, smallamp
Target Milestone: GA   
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.11.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:33:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

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