Bug 988056

Summary: We should have maximum value for Maximum number of VMs per user
Product: [Retired] oVirt Reporter: Maor <mlipchuk>
Component: ovirt-engine-coreAssignee: Martin Betak <mbetak>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, iheim, michal.skrivanek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-23 07:27:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log none

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)