Bug 988036

Summary: We get enum instead of a message when user tries to run more VMs from the User portal then he has permissions to
Product: [Retired] oVirt Reporter: Maor <mlipchuk>
Component: ovirt-engine-userportalAssignee: Martin Betak <mbetak>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, ecohen, 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:53 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
CDA
none
log none

Description Maor 2013-07-24 14:55:36 UTC
Created attachment 777835 [details]
CDA

Description of problem:
We get enum message instead of a text message.

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


How reproducible:


Steps to Reproduce:
1. In the admin portal set Maximum number of VMs per user to 2
2. In the user portal start the first VM
3. Go back to the admin portal and set the Maximum number of VMs per user to 1
4. in the User portal try to start the second VM

Actual results:
we get the CDA message VM_POOL_CANNOT_ATTACH_TO_MORE_VMS_FROM_POOL

Expected results:
We should get the message:
"User is already attached to maximum number of VMs from this VM-Pool."

Additional info:

Comment 1 Maor 2013-07-24 14:58:25 UTC
Created attachment 777837 [details]
log

Comment 2 Maor 2013-07-24 15:37:54 UTC
enum value should be added to vdcBllMessages

Comment 3 Itamar Heim 2013-08-21 16:43:10 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:53 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)