incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francesco Vollero (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-88) deltacloud-core should pass back better error messages from RHEV-M errors
Date Fri, 07 Oct 2011 21:50:29 GMT


Francesco Vollero commented on DTACLOUD-88:

As Chris reported, i found that the problem is that DC report correctly the status code returned
by RHEV-m but obviously can't report the error message that is wrapped into the XML message.
This problem, discovered testing another different issue, , help me
find out that the root of the cause wasn't DC itself. A patch is planned for Monday.
> deltacloud-core should pass back better error messages from RHEV-M errors
> -------------------------------------------------------------------------
>                 Key: DTACLOUD-88
>                 URL:
>             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
> However, we can do better.  If an action fails, RHEV-M returns a piece of XML with detail,
> <?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:!default.jspa
For more information on JIRA, see:


View raw message