You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltacloud.apache.org by "Ramesh A (Closed) (JIRA)" <ji...@apache.org> on 2012/03/22 12:48:22 UTC
[jira] [Closed] (DTACLOUD-37) Exceptions being thrown on deltacloud
git HEAD
[ https://issues.apache.org/jira/browse/DTACLOUD-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh A closed DTACLOUD-37.
----------------------------
Closing this issue as per my previous comments
> Exceptions being thrown on deltacloud git HEAD
> ----------------------------------------------
>
> Key: DTACLOUD-37
> URL: https://issues.apache.org/jira/browse/DTACLOUD-37
> Project: DeltaCloud
> Issue Type: Bug
> Components: Server
> Environment: Fedora-14 x86_64, deltacloud git 8cad9b7c0ef143555db21edd2bc42676d0b1c594 (git-svn-id: https://svn.apache.org/repos/asf/incubator/deltacloud/trunk@1099078 13f79535-47bb-0310-9956-ffa450edef68)
> Reporter: Chris Lalancette
> Assignee: Michal Fojtik
> Attachments: lb.rb, stacktrace
>
>
> I'm testing out loadbalancer support with libdeltacloud. When I was on deltacloud server git commit dcfa28a345a1ec782b136e31a7f5a871fa1f66c9, I was able to properly run a sequence where I create a loadbalancer in EC2, look up the just created instance by ID, and then delete the loadbalancer. However, since I've updated to 8cad9b7c0ef143555db21edd2bc42676d0b1c594, I am no longer able to successfully delete the loadbalancer. I get an error like:
> New Aws::Elb using per_thread-connection mode
> Deleting Load Balancer - lb2
> Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> warning: peer certificate won't be verified in this SSL session
> ThreadError - return can't jump across threads:
> ././server.rb:346
> ././lib/sinatra/respond_to.rb:244:in `call'
> ././lib/sinatra/respond_to.rb:244:in `respond_to'
> ././server.rb:345
> ././lib/sinatra/rabbit.rb:114:in `instance_eval'
> ././lib/sinatra/rabbit.rb:114:in `DELETE /api/load_balancers/:id'
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:871:in `call'
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:871:in `route'
> /usr/lib/ruby/gems/1.8/gems/sinatra-1.0/lib/sinatra/base.rb:527:in `instance_eval'
> <snip>
> I'll attach the full stack trace.
--
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