Description of problem: Create a VM with 64M Memory, go to overview page and edit it, the memory is loading as 64G memory. If user does not notice it and save the VM, the VM memory size is becoming large unexpectedly. Besides it, user can only input integer, float is not allowed there. Version-Release number of selected component (if applicable): kubevirt-web-ui:v1.4.0-14.1 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
since it is "low", "low" and would be hard to hit in practice and the impact is an annoyance but does not break anything, targeting to 2.1
The flavor editing feature is missing in 2.1 so targeting 2.2
kubevirt-web-ui is no longer used as the primary plugin for the console. Thus, the problem described in https://bugzilla.redhat.com/show_bug.cgi?id=1690701#c0 doesn't happen anymore. But another issue does occur: If a user create a VM from YAML, not from the wizard, the VM's flavor cannot be changed via the overview page
So after offline discussion with Ido, the issue is this: If you create the VM using a yaml which does not contain the template/flavor/os annotations, you can not edit the VM's memory/CPU in vm details. It does work for VMs which are created using the wizard. It is a rather normal thing that if the VM is not created using the wizard, the UI is able to work with it but not all the features will work. It would be nice to be able to cpu/memory independently of the flavor, but it is that critical. Moving to 4.4
verified on 4.5.0-0.nightly-2020-03-29-224016.
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, 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/RHBA-2020:2409