deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martyn Taylor (Commented) (JIRA)" <>
Subject [jira] [Commented] (DTACLOUD-127) Add better error handling on valid_credentials? request
Date Mon, 06 Feb 2012 17:41:59 GMT


Martyn Taylor commented on DTACLOUD-127:

I've received this patch from fvollero:;a=commit;h=2fbc147f9e3041b19f2c89e4d222ba2185486405

but this only addresses the problem in ec2 driver.  We need this addressed for all drivers.

There's also a fundamental issue in the client, in that it does not properly handle HTTP Error
codes.  I would expect that all the error codes are wrapped in an appropriate exception and
raised.  We at least need to handle HTTP Errors in the clients valid_credentials method in
order to resolve the conductor BZ highlighted in the original description.
> Add better error handling on valid_credentials? request
> -------------------------------------------------------
>                 Key: DTACLOUD-127
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Martyn Taylor
>            Assignee: Michal Fojtik
> In order to determine why a particular valid_credentials? request (using the ruby client)
has failed.  There should be sufficient error/exceptions.  
> Example:
> thin server (localhost:3002) [deltacloud-mock][22098]:
> Aws::AwsError:ec2-eu-west-1 temporarily unavailable: (getaddrinfo: Name or service not
> This causes failure of the valid_credentials? method but offers no more information.
> This is related to this BZ in aeolus-conductor: 

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