Description of problem: One of my customer has his browser in French. When he logs in to oVirt, the "French" language is auto selected. When creating a VM, the size format is set to Mo ("mega octets") which is the correct localized way to represent digital base2 numbers. However the validation goes haywire and pressing "ok" does nothing at all. There is no error message displayed in the interface, it just does nothing. Version-Release number of selected component (if applicable): How reproducible: 1. Log-in in French 2. Try to create a VM normally 3. Check "show advanced" or whatever it is in french 4. Try to set an amount of memory 5. Fail to create the VM Actual results: Nothings happen, when dialog is not dismissed and there is no error message Expected results: Create a VM
please attach the ui.log if you have it
The customer gave up on oVirt due to this bug. I have no longer access to the information. AFAIK, it is trivial to reproduce.
Note: This patch is dependent upon completion of the French translation, specifically setting the sizeMB value to Mo for the change to work.
This bug is in modified state and targeting 4.4.1. Can we re-target to 4.4.0 and move to QA?
(In reply to Sandro Bonazzola from comment #4) > This bug is in modified state and targeting 4.4.1. Can we re-target to 4.4.0 > and move to QA? Did we add the proper French Translation as per Comment 3?
Steps: 1. Use French translations and login to AdminPortal 2. Go to 'Create VM' dialogue and set memory to non-default value 3. Create the VM Result: After writing some value to the memory field, this and all other memory fields (maximum, guaranteed) change to '0 Mo'. After changing them all manually as automatic fill up with tab does not work, VM still cannot be created as the memory field is stuck in error state even with correct value inside. Tested in: ovirt-engine-4.4.0-0.29.master.el8ev.noarch
Steps: 1. Use French translations and login to AdminPortal 2. Go to 'Create VM' dialogue and set memory to non-default value 3. Create the VM Results: After rewriting the default memory value, other memory values are correctly updated and VM can be created successfully. Verified in: ovirt-engine-4.4.0-0.33.master.el8ev.noarch ovirt-engine-webadmin-portal-4.4.0-0.33.master.el8ev.noarch
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.