Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
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)
Description
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.