Surfacing an exception that makes sense based on the role of the user
receiving the exception will require a more fundamental change: The
error message you see is basically the cleaned version of what the
admin sees. Looking at the ApiServer you'll see that whether the user
context receives - InsufficientCapacityException,
ResourceAllocationException, ResourceUnavailableException or just any
other generic exception the api decides to throw - the user will
receive the 'internal error' message. And the class of APIs that will
see this kind of filtering is anything that implements the BaseCmd
which is just about every API in cloudstack :)

On 3 April 2013 12:39, Sailaja Mada <sailaja.m...@citrix.com> wrote:
> It would be good to mention failure reason with out providing the information 
> about specific Resource type and domain id .
>
> Thanks,
> Sailaja.M
>
> -----Original Message-----
> From: Ahmad Emneina [mailto:aemne...@gmail.com]
> Sent: Wednesday, April 03, 2013 12:32 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [ACS42][QA]Limit Resources - Internal Error when there are no 
> resources available
>
> this is done to hide potentially sensitive operational/resource information 
> from end users. Limiting exploitation vectors. probably worth a discussion 
> and/or a feature enhancement to modify the behavior.
>
>
> On Tue, Apr 2, 2013 at 11:27 PM, Sailaja Mada <sailaja.m...@citrix.com>wrote:
>
>> Hi,
>>
>> I have set the limit to use x amount of resources for the Domain Admin
>> account. When there are not enough resources available and tried to
>> deploy VM,  this user gets the message as "Internal error executing
>> command, please contact your system administrator"  .
>>
>> Only in the Management Server log  , root user can get the reason why
>> it failed as INFO Message : 2013-04-03 11:50:59,813 INFO
>> [cloud.api.ApiServer] (catalina-exec-18:null) Maximum number of
>> resources of type 'cpu' for domain id=3 has been exceeded."
>>
>> Is there any reason why we can not provide the root cause for failure
>> to Child Domain Account ?
>>
>> Thanks,
>> Sailaja.M
>>

Reply via email to