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 (Created) (JIRA)" <ji...@apache.org> on 2012/02/24 15:24:48 UTC
[jira] [Created] (DTACLOUD-150) Unhandled exception or status code
- invalid vsphere provider
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
[jira] [Resolved] (DTACLOUD-150) Unhandled exception or status code
- invalid vsphere provider
Posted by "Michal Fojtik (Resolved) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Closed] (DTACLOUD-150) Unhandled exception or status code -
invalid vsphere provider
Posted by "Ronelle Landy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy closed DTACLOUD-150.
----------------------------------
Resolution: Fixed
This works for deltacloud commit version 8e5669ad88ccc77f18bde0aaf7a6f6beb859f1f9. See test results copied below:
curl -X GET --user '<un>:<pw>' "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml" | more
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
45 35604 45 16141 0 0 759 0 0:00:46 0:00:21 0:00:<error status='504' url='/api/images?format=xml'>
25 <kind>backend_error</kind>
3817 <backend driver='vsphere' provider='10.16.120.137'>
<code>504</code>
</backend>
<message><![CDATA[Connection timed out - connect(2)]]></message>
<backtrace><![CDATA[/usr/lib/ruby/1.8/net/http.rb:560:in `initialize'
100 35/usr/lib/ruby/1.8/net/http.rb:560:in `open'
604 1/usr/lib/ruby/1.8/net/http.rb:560:in `connect'
00 356/usr/lib/ruby/1.8/timeout.rb:67:in `timeout'
04 /usr/lib/ruby/1.8/timeout.rb:101:in `timeout'
0 /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
0 167/usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
5 /usr/lib/ruby/1.8/net/http.rb:548:in `start'
0 0:00:2/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.5.1/lib/rbvmomi/trivial_soap.rb:56:in `res
1 tart_http'
or if there is no timeout but a 'bad gateway':
curl -X GET --user '<un>:<pw>' "http://qe-blade-02.idm.lab.bos.redhat.com:3006/api/images?format=xml" | more
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 35800 100 35800 0 0 191k <error status='502' url='/api/images?format=xml'>
<kind>backend_error</kind>
0 --:-- <backend driver='vsphere' provider='10.16.120.225'>
:-- <code>502</code>
- </backend>
-:--:-- <message><![CDATA[VSphere Internal Error]]></message>
--:--:-- 1 <backtrace><![CDATA[/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.3/lib/nokogiri/xm
93kl/node.rb:159:in `evaluate'
> 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: Michal Fojtik
>
> 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
[jira] [Commented] (DTACLOUD-150) Unhandled exception or status
code - invalid vsphere provider
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266498#comment-13266498 ]
Ramesh A commented on DTACLOUD-150:
-----------------------------------
Able to reproduce this issue on API_PROVIDER=10.16.120.136, Which was working fine previously
> 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: Michal Fojtik
>
> 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
[jira] [Reopened] (DTACLOUD-150) Unhandled exception or status code
- invalid vsphere provider
Posted by "Ronelle Landy (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy reopened DTACLOUD-150:
------------------------------------
Tested deltacloud commit version: 61ac9fef965dd7d1af7c213357ea7d66630d88d7 clone: from https://git-wip-us.apache.org/repos/asf/deltacloud.git
Still seeing the same unhandled exception for na invalid vsphere server:
>> API_PROVIDER=10.16.120.137 ./bin/deltacloudd -i vsphere -r localhost -p 3009
curl -X GET --user 'username:password' "http://localhost:3009/api/instances?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<error status='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/lib/nokogiri/xml/node.rb:159:in `evaluate'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0/lib/nokogiri/xml/node.rb:159:in `xpath'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0/lib/nokogiri/xml/node.rb:150:in `map'
/usr/lib/ruby/gems/1.8/gems/nokogiri-1.5.0/lib/nokogiri/xml/node.rb:150:in `xpath'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/trivial_soap.rb:104:in `request'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/connection.rb:67:in `call'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/basic_types.rb:187:in `_call'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/basic_types.rb:69:in `RetrieveServiceContent'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/vim.rb:79:in `serviceContent'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/vim.rb:35:in `connect'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/vim.rb:34:in `tap'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.4.0/lib/rbvmomi/vim.rb:34:in `connect'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:399:in `new_client'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/base_driver/exceptions.rb:173:in `call'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/base_driver/exceptions.rb:173:in `safely'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:398:in `new_client'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/drivers/vsphere/vsphere_driver.rb:148:in `instances'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/helpers/application_helper.rb:81:in `send'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/helpers/application_helper.rb:81:in `filter_all'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/helpers/application_helper.rb:80:in `filter_all'
/home/rlandy/workspace/deltacloud/server/lib/deltacloud/server.rb:464
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rabbit.rb:125:in `instance_eval'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rabbit.rb:125:in `GET /api/instances'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1211:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1211:in `compile!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `[]'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:788:in `route_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:772:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:821:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:819:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:819:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:771:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:770:in `each'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:770:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:706:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:706:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:692:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/commonlogger.rb:20:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_date.rb:31:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_accept.rb:149:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/showexceptions.rb:21:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_driver_select.rb:45:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_matrix_params.rb:106:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_runtime.rb:36:in `call'
/home/rlandy/workspace/deltacloud/server/lib/sinatra/rack_etag.rb:41:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-accept-0.4.4/lib/rack/accept/context.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.1.4/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/logger.rb:15:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/commonlogger.rb:20:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.3.5/lib/rack/methodoverride.rb:24:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1403:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.1/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:80:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `catch'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:78:in `pre_process'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `call'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1060:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `initialize'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `new'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1057:in `spawn_threadpool'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:1049:in `defer'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:50:in `process'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/connection.rb:38:in `receive_data'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
/usr/lib/ruby/gems/1.8/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/backends/base.rb:61:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/server.rb:159:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/controllers/controller.rb:86:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `send'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:185:in `run_command'
/usr/lib/ruby/gems/1.8/gems/thin-1.3.1/lib/thin/runner.rb:151:in `run!'
./bin/deltacloudd:239]]>
</backtrace>
<request>
<param name='format'>xml</param>
</request>
</error>
> 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: Michal Fojtik
>
> 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
[jira] [Commented] (DTACLOUD-150) Unhandled exception or status
code - invalid vsphere provider
Posted by "Ronelle Landy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244164#comment-13244164 ]
Ronelle Landy commented on DTACLOUD-150:
----------------------------------------
Related to BZ-805171
> 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: Michal Fojtik
>
> 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
[jira] [Assigned] (DTACLOUD-150) Unhandled exception or status code
- invalid vsphere provider
Posted by "Michal Fojtik (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michal Fojtik reassigned DTACLOUD-150:
--------------------------------------
Assignee: Michal Fojtik (was: David Lutterkort)
> 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: Michal Fojtik
>
> 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
[jira] [Issue Comment Edited] (DTACLOUD-150) Unhandled exception or
status code - invalid vsphere provider
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266498#comment-13266498 ]
Ramesh A edited comment on DTACLOUD-150 at 5/2/12 11:58 AM:
------------------------------------------------------------
Able to reproduce this issue on API_PROVIDER=10.16.120.136 and 10.16.120.224 Which was working fine previously. Not sure what has went wrong.
was (Author: rananda):
Able to reproduce this issue on API_PROVIDER=10.16.120.136, Which was working fine previously. Not sure what has went wrong.
> 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: Michal Fojtik
>
> 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
[jira] [Issue Comment Edited] (DTACLOUD-150) Unhandled exception or
status code - invalid vsphere provider
Posted by "Ramesh A (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266498#comment-13266498 ]
Ramesh A edited comment on DTACLOUD-150 at 5/2/12 11:49 AM:
------------------------------------------------------------
Able to reproduce this issue on API_PROVIDER=10.16.120.136, Which was working fine previously. Not sure what has went wrong.
was (Author: rananda):
Able to reproduce this issue on API_PROVIDER=10.16.120.136, Which was working fine previously
> 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: Michal Fojtik
>
> 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