Created attachment 1855682 [details]
disk size unit is byte
Description of problem:
Auto-update boot source size is calculated in byte on customize wizard, which is hard to read, it should use 'GiB' instead of Byte.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create vm from template which boot source is auto-updated, like template rhel9
It use "B" for disk size
It use "GiB" for disk size
It does not happen to user uploaded golden images.
*** Bug 2049412 has been marked as a duplicate of this bug. ***
set this to high, this is a very annoying issue and could cause unexpected behavior. An example is:
on the customize wizard, if a user edits the disk and saves it, it could create a very large disk (1000 PiB) without attention.
We need to fix this issue and backport to 4.10.z.
(In reply to Guohua Ouyang from comment #3)
> set this to high, this is a very annoying issue and could cause unexpected
> behavior. An example is:
> on the customize wizard, if a user edits the disk and saves it, it could
> create a very large disk (1000 PiB) without attention.
create a new bug https://bugzilla.redhat.com/show_bug.cgi?id=2054950 for the disk modal because the current fix of this bug won't take care of it.
Created attachment 1862928 [details]
disk unit on customize wizard
Tested on master, the disk unit is still 'B' if the template has no boot source.
Another problem the disk unit even uses 'B' after modifying it with other values.
Tests should cover three scenarios:
1. create VM from template has no boot source
2. create VM from template has manual updated boot source
3. create VM from template which has auto-updated boot source
Test on master which has the PR included, the first 2 scenarios are PASS, but failed on the scenario 3.
This bug is similar with https://bugzilla.redhat.com/show_bug.cgi?id=2054950
And not reproduced on latest master
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 Container Platform 4.11.0 bug fix and 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.