Bug 2094440

Summary: Utilization pie charts figures are not based on current data
Product: Container Native Virtualization (CNV) Reporter: Leon Kladnitsky <lkladnit>
Component: User ExperienceAssignee: Matan Schatzman <mschatzm>
Status: CLOSED ERRATA QA Contact: Leon Kladnitsky <lkladnit>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.11.0CC: cnv-qe-bugs, gouyang, mschatzm
Target Milestone: ---   
Target Release: 4.11.0   
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: 2022-09-14 19:35:43 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
charts none

Description Leon Kladnitsky 2022-06-07 15:29:10 UTC
Created attachment 1887618 [details]
charts

Description of problem: When CPU|Memory profile of running VM is changed, the pie charts start to use new max values immediately, although these values are not applied until the VM is restarted.


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


How reproducible:


Steps to Reproduce:
1. Open  Overview page of running VM.
2. Edit CPU | Memory, increase CPU and Memory (multiply x 4)
3. Click Save button

Actual results: Pie charts on Utilization card are updated immediately, according to new maximum values


Expected results: Should not update until VM is restarted and new max values are in effect.


Additional info:

Comment 1 Leon Kladnitsky 2022-06-11 10:14:26 UTC
Verified on 4.11.0-456

Comment 4 errata-xmlrpc 2022-09-14 19:35:43 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 (Important: OpenShift Virtualization 4.11.0 Images security and bug fix update), 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/RHSA-2022:6526