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/01/08 04:40:39 UTC
[jira] [Created] (DTACLOUD-125) Error when accessing Deltacloud API
collections that require log in - Vsphere provider; deltacloud-core-0.5.0
Error when accessing Deltacloud API collections that require log in - Vsphere provider; deltacloud-core-0.5.0
--------------------------------------------------------------------------------------------------------------
Key: DTACLOUD-125
URL: https://issues.apache.org/jira/browse/DTACLOUD-125
Project: DeltaCloud
Issue Type: Bug
Components: Server
Environment: deltacloud-core-0.5.0 installed from http://people.apache.org/~lutter/deltacloud/0.5.0/rc1/; RHEL 6
Reporter: Ronelle Landy
Assignee: David Lutterkort
The following error is returned when accessing collections that require log in (realms, images, instances, hardware profiles) for Vsphere Deltacloud server:
Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (getaddrinfo: Name or service not known)
Below is the same error accessed from the API directly:
curl -X GET --user 'username:password' "http://server:3006/api/images?format=xml"
<error status='500' url='/api/images?format=xml'>
<kind>backend_error</kind>
<backend driver='vsphere'>
<code>500</code>
</backend>
<message><![CDATA[Unhandled exception or status code (getaddrinfo: Name or service not known)]]></message>
</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-125) Error when accessing Deltacloud
API collections that require log in - Vsphere provider;
deltacloud-core-0.5.0
Posted by "Ronelle Landy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182640#comment-13182640 ]
Ronelle Landy commented on DTACLOUD-125:
----------------------------------------
=== Copying trace from UI: ===
500 - Internal Server Error
Unhandled exception or status code (getaddrinfo: Name or service not known)
Server message
Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (getaddrinfo: Name or service not known)
Original request URI
/api/images Retry
Error details
No details
Backtrace click to expand contents
/usr/lib/ruby/1.8/net/http.rb:560:in `initialize'
/usr/lib/ruby/1.8/net/http.rb:560:in `open'
/usr/lib/ruby/1.8/net/http.rb:560:in `connect'
/usr/lib/ruby/1.8/timeout.rb:67:in `timeout'
/usr/lib/ruby/1.8/timeout.rb:101:in `timeout'
/usr/lib/ruby/1.8/net/http.rb:560:in `connect'
/usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
/usr/lib/ruby/1.8/net/http.rb:548:in `start'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.5.0/lib/rbvmomi/trivial_soap.rb:56:in `restart_http'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.5.0/lib/rbvmomi/trivial_soap.rb:20:in `initialize'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.5.0/lib/rbvmomi/connection.rb:31:in `initialize'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.5.0/lib/rbvmomi/vim.rb:34:in `new'
/usr/lib/ruby/gems/1.8/gems/rbvmomi-1.5.0/lib/rbvmomi/vim.rb:34:in `connect'
./bin/../lib/deltacloud/drivers/vsphere/vsphere_driver.rb:382:in `new_client'
./bin/../lib/deltacloud/base_driver/exceptions.rb:151:in `call'
./bin/../lib/deltacloud/base_driver/exceptions.rb:151:in `safely'
./bin/../lib/deltacloud/drivers/vsphere/vsphere_driver.rb:381:in `new_client'
./bin/../lib/deltacloud/drivers/vsphere/vsphere_driver.rb:72:in `images'
./bin/../lib/deltacloud/helpers/application_helper.rb:80:in `send'
./bin/../lib/deltacloud/helpers/application_helper.rb:80:in `filter_all'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
./bin/../lib/deltacloud/helpers/application_helper.rb:79:in `filter_all'
./bin/../lib/deltacloud/server.rb:236
./bin/../lib/sinatra/rabbit.rb:125:in `instance_eval'
./bin/../lib/sinatra/rabbit.rb:125:in `GET /api/images'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1211:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1211:in `compile!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `[]'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:801:in `route_eval'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:822:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:820:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:820:in `process_route'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:784:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:783:in `each'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:783:in `route!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:886:in `dispatch!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `catch'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:871:in `invoke'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:719:in `call!'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:705:in `call'
./bin/../lib/sinatra/rack_date.rb:31:in `call'
./bin/../lib/sinatra/rack_accept.rb:149:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.0/lib/rack/nulllogger.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.0/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/showexceptions.rb:21:in `call'
./bin/../lib/sinatra/rack_driver_select.rb:45:in `call'
./bin/../lib/sinatra/rack_matrix_params.rb:106:in `call'
./bin/../lib/sinatra/rack_runtime.rb:36:in `call'
./bin/../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.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.0/lib/rack/logger.rb:15:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.0/lib/rack/head.rb:9:in `call'
/usr/lib/ruby/gems/1.8/gems/rack-1.4.0/lib/rack/methodoverride.rb:21:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1334:in `call'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/lib/sinatra/base.rb:1416:in `synchronize'
/usr/lib/ruby/gems/1.8/gems/sinatra-1.3.2/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:235
Parameters click to expand contents
splat
[]
captures
[#]
> Error when accessing Deltacloud API collections that require log in - Vsphere provider; deltacloud-core-0.5.0
> --------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-125
> URL: https://issues.apache.org/jira/browse/DTACLOUD-125
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud-core-0.5.0 installed from http://people.apache.org/~lutter/deltacloud/0.5.0/rc1/; RHEL 6
> Reporter: Ronelle Landy
> Assignee: David Lutterkort
> Priority: Blocker
>
> The following error is returned when accessing collections that require log in (realms, images, instances, hardware profiles) for Vsphere Deltacloud server:
> Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (getaddrinfo: Name or service not known)
> Below is the same error accessed from the API directly:
> curl -X GET --user 'username:password' "http://server:3006/api/images?format=xml"
> <error status='500' url='/api/images?format=xml'>
> <kind>backend_error</kind>
> <backend driver='vsphere'>
> <code>500</code>
> </backend>
> <message><![CDATA[Unhandled exception or status code (getaddrinfo: Name or service not known)]]></message>
> </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-125) Error when accessing Deltacloud API
collections that require log in - Vsphere provider; deltacloud-core-0.5.0
Posted by "Ronelle Landy (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy closed DTACLOUD-125.
----------------------------------
Resolution: Not A Problem
Changing the way the Vshpere server is started, fixes the error.
> Error when accessing Deltacloud API collections that require log in - Vsphere provider; deltacloud-core-0.5.0
> --------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-125
> URL: https://issues.apache.org/jira/browse/DTACLOUD-125
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud-core-0.5.0 installed from http://people.apache.org/~lutter/deltacloud/0.5.0/rc1/; RHEL 6
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Blocker
>
> The following error is returned when accessing collections that require log in (realms, images, instances, hardware profiles) for Vsphere Deltacloud server:
> Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (getaddrinfo: Name or service not known)
> Below is the same error accessed from the API directly:
> curl -X GET --user 'username:password' "http://server:3006/api/images?format=xml"
> <error status='500' url='/api/images?format=xml'>
> <kind>backend_error</kind>
> <backend driver='vsphere'>
> <code>500</code>
> </backend>
> <message><![CDATA[Unhandled exception or status code (getaddrinfo: Name or service not known)]]></message>
> </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-125) Error when accessing Deltacloud
API collections that require log in - Vsphere provider;
deltacloud-core-0.5.0
Posted by "Ronelle Landy (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182675#comment-13182675 ]
Ronelle Landy commented on DTACLOUD-125:
----------------------------------------
Closing issue:
Need to access Vsphere server using just the server name and not 'https' proceeding it.
> Error when accessing Deltacloud API collections that require log in - Vsphere provider; deltacloud-core-0.5.0
> --------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-125
> URL: https://issues.apache.org/jira/browse/DTACLOUD-125
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud-core-0.5.0 installed from http://people.apache.org/~lutter/deltacloud/0.5.0/rc1/; RHEL 6
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Blocker
>
> The following error is returned when accessing collections that require log in (realms, images, instances, hardware profiles) for Vsphere Deltacloud server:
> Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (getaddrinfo: Name or service not known)
> Below is the same error accessed from the API directly:
> curl -X GET --user 'username:password' "http://server:3006/api/images?format=xml"
> <error status='500' url='/api/images?format=xml'>
> <kind>backend_error</kind>
> <backend driver='vsphere'>
> <code>500</code>
> </backend>
> <message><![CDATA[Unhandled exception or status code (getaddrinfo: Name or service not known)]]></message>
> </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] [Updated] (DTACLOUD-125) Error when accessing Deltacloud API
collections that require log in - Vsphere provider; deltacloud-core-0.5.0
Posted by "Ronelle Landy (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy updated DTACLOUD-125:
-----------------------------------
Priority: Blocker (was: Major)
> Error when accessing Deltacloud API collections that require log in - Vsphere provider; deltacloud-core-0.5.0
> --------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-125
> URL: https://issues.apache.org/jira/browse/DTACLOUD-125
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud-core-0.5.0 installed from http://people.apache.org/~lutter/deltacloud/0.5.0/rc1/; RHEL 6
> Reporter: Ronelle Landy
> Assignee: David Lutterkort
> Priority: Blocker
>
> The following error is returned when accessing collections that require log in (realms, images, instances, hardware profiles) for Vsphere Deltacloud server:
> Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (getaddrinfo: Name or service not known)
> Below is the same error accessed from the API directly:
> curl -X GET --user 'username:password' "http://server:3006/api/images?format=xml"
> <error status='500' url='/api/images?format=xml'>
> <kind>backend_error</kind>
> <backend driver='vsphere'>
> <code>500</code>
> </backend>
> <message><![CDATA[Unhandled exception or status code (getaddrinfo: Name or service not known)]]></message>
> </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-125) Error when accessing Deltacloud
API collections that require log in - Vsphere provider;
deltacloud-core-0.5.0
Posted by "Ronelle Landy (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DTACLOUD-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ronelle Landy reassigned DTACLOUD-125:
--------------------------------------
Assignee: Ronelle Landy (was: David Lutterkort)
> Error when accessing Deltacloud API collections that require log in - Vsphere provider; deltacloud-core-0.5.0
> --------------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-125
> URL: https://issues.apache.org/jira/browse/DTACLOUD-125
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: deltacloud-core-0.5.0 installed from http://people.apache.org/~lutter/deltacloud/0.5.0/rc1/; RHEL 6
> Reporter: Ronelle Landy
> Assignee: Ronelle Landy
> Priority: Blocker
>
> The following error is returned when accessing collections that require log in (realms, images, instances, hardware profiles) for Vsphere Deltacloud server:
> Deltacloud::ExceptionHandler::BackendError - Unhandled exception or status code (getaddrinfo: Name or service not known)
> Below is the same error accessed from the API directly:
> curl -X GET --user 'username:password' "http://server:3006/api/images?format=xml"
> <error status='500' url='/api/images?format=xml'>
> <kind>backend_error</kind>
> <backend driver='vsphere'>
> <code>500</code>
> </backend>
> <message><![CDATA[Unhandled exception or status code (getaddrinfo: Name or service not known)]]></message>
> </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