[ 
https://issues.apache.org/jira/browse/DTACLOUD-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202722#comment-13202722
 ] 

Ronelle Landy commented on DTACLOUD-127:
----------------------------------------

According to Conductor developer: this error is a new addition to Conductor, 
and it comes up when we get an exception.

rpms used to perform the above tests:

rpm -qa |grep deltacloud
deltacloud-core-ec2-0.5.0-5.el6.noarch
deltacloud-core-0.5.0-5.el6.noarch
deltacloud-core-vsphere-0.5.0-5.el6.noarch
deltacloud-core-doc-0.5.0-5.el6.noarch
deltacloud-core-all-0.5.0-5.el6.noarch
rubygem-deltacloud-client-0.5.0-2.el6.noarch
deltacloud-core-rhevm-0.5.0-5.el6.noarch

rpm -qa |grep aeolus
aeolus-conductor-daemons-0.8.0-22.el6.noarch
rubygem-aeolus-cli-0.3.0-7.el6.noarch
aeolus-conductor-doc-0.8.0-22.el6.noarch
aeolus-configure-2.5.0-11.el6.noarch
aeolus-all-0.8.0-22.el6.noarch
aeolus-conductor-0.8.0-22.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch

                
> 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

        

Reply via email to