deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DTACLOUD-150) Unhandled exception or status code - invalid vsphere provider
Date Mon, 04 Jun 2012 18:28:23 GMT

     [ 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

        

Mime
View raw message