Bug 2094440 - Utilization pie charts figures are not based on current data
Summary: Utilization pie charts figures are not based on current data
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.11.0
Assignee: Matan Schatzman
QA Contact: Leon Kladnitsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-07 15:29 UTC by Leon Kladnitsky
Modified: 2023-11-13 08:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-14 19:35:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
charts (984.02 KB, video/mp4)
2022-06-07 15:29 UTC, Leon Kladnitsky
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 567 0 None Merged Bug 2094440: Memory Utilization chart VM overview memory change 2022-06-11 08:59:26 UTC
Red Hat Issue Tracker CNV-18952 0 None None None 2023-11-13 08:18:59 UTC
Red Hat Product Errata RHSA-2022:6526 0 None None None 2022-09-14 19:35:52 UTC

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


Note You need to log in before you can comment on or make changes to this bug.