[
https://issues.apache.org/jira/browse/DTACLOUD-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199790#comment-13199790
]
Ronelle Landy commented on DTACLOUD-88:
---------------------------------------
Adding comments from https://bugzilla.redhat.com/show_bug.cgi?id=786535:
============================================
Through conductor I deployed 10 images but only 9 vms actually started.
Looking through the logs I found this backend exception in deltacloud-core.
This type of error need to be communicated to the user.
Version-Release number of selected component (if applicable):
=================================================================
deltacloud-core-0.5.0-4.rc1.el6.noarch
deltacloud-core-ec2-0.5.0-4.rc1.el6.noarch
deltacloud-core-rhevm-0.5.0-4.rc1.el6.noarch
deltacloud-core-vsphere-0.5.0-4.rc1.el6.noarch
rubygem-deltacloud-client-0.4.0-3.el6.noarch
Additional info:
==================================
thin server (localhost:3002) [deltacloud-mock][18292]:
RHEVM::RHEVMBackendException:Cannot run VM. There are no available running
Hosts with sufficient memory in VM's Cluster .
/usr/share/deltacloud-core/bin/../lib/deltacloud/drivers/rhevm/rhevm_client.rb:89:in
`vm_action'
> 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
