[
https://issues.apache.org/jira/browse/DTACLOUD-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201423#comment-13201423
]
Martyn Taylor commented on DTACLOUD-127:
----------------------------------------
I've received this patch from fvollero:
https://git-wip-us.apache.org/repos/asf?p=deltacloud.git;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: https://issues.apache.org/jira/browse/DTACLOUD-127
> 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 known)
> This causes failure of the valid_credentials? method but offers no more
> information.
> This is related to this BZ in aeolus-conductor:
> https://bugzilla.redhat.com/show_bug.cgi?id=753880
--
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