You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Chris Lalancette (Created) (JIRA)" <ji...@apache.org> on 2011/10/07 20:54:29 UTC
[jira] [Created] (DTACLOUD-88) deltacloud-core should pass back
better error messages from RHEV-M errors
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
[jira] [Commented] (DTACLOUD-88) deltacloud-core should pass back
better error messages from RHEV-M errors
Posted by "Francesco Vollero (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123233#comment-13123233 ]
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, http://fpaste.org/veII/ , 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: 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