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 (JIRA)" <ji...@apache.org> on 2012/06/12 08:55:42 UTC
[jira] [Commented] (DTACLOUD-169) Deltacloud API does not validate
for the existence of an load balancer while deleting it in EC2 setup
[ https://issues.apache.org/jira/browse/DTACLOUD-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13293396#comment-13293396 ]
Ramesh A commented on DTACLOUD-169:
-----------------------------------
Verification Failed. Hence re-opening this issue
Environment:
==========
OS- RHEL 6.2, Fedora 16
[root@server ~]# rpm -qa| grep deltacloud
deltacloud-core-ec2-0.6.0-2.el6.noarch
deltacloud-core-0.6.0-2.el6.noarch
deltacloud-core-all-0.6.0-2.el6.noarch
deltacloud-core-rhevm-0.6.0-2.el6.noarch
deltacloud-core-doc-0.6.0-2.el6.noarch
deltacloud-core-vsphere-0.6.0-2.el6.noarch
Also, found in commit - c71c8cceee27fb356651fd3100dc2ac6fd83accd
Verification Details:
==============
Deleting from Web-ui:
================
1. Displays "Sinatra doesn’t know this ditty" on the web page
2 Throws error in the terminal
Log Snippet:
==========
127.0.0.1 - - [12/Jun/2012 06:34:09] "GET /api/__sinatra__/404.png HTTP/1.1" 404 463 0.0129
Deleting from cURL:
===============
Tried two scenarios
1. Deleting an existing Load Balancer
2. Deleting an non-existing Load Balancer
Both of the above scenarios yields the same result
[rananda@rananda ~]$ curl -X Delete --user "username:password" "http://localhost:3003/api/load_balancers/ramesh-test-aws-lb?format=xml"
curl: (52) Empty reply from server
Log o/p:
========
!! Invalid request
Invalid HTTP format, parsing fails.
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/request.rb:82:in `execute'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/request.rb:82:in `parse'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/connection.rb:42: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.2.11/lib/thin/backends/base.rb:61:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/server.rb:159:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/controllers/controller.rb:86:in `start'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/runner.rb:185:in `send'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/runner.rb:185:in `run_command'
/usr/lib/ruby/gems/1.8/gems/thin-1.2.11/lib/thin/runner.rb:151:in `run!'
/usr/share/deltacloud-core/bin/deltacloudd:239
/usr/bin/deltacloudd:5:in `load'
/usr/bin/deltacloudd:5
> Deltacloud API does not validate for the existence of an load balancer while deleting it in EC2 setup
> -----------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-169
> URL: https://issues.apache.org/jira/browse/DTACLOUD-169
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: Deltacloud API 0.5.0
> commit - 7e372dfca79c02a799046287e5936129216b781b
> OS - Fedora 16, RHEl 6.1
> Setup - EC2
> Reporter: Ramesh A
> Assignee: Michal Fojtik
>
> Deltacloud API does not validate for the existence of an load balancer while deleting it for EC2 setup.
> Scenario's:
> ==========
> 1. Try deleting the an existing load balancer multiple times
> 2. Try deleting the non existing load balancer (can be executed multiple times also)
> Curl Command: (Note i have executed this command trice and deltacloud API does not seems to validate and give the same output in the console)
> ===========
> curl -X DELETE --user "user:password" "http://localhost:3003/api/load_balancers/ramesh-test-lb?format=xml"
> Console o/p:
> =========
> First time:
> ========
> I, [2012-03-22T18:08:14.750269 #11412] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-03-22T18:08:14.750591 #11412] INFO -- : Deleting Load Balancer - ramesh-test-lb
> W, [2012-03-22T18:08:14.751262 #11412] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
> I, [2012-03-22T18:08:14.751330 #11412] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> 127.0.0.1 - - [22/Mar/2012 18:08:16] "DELETE /api/load_balancers/ramesh-test-lb?format=xml HTTP/1.1" 204 - 1.6519
> Second Time:
> ==========
> I, [2012-03-22T18:08:25.004502 #11412] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-03-22T18:08:25.004618 #11412] INFO -- : Deleting Load Balancer - ramesh-test-lb
> W, [2012-03-22T18:08:25.005328 #11412] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
> I, [2012-03-22T18:08:25.005416 #11412] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> 127.0.0.1 - - [22/Mar/2012 18:08:26] "DELETE /api/load_balancers/ramesh-test-lb?format=xml HTTP/1.1" 204 - 1.6351
> Third Time:
> ========
> I, [2012-03-22T18:08:28.944863 #11412] INFO -- : New Aws::Elb using per_thread-connection mode
> I, [2012-03-22T18:08:28.945209 #11412] INFO -- : Deleting Load Balancer - ramesh-test-lb
> W, [2012-03-22T18:08:28.945891 #11412] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
> I, [2012-03-22T18:08:28.945966 #11412] INFO -- : Opening new HTTPS connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> 127.0.0.1 - - [22/Mar/2012 18:08:30] "DELETE /api/load_balancers/ramesh-test-lb?format=xml HTTP/1.1" 204 - 1.6125
--
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