Created attachment 1861398 [details] large disk size Description of problem: While create vm from templates which has boot source, a large number showing disk size field, user may did not notice it and continue save the disk. Which cause the VM disk is too large. This is a supplyment of bug https://bugzilla.redhat.com/show_bug.cgi?id=2046598, so we won't miss it. Version-Release number of selected component (if applicable): 4.10.0-rc.2 How reproducible: 100% Steps to Reproduce: 1. create vm from a template which has boot source 2. edit disk on storage step(customize wizard) 3. Actual results: Expected results: Additional info:
(In reply to Hilda Stastna from comment #1) > Hi Guohua, > > to be more specific, the problem is incorrect units or the disk size > displayed in bytes instead of Gib, in the "Edit disk" modal window. But I > would like to make sure about the expected result. Should the disk size be > displayed in GiB in that window? Also let's make sure about the behavior > when changing units - The value doesn't change when changing GiB to MiB/TiB. > Is this expected behavior? Thanks! the problem is it loads with a large number and unit GiB. the expected results is it loads a small number and unit GiB, a large number is not readable.
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, it still shows a large number on storage and edit disk modal.
Created attachment 1867326 [details] large number on storage step while using templates which has auto-updated boot source
Test it on latest master and 4.11, the problem #1, #2, #3 are not reproduced any more. move the bug back to ON_QA.
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. https://access.redhat.com/errata/RHSA-2022:5069