[
https://issues.apache.org/jira/browse/DTACLOUD-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ronelle Landy closed DTACLOUD-89.
---------------------------------
Resolution: Not A Problem
Closing this JIRA issue out. Deltacloud does report when actions are not
supported on an instance in a particular state:
Example: executing 'start' on a RUNNING instance
<error status='405'
url='/api/instances/bf388696-55a4-4fb2-b2d8-170416651a28/start?format=xml'>
<message>
Requested method not allowed
</message>
<method>
POST
</method>
</error>
and executing GET /api/instance/:id will show the supported actions for the
instance in its current state:
<actions>
<link
href='http://server:3001/api/instances/bf388696-55a4-4fb2-b2d8-170416651a28/stop'
method='post' rel='stop' />
<link
href='http://server:3001/api/images;instance_id=bf388696-55a4-4fb2-b2d8-170416651a28'
method='post' rel='create_image' />
</actions>
so comments are verified.
Will add testing for client responses to backend errors.
> deltacloud-client should throw an exception if an action fails
> --------------------------------------------------------------
>
> Key: DTACLOUD-89
> URL: https://issues.apache.org/jira/browse/DTACLOUD-89
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby)
> Environment: Fedora-15, rubygem-deltacloud-client-0.4.0-3.fc15.noarch
> Reporter: Chris Lalancette
> Assignee: Michal Fojtik
>
> Aeolus was running the following code:
> dcloud_instance.send(action)
> (where action == :start!)
> However, the RHEV-M datacenter that this was being run against failed to
> start the instance. Not only did deltacloud-core fail to return a usable
> error message (https://issues.apache.org/jira/browse/DTACLOUD-88), but the
> deltacloud client also did not seem to throw an exception for this failure.
> If the call outright fails, the ruby-ish thing to do is probably to raise an
> exception and let the user deal with it.
--
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
