Bug 1422546 - [UI] [Max memory] Max memory validation doesn't prevent dialog from being confirmed
Summary: [UI] [Max memory] Max memory validation doesn't prevent dialog from being con...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.1.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks: 1388245
TreeView+ depends on / blocked
 
Reported: 2017-02-15 14:12 UTC by Israel Pinto
Modified: 2022-04-11 09:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-14 12:14:45 UTC
oVirt Team: Virt
Embargoed:
sbonazzo: ovirt-4.2-


Attachments (Terms of Use)
edit vm (207.65 KB, image/png)
2017-02-15 14:14 UTC, Israel Pinto
no flags Details
engine.log (201.79 KB, application/zip)
2017-02-15 14:15 UTC, Israel Pinto
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45584 0 None None None 2022-04-11 09:25:44 UTC

Description Israel Pinto 2017-02-15 14:12:57 UTC
Description of problem:
While updating running VM the max memory value is reset to zero and update failed and operation cancel since:
Error while executing action: 
* must be greater than or equal to 1
* Attribute: vmStatic.maxMemorySizeMb

Version-Release number of selected component (if applicable):
Red Hat Virtualization Manager Version: 4.1.1-0.1.el7


How reproducible:
All the time

Steps to Reproduce:
1. Create VM and run it (with 1024 MB)
2. Update max memory running VM tot 10240 MB

Actual results:
Max memory value is reset to zero.

Comment 1 Israel Pinto 2017-02-15 14:14:35 UTC
Created attachment 1250620 [details]
edit vm

Comment 2 Israel Pinto 2017-02-15 14:15:11 UTC
Created attachment 1250621 [details]
engine.log

Comment 3 jniederm 2017-02-16 15:18:12 UTC
Hi Israel, I can't reproduce this bug. I tried following steps:
1. Create a VM, add NIC, set it to boot from network, don't touch any memory settings, defaults are 1024 mem, 4096 maxmem 
2. run vm
3. update maxmem to 10240 and confirm that it will be applied after restart
Steps above didn't lead to any exception. Are the steps correct?

Comment 4 Israel Pinto 2017-02-16 17:04:52 UTC
(In reply to jniederm from comment #3)
> Hi Israel, I can't reproduce this bug. I tried following steps:
> 1. Create a VM, add NIC, set it to boot from network, don't touch any memory
> settings, defaults are 1024 mem, 4096 maxmem 
> 2. run vm
> 3. update maxmem to 10240 and confirm that it will be applied after restart
> Steps above didn't lead to any exception. Are the steps correct?

well, I re-check it and it happened with space character in the textbox (of maxmem) the maxmem is reset to zero and it enable me to continue and press 'ok' and get the exception:
Error while executing action: 
* must be greater than or equal to 1
* Attribute: vmStatic.maxMemorySizeMb
And the operation cancel.

If I set the memory and maxmem to zero it will not let me continue and press ok.
The system tab will be mark with red and I will need to reconfigure the memory again.

So we need to set low severity for this case, 
But I expect the UI to block me from continue.

Comment 5 Tomas Jelinek 2017-07-14 12:14:45 UTC
it is a very low priority item - closing due to capacity.

Please feel free to reopen if it is an important issue for your use case.


Note You need to log in before you can comment on or make changes to this bug.