Bug 2096263

Summary: Incorrectly displaying units for Disks size or Memory field in various places
Product: Container Native Virtualization (CNV) Reporter: Hilda Stastna <hstastna>
Component: User ExperienceAssignee: Hilda Stastna <hstastna>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.11.0CC: cnv-qe-bugs, gouyang
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:57 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
Actual and the expected result example for displaying the memory info none

Description Hilda Stastna 2022-06-13 11:58:45 UTC
Created attachment 1889404 [details]
Actual and the expected result example for displaying the memory info

Description of problem:
There is an incorrect format of displying memory/disk size in various places:
Mi/Gi/Ti is shown instead of MiB/GiB/TiB, or missing space between the value and the unit that would improve readability.

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

How reproducible:
always

Steps to Reproduce:
1. Go to Templates/VirtualMachines/Catalog or try to create/clone a VM
2. Check the Disks/CPU|Memory/Flavor field and the disk size/memory info

Actual results:
Templates disks tab: displaying correct units but without a space between the value and the units (for example 30GiB instead of 30 GiB)
VMs Overview tab: - Details card - CPU | Memory field - incorrect unit + missing space
                  - Disks card - incorrect unit for the Size column
VMs Disk tab: incorrect unit for the Size column
VMs Details tab: CPU | Memory field - incorrect unit + missing space
VMs/Templates Edit CPU | Memory modal: incorrect units in the drop down for the Memory unit
Catalog Template card: CPU | Memory field - incorrect unit + missing space for the memory info
Create VM drawer: CPU | Memory field - incorrect unit + missing space for the memory info
Review and create VirtualMachine Overview tab: - CPU | Memory field - incorrect unit + missing space for the memory info
                                               - modal to Edit CPU | Memory values there - incorrect unit
                                               - Disks field - correct units but without the space
Review and create VirtualMachine Disks tab: correct units but without the space
Clone VirtualMachine modal: Flavor field - incorrect unit + missing space for the memory info 

Expected results:
Display for example '30 GiB' instead of '30GiB' or '30Gi' (same for the other units), in the CPU | Memory field (or the modal to edit them) or Disks tab/card.

Comment 1 Hilda Stastna 2022-06-13 12:05:32 UTC
Another place that needs a fix:

VMs Disks tab: File System section - both 'Total Bytes' and 'Used Bytes' columns - incorrect unit

Comment 2 Hilda Stastna 2022-06-15 18:21:27 UTC
Another place that needs a fix:

Templates Catalog list view - CPU | Memory column - incorrect unit + missing space - for the memory info

Comment 3 Hilda Stastna 2022-06-15 18:27:08 UTC
Create VM drawer: Disks field - Size column - missing space for the memory info

Comment 4 Hilda Stastna 2022-06-15 18:42:58 UTC
Clone VirtualMachine modal: Disks field - incorrect units, without 'B' suffix

Comment 5 Guohua Ouyang 2022-06-17 06:47:35 UTC
verified on v4.11.0-58

Comment 8 errata-xmlrpc 2022-09-14 19:35:57 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