You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Ronelle Landy (Closed) (JIRA)" <ji...@apache.org> on 2012/02/07 21:16:59 UTC
[jira] [Closed] (DTACLOUD-127) Add better error handling on
valid_credentials? request
[ https://issues.apache.org/jira/browse/DTACLOUD-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy closed DTACLOUD-127.
----------------------------------
Resolution: Fixed
Closing out this issue as per the verification steps included in comments above.
Also tested adding an account to a vsphere provider (invalid provider, valid creds; valid provider, invalid creds). The same error appeared in Conductor; An error occurred when checking provider credentials. Please check your setup and try again
> 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