Bug 988056 - We should have maximum value for Maximum number of VMs per user
Summary: We should have maximum value for Maximum number of VMs per user
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Martin Betak
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 15:46 UTC by Maor
Modified: 2013-09-23 07:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 07:27:32 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)
log (1.02 MB, text/x-log)
2013-07-24 15:47 UTC, Maor 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 17677 0 None None None Never

Description Maor 2013-07-24 15:46:55 UTC 
Description of problem:
We can put a very bug number in the "Maximum number of VMs per user" column and the engine can't parse it

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. put any number bigger then 1,000,000 (I tried 100,000,000) in the "Maximum number of VMs per user" text box
2. press on ok
3. edit the pool again

Actual results:
You will see negative number (or wrong number)

Expected results:
We should validate the maximum number and present an appropriate message to the user

Additional info:
Comment 1 Maor 2013-07-24 15:47:33 UTC 
Created attachment 777849 [details]
log
Comment 2 Michal Skrivanek 2013-07-25 07:53:36 UTC 
either the parsing should be fixed or we can put some artificial big-enough limit like 1000000
Comment 3 Itamar Heim 2013-08-21 16:40:23 UTC 
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)
Comment 4 Itamar Heim 2013-09-23 07:27:32 UTC 
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)
Note You need to log in before you can comment on or make changes to this bug.