Bug 988051 - We get enum message instead of a text one when putting a negative number in "Maximum number of VMs per user"
We get enum message instead of a text one when putting a negative number in "...
Product: oVirt
Classification: Community
Component: ovirt-engine-core (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Martin Betak
Depends On:
  Show dependency treegraph
Reported: 2013-07-24 11:38 EDT by Maor
Modified: 2013-08-01 17:17 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 17:17:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
engine log (1.02 MB, text/x-log)
2013-07-24 11:38 EDT, Maor
no flags Details

  None (edit)
Description Maor 2013-07-24 11:38:06 EDT
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:

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"

Actual results:

Expected results:
There should be a text message

Additional info:
The enum should be added to VdcBllMessages
Comment 1 Martin Betak 2013-08-01 14:49:39 EDT
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.

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