Bug 1527695
| Summary: | Virtual Machine CPU States chart is not correct when some numbers are 0 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Yuri Rudman <yrudman> | ||||||||||
| Component: | UI - OPS | Assignee: | Robin Knaur <rknaur> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Nandini Chandra <nachandr> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 5.9.0 | CC: | hkataria, lavenel, mpovolny, ndhandre, obarenbo, rknaur, simaishi | ||||||||||
| 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:21 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: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Yuri Rudman
2017-12-19 23:31:32 UTC
Created attachment 1370185 [details]
good1
Created attachment 1370186 [details]
good2
Created attachment 1370187 [details]
broken
Created attachment 1370188 [details]
DB dump
*** Bug 1527694 has been marked as a duplicate of this bug. *** I was able to reproduce it. I am pretty sure that the data are correct. The 'Virtual Machine CPU States' chart is using Stacked Area chart, that should behave exactly like this. It aggregates the individual values. I agree that this is not intuitive, so I can replace Stacked Area charts for Area charts in the definitions that would not aggregate values. Verified in 5.11.0.10 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 |