Bug 2108612

Summary: RHV Dashboard - Top Utilized Resources CPU dialog - percentage values are invalid (larger than 100%)
Product: [oVirt] ovirt-engine Reporter: Sharon Gratch <sgratch>
Component: ovirt-engine-ui-extensionsAssignee: Sharon Gratch <sgratch>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Novotny <pnovotny>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.5.1CC: bugs
Target Milestone: ovirt-4.5.2Keywords: ZStream
Target Release: 4.5.2Flags: sgratch: ovirt-4.5+
sgratch: planning_ack?
sgratch: devel_ack+
gdeolive: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-ui-extensions-1.3.5-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-08 08:17:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: UX RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Top Utilized Resources (CPU) dialog with invalid values none

Description Sharon Gratch 2022-07-19 13:26:13 UTC
Created attachment 1898115 [details]
Top Utilized Resources (CPU) dialog with invalid values

Description of problem:

The footer labels percentage values located next to the Utilization Bar Charts for representing the percentage of the top utilized CPU (host, VMs) is invalid since numbers are > 100%.
  
Version-Release number of selected component (if applicable):
4.5.1-3

How reproducible:
100%

Steps to Reproduce:
1.Go to RHV dashboard -> Global Utilization card -> CPU Donut Chart
2.click on the CPU Donut chart
3.Top Utilized Resources (CPU) popup dialog appears, check the percentage values next to the utilization bar charts.

Actual results:
values should be <= 100%

Expected results:
some values are > 100%


Additional info:
Check screenshot

Comment 2 Sandro Bonazzola 2022-08-30 08:49:07 UTC
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.2 release, it has been closed with a resolution of CURRENT RELEASE.
If the solution does not work for you, please open a new bug report.