[
https://issues.apache.org/jira/browse/DTACLOUD-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Fojtik resolved DTACLOUD-168.
------------------------------------
Resolution: Won't Fix
Assignee: Michal Fojtik (was: David Lutterkort)
Unfortunately I can't fix this issue without querying the EC2 API for existence
of load_balancer. The EC2 should respond with something more clever in this
case :(
> Validation fails for creating load balancers with the same name multiple
> times for EC2 setup
> --------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-168
> URL: https://issues.apache.org/jira/browse/DTACLOUD-168
> Project: DeltaCloud
> Issue Type: Bug
> Components: Client (Ruby), Server
> Environment: Deltacloud API 0.5.0
> commit - 7e372dfca79c02a799046287e5936129216b781b
> OS - Fedora 15, 16, RHEl 6.1
> Setup - EC2
> Reporter: Ramesh A
> Assignee: Michal Fojtik
>
> Deltacloud API does not validate for the existance of loadbalancer with the
> same name and allows to create load balancers with the same name. However,
> there is only one load balancer displayed nevertheless how many times it has
> been created with the same name. This behavior is observed both in UI and
> curl.
> Console o/p:
> =========
> First Time:
> ========
> I, [2012-03-22T17:31:03.378527 #11412] INFO -- : New Aws::Elb using
> per_thread-connection mode
> I, [2012-03-22T17:31:03.378796 #11412] INFO -- : Describing Load Balancers
> W, [2012-03-22T17:31:03.379458 #11412] WARN -- : Rightscale::HttpConnection
> : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
> I, [2012-03-22T17:31:03.379526 #11412] INFO -- : Opening new HTTPS
> connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> {:health_check=>{:interval=>30, :healthy_threshold=>10,
> :unhealthy_threshold=>2, :target=>"TCP:80", :timeout=>5},
> :availability_zones=>["us-east-1a"], :load_balancer_name=>"ramesh",
> :created=>Thu Mar 22 11:56:20 UTC 2012,
> :dns_name=>"ramesh-647648254.us-east-1.elb.amazonaws.com", :created_time=>Thu
> Mar 22 11:56:20 UTC 2012, :listeners=>[{:protocol=>"HTTP",
> :load_balancer_port=>80, :instance_port=>80}], :name=>"ramesh",
> :instances=>[]}
> I, [2012-03-22T17:31:04.947935 #11412] INFO -- : New Aws::Ec2 using
> per_thread-connection mode
> W, [2012-03-22T17:31:04.948912 #11412] WARN -- : Rightscale::HttpConnection
> : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
> I, [2012-03-22T17:31:04.948998 #11412] INFO -- : Opening new HTTPS
> connection to ec2.us-east-1.amazonaws.com:443
> Second Time:
> ===========
> I, [2012-03-22T17:31:23.494580 #11412] INFO -- : New Aws::Elb using
> per_thread-connection mode
> I, [2012-03-22T17:31:23.494969 #11412] INFO -- : Creating LoadBalancer
> called ramesh
> W, [2012-03-22T17:31:23.496134 #11412] WARN -- : Rightscale::HttpConnection
> : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
> I, [2012-03-22T17:31:23.496251 #11412] INFO -- : Opening new HTTPS
> connection to elasticloadbalancing.us-east-1.amazonaws.com:443
> I, [2012-03-22T17:31:25.104039 #11412] INFO -- : New Aws::Elb using
> per_thread-connection mode
> I, [2012-03-22T17:31:25.108007 #11412] INFO -- : Describing Load Balancers
> {:health_check=>{:interval=>30, :healthy_threshold=>10,
> :unhealthy_threshold=>2, :target=>"TCP:80", :timeout=>5},
> :availability_zones=>["us-east-1a"], :load_balancer_name=>"ramesh",
> :created=>Thu Mar 22 11:56:20 UTC 2012,
> :dns_name=>"ramesh-647648254.us-east-1.elb.amazonaws.com", :created_time=>Thu
> Mar 22 11:56:20 UTC 2012, :listeners=>[{:protocol=>"HTTP",
> :load_balancer_port=>80, :instance_port=>80}], :name=>"ramesh",
> :instances=>[]}
> I, [2012-03-22T17:31:25.400064 #11412] INFO -- : New Aws::Ec2 using
> per_thread-connection mode
> W, [2012-03-22T17:31:25.401058 #11412] WARN -- : Rightscale::HttpConnection
> : request failure count: 1, exception: #<Errno::EPIPE: Broken pipe>
> I, [2012-03-22T17:31:25.401189 #11412] INFO -- : Opening new HTTPS
> connection to ec2.us-east-1.amazonaws.com:443
> /home/rananda/deltacloud/server/lib/deltacloud/server.rb:373: warning:
> Object#id will be deprecated; use Object#object_id
--
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
