Bug 2188226 - UI display resource request from instanceType instead of controllerRevision
Summary: UI display resource request from instanceType instead of controllerRevision
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.13.0
Hardware: All
OS: All
high
high
Target Milestone: ---
: 4.14.0
Assignee: Tal Nisan
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-20 07:31 UTC by Roni Kishner
Modified: 2023-11-08 14:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:05:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
ue_bug (104.74 KB, image/png)
2023-04-20 07:31 UTC, Roni Kishner
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-28248 0 None None None 2023-04-20 08:02:49 UTC
Red Hat Product Errata RHSA-2023:6817 0 None None None 2023-11-08 14:05:42 UTC

Description Roni Kishner 2023-04-20 07:31:52 UTC
Created attachment 1958485 [details]
ue_bug

Description of problem:
The UI display the resources request (CPU/memory/etc...) from the instanceType when used.
After we edit the instanceType the UI still takes the info from that instanceType, so if we edit the instanceType while the VM is running, we will get different values in the VMI and VM display, since the UI don't care about the version/controllerRevision, this is shown in the attached file.

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

How reproducible:
100%

Steps to Reproduce:
1.Create a VM with instanceType and start it
2.Edit CPU/Memory field in the instanceType used
3.

Actual results:
The instanceType CPU/memory is shown

Expected results:
The VMI (currently used version of instanceType) CPU/memory is shown

Additional info:

Comment 1 Guohua Ouyang 2023-04-21 00:14:59 UTC
Move this bug to High severity as it could cause unexpected results.

Comment 2 Guohua Ouyang 2023-08-22 10:32:37 UTC
verified on kubevirt-console-plugin-rhel9:v4.14.0-2581
verified steps:
1. create an instanceType
2. create VM from the IT and get it running
3. edit cpu/mem of the IT
4. the CPU/mem of the VM is not changed

Comment 4 errata-xmlrpc 2023-11-08 14:05:28 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.14.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-2023:6817


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