Bug 2092796

Summary: [RFE] CPU|Memory display in the template card is not consistent with the display in the template drawer
Product: Container Native Virtualization (CNV) Reporter: Leon Kladnitsky <lkladnit>
Component: User ExperienceAssignee: Matan Schatzman <mschatzm>
Status: CLOSED ERRATA QA Contact: Leon Kladnitsky <lkladnit>
Severity: low Docs Contact:
Priority: low    
Version: 4.11.0CC: gouyang, hstastna, mschatzm, yfrimanm, yzamir
Target Milestone: ---   
Target Release: 4.12.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: 2023-01-24 13:36:17 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
catalog
none
CPU Memory display in drawer should be as in the card. Divider line should be in grey color as the template display name in the card (to avoid confusion with the number)
none
CPU Memory display in the drawer
none
CPU & Memory in card view
none
CPU & Memory in drawer view none

Description Leon Kladnitsky 2022-06-02 09:25:47 UTC
Created attachment 1886000 [details]
catalog

Description of problem: CPU|Memory display in the template card of Virtualization Catalog page should have value before the units, like the display in the drawer card 


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yifat Menchik 2022-06-02 11:51:51 UTC
Created attachment 1886072 [details]
CPU Memory display in drawer should be as in the card. Divider line should be in grey color as the template display name in the card (to avoid confusion with the number)

Comment 2 Yifat Menchik 2022-06-02 11:55:05 UTC
Created attachment 1886073 [details]
CPU Memory display in the drawer

Comment 3 Yifat Menchik 2022-06-06 10:13:10 UTC
Please discard the attachment in comments #1 and #2, as a result of my misunderstanding the problem.
This is the updated design for the CPU and memory in the card view and in the drawer view.

Comment 4 Yifat Menchik 2022-06-06 10:14:08 UTC
Created attachment 1887054 [details]
CPU & Memory in card view

Comment 5 Yifat Menchik 2022-06-06 10:14:52 UTC
Created attachment 1887055 [details]
CPU & Memory in drawer view

Comment 6 Hilda Stastna 2022-06-06 18:38:30 UTC
From what I've understood about this bug, there are two issues regarding CPU | Memory field:

1. inconsistency of displaying the CPU and Memory info in the UI,
2. problematic divider "|", that can look like number one for some users.

The expected result/solution that was agreed on (Comment 4 and 5) is problematic, because it solves the issue only with the divider + has two other issues:

1. solves the issue regarding the divider ONLY for the Catalog card, as the solution is present only for it,
   not for any other places in the UI with the CPU | Memory field, including the drawer mentioned in this BZ.
   When started dealing with this bug, I was told not to fix it in any other places in the UI.
2. adds even more inconsistency to the UI, because again - the solution presented in this ticket is only for the Catalog card

According to mentioned above, I recommend to re-evaluate what should be the expected result of this bug. If there is no time for this or if more changes are coming regarding CPU | Memory field, postponing this bug for a next release could be a way, too, to fix both inconsistency and the divider issues and to prevent creating more inconsistency in the UI.

Comment 9 Guohua Ouyang 2022-08-18 23:39:45 UTC
verified on v4.12.0-106

Comment 13 errata-xmlrpc 2023-01-24 13:36:17 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.12.0 Images security 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:0408