Bug 988051

Summary: We get enum message instead of a text one when putting a negative number in "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-08-01 21:17:12 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
engine log none

Description Maor 2013-07-24 15:38:06 UTC 
Created attachment 777846 [details]
engine log

Description of problem:
Try to put a negative number in the "Maximum number of VMs per user" through the API

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


How reproducible:
100%

Steps to Reproduce: ( It can be reproduced through rest Although I succeeded to reproduce this from the GUI due to another issue I encountered)
1. Put negative in "Maximum number of VMs per user"
2.
3.

Actual results:
VALIDATION_VM_POOLS_NUMBER_OF_MAX_ASSIGNED_VMS_OUT_OF_RANGE

Expected results:
There should be a text message

Additional info:
The enum should be added to VdcBllMessages
Comment 1 Martin Betak 2013-08-01 18:49:39 UTC 
The enum value VALIDATION_VM_POOLS_NUMBER_OF_MAX_ASSIGNED_VMS_OUT_OF_RANGE was replaced by VALIDATION.VM_POOLS.NUMBER_OF_MAX_ASSIGNED_VMS_OUT_OF_RANGE in 9e029f322b13409243f814c98159a8a676dd3ef5 and since this patch it also returns correct message when trying to set negative value via REST api.