You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Michal Fojtik (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/08 13:43:58 UTC
[jira] [Resolved] (DTACLOUD-151) Unhandled exception or status code
(No route to host - connect(2)) - invalid rhevm server/provider supplied
[ https://issues.apache.org/jira/browse/DTACLOUD-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik resolved DTACLOUD-151.
------------------------------------
Resolution: Fixed
Assignee: Michal Fojtik (was: David Lutterkort)
commit 80cdb7e961ff1c0590e0cdf4f0df283e83f72f51
Author: Michal Fojtik <mf...@redhat.com>
Date: Fri Feb 24 13:09:05 2012 +0100
RHEV-M: Report unaccessible API_PROVIDER as 502
Previously when API_PROVIDER was specified incorrectly
or RHEV-M API server was unaccessible, HTTP status code
500 (Internal Server Error) was reported.
HTTP specification, handle this with 502 (Bad Gateway) error.
> Unhandled exception or status code (No route to host - connect(2)) - invalid rhevm server/provider supplied
> -----------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-151
> URL: https://issues.apache.org/jira/browse/DTACLOUD-151
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: rhevm 3.0
> deltacloud-core-vsphere-0.5.0-5.el6.noarch
> deltacloud-core-ec2-0.5.0-5.el6.noarch
> deltacloud-core-rhevm-0.5.0-5.el6.noarch
> deltacloud-core-0.5.0-5.el6.noarch
> rubygem-deltacloud-client-0.5.0-2.el6.noarch
> Reporter: Ronelle Landy
> Assignee: Michal Fojtik
>
> Below are errors returned from Deltacloud when a user supplies either an invalid provider or rhevm server (note: unhandled exception error):
> Invalid rhevm provider:
> API_PROVIDER="https://10.16.120.230:8443/api;123456" deltacloudd -i rhevm -r hp-dl360g5-02.rhts.eng.bos.redhat.com -p 3008
> curl -X GET --user 'username:password'
> "http://hp-dl360g5-02.rhts.eng.bos.redhat.com:3008/api/instances?format=xml"
> <error status='404' url='/api/instances?format=xml'>
> <message>Resource not found</message>
> </error>
> >> Incorrect server:
> API_PROVIDER="https://10.16.120.235:8443/api;123456" deltacloudd -i rhevm -r hp-dl360g5-02.rhts.eng.bos.redhat.com -p 3008
> curl -X GET --user 'username:password'
> "http://hp-dl360g5-02.rhts.eng.bos.redhat.com:3008/api/instances?format=xml"
> <error status='500' url='/api/instances?format=xml'>
> <kind>backend_error</kind>
> <backend driver='rhevm' provider='https://10.16.120.235:8443/api;123456'>
> <code>500</code>
> </backend>
> <message><![CDATA[Unhandled exception or status code (No route to host -
> connect(2))]]></message>
> <backtrace>
--
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