[ 
https://issues.apache.org/jira/browse/DTACLOUD-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh A closed DTACLOUD-169.
-----------------------------

    Resolution: Fixed
      Assignee: Ramesh A  (was: Michal Fojtik)
    
> 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: Ramesh A
>
> 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

        

Reply via email to