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:46:01 UTC
[jira] [Resolved] (DTACLOUD-150) Unhandled exception or status code
- invalid vsphere provider
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik resolved DTACLOUD-150.
------------------------------------
Resolution: Fixed
commit fcba437d6ae5776761a8efa608cf9039d74eee63
Author: Michal Fojtik <mf...@redhat.com>
Date: Fri Feb 24 13:02:36 2012 +0100
VSphere: Report unaccessible API_PROVIDER as 502
Previously, when client accessed VSphere through our
VSphere driver and wrong API_PROVIDER was specified,
client got 500 (Internal Server) error.
This kind of error is according to HTTP specification
covered by 502 (Bad Gateway).
> Unhandled exception or status code - invalid vsphere provider
> -------------------------------------------------------------
>
> Key: DTACLOUD-150
> URL: https://issues.apache.org/jira/browse/DTACLOUD-150
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: Rhel 6.2
> 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: David Lutterkort
>
> Querying for instances in a server with no vsphere installed results in a '[Unhandled exception or status code (Undefined namespace
> prefix: //soapenv:Body/*)' message:
> >> API_PROVIDER=10.16.120.137 deltacloudd -i vsphere -r hp-dl360g5-02.rhts.eng.bos.redhat.com -p 4006
> $ curl -X GET --user 'username:password' "http://hp-dl360g5-02.rhts.eng.bos.redhat.com:4006/api/instances?format=xml"
> <errorstatus='500' url='/api/instances?format=xml'>
> <kind>backend_error</kind>
> <backend driver='vsphere' provider='10.16.120.137'>
> <code>500</code>
> </backend>
> <message><![CDATA[Unhandled exception or status code (Undefined namespace
> prefix: //soapenv:Body/*)]]></message>
> <backtrace>
>
> <![CDATA[/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0.beta.4/lib/nokogiri/xml/node.rb:159:in
> `evaluate'
>
> /usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0.beta.4/lib/nokogiri/xml/node.rb:159:in
> `xpath'
> Comment from dev: Yes, this is a bug and we need to catch this error.
--
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