Bug 1361130

Summary: Main dashboard cpu charts
Product: [Red Hat Storage] Red Hat Storage Console Reporter: Lubos Trilety <ltrilety>
Component: UIAssignee: sankarshan <sankarshan>
Status: CLOSED DUPLICATE QA Contact: sds-qe-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2CC: nthomas, sankarshan
Target Milestone: ---   
Target Release: 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-28 12:16:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
main dashboard
none
cluster dashboard none

Description Lubos Trilety 2016-07-28 11:43:24 UTC
Created attachment 1185048 [details]
main dashboard

Description of problem:
Main dashboard shows bad charts for CPU.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.36-1.el7scon.x86_64
rhscon-ui-0.0.50-1.el7scon.noarch
rhscon-ceph-0.0.36-1.el7scon.x86_64
rhscon-core-selinux-0.0.36-1.el7scon.noarch

How reproducible:
90%

Steps to Reproduce:
1. Create one cluster so there should be the same values on main and cluster dashboards
2. Run some stress command to load CPU on some of the cluster host
3. After a while open main dashboard

Actual results:
There's no peak in the chart and values in the chart differed from those which are displayed on cluster dashboard
Moreover in my case there's no don't donut chart for CPU on main dashboard whilst on cluster dashboard there is.

Expected results:
The chart should display correct values, if there is just one cluster they should be the same as for the cluster

Additional info:

Comment 1 Lubos Trilety 2016-07-28 11:45:30 UTC
Created attachment 1185049 [details]
cluster dashboard

Comment 2 Nishanth Thomas 2016-07-28 12:16:47 UTC

*** This bug has been marked as a duplicate of bug 1360889 ***