[jira] [Closed] (DTACLOUD-88) deltacloud-core should pass back better error messages from RHEV-M errors

["Ronelle Landy (Closed) (JIRA)" <ji...@apache.org>]

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

Ronelle Landy closed DTACLOUD-88.
---------------------------------

    Resolution: Fixed

Closing out this JIRA based on comments above and the results of BZ-786535.
                
> deltacloud-core should pass back better error messages from RHEV-M errors
> -------------------------------------------------------------------------
>
>                 Key: DTACLOUD-88
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-88
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>         Environment: Fedora-15, deltacloud-core-0.5.0-0.2.1317167702git.fc15.noarch (nightly)
>            Reporter: Chris Lalancette
>            Assignee: David Lutterkort
>
> When trying to run a RHEV-M action (lib/deltacloud/drivers/rhevm/rhevm_client.rb:vm_action()), the action may fail.  If it does, deltacloud-core returns a pretty generic: Operation start failed.
> However, we can do better.  If an action fails, RHEV-M returns a piece of XML with detail, like:
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <action>
>     <status>
>         <state>failed</state>
>     </status>
>     <fault>
>         <reason>Nogah operation failed</reason>
>         <detail>[Cannot run VM. VM is not found.]</detail>
>     </fault>
> </action>
> We should parse that detail out and return it as part of the exception so that the client will have a better idea of what the problem is.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira