You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2014/10/14 18:24:34 UTC

[jira] [Updated] (CLOUDSTACK-7105) Detail errortext in the API response

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Animesh Chaturvedi updated CLOUDSTACK-7105:
-------------------------------------------
    Assignee: Anshul Gangwar

> Detail errortext in the API response
> ------------------------------------
>
>                 Key: CLOUDSTACK-7105
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7105
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>            Priority: Minor
>
> While using cloudstack API and GUI, we feel error text should be in detail to recognize the error condition and trace the error cause. 
>  For example, in deployVirtualMachine API 
> ◾Case1) if there is no resource available, "# of POD resource full"
> ◾Case2) if service offering is not correct, "There's no host (or storage) to support service offering"
> ◾Case3) if volume migration failed while attaching volumes to vm of other cluster, "Volume attach/detach timeout error"
> ◾And so on.
> We can trace management-server.log, but not all other system using cloudstack api can trace that log file. 
>  This requirement can be a little vague and broad. But it can be very helpful in operational point of view. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)