Return-Path: X-Original-To: apmail-deltacloud-dev-archive@www.apache.org Delivered-To: apmail-deltacloud-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 23157E771 for ; Mon, 18 Mar 2013 21:47:16 +0000 (UTC) Received: (qmail 48414 invoked by uid 500); 18 Mar 2013 21:47:15 -0000 Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org Received: (qmail 48403 invoked by uid 500); 18 Mar 2013 21:47:15 -0000 Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@deltacloud.apache.org Delivered-To: mailing list dev@deltacloud.apache.org Received: (qmail 48393 invoked by uid 99); 18 Mar 2013 21:47:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Mar 2013 21:47:15 +0000 Date: Mon, 18 Mar 2013 21:47:15 +0000 (UTC) From: "Ronelle Landy (JIRA)" To: dev@deltacloud.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DTACLOUD-299) Creating a bucket is not working for eucalyptus driver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DTACLOUD-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ronelle Landy updated DTACLOUD-299: ----------------------------------- Priority: Major (was: Blocker) > Creating a bucket is not working for eucalyptus driver > ------------------------------------------------------ > > Key: DTACLOUD-299 > URL: https://issues.apache.org/jira/browse/DTACLOUD-299 > Project: DeltaCloud > Issue Type: Dependency upgrade > Components: Server > Environment: ubuntu, deltacloud > Reporter: Deepika Agrawal > > Hi, > I am trying to create a bucket with eucalyptus driver, and getting the following response: > [2012-08-06T11:19:19.266244 #19432] INFO -- : New Aws::S3Interface using per_thread-connection mode > I, [2012-08-06T11:19:19.630287 #19432] INFO -- : Opening new HTTP connection to delta-bucket1.172.30.54.153:8773 > W, [2012-08-06T11:19:23.738581 #19432] WARN -- : Rightscale::HttpConnection : request failure count: 1, exception: # > I, [2012-08-06T11:19:24.840796 #19432] INFO -- : Opening new HTTP connection to delta-bucket1.172.30.54.153:8773 > W, [2012-08-06T11:19:27.747027 #19432] WARN -- : Rightscale::HttpConnection : request failure count: 2, exception: # > I, [2012-08-06T11:19:30.202140 #19432] INFO -- : Opening new HTTP connection to delta-bucket1.172.30.54.153:8773 > W, [2012-08-06T11:19:33.910874 #19432] WARN -- : Rightscale::HttpConnection : request failure count: 3, exception: # > I, [2012-08-06T11:19:36.215310 #19432] INFO -- : Opening new HTTP connection to delta-bucket1.172.30.54.153:8773 > W, [2012-08-06T11:19:37.819401 #19432] WARN -- : Rightscale::HttpConnection : request failure count: 4, exception: # > W, [2012-08-06T11:19:38.822926 #19432] WARN -- : Rightscale::HttpConnection : re-raising same error: delta-bucket1.172.30.54.153 temporarily unavailable: (getaddrinfo: Name or service not known) -- error count: 4, error age: 1 > Aws::AwsError:delta-bucket1.172.30.54.153 temporarily unavailable: (getaddrinfo: Name or service not known) > /var/lib/gems/1.9.1/gems/http_connection-1.4.1/lib/right_http_connection.rb:332:in `block in request' > /var/lib/gems/1.9.1/gems/http_connection-1.4.1/lib/right_http_connection.rb:322:in `loop' > /var/lib/gems/1.9.1/gems/http_connection-1.4.1/lib/right_http_connection.rb:322:in `request' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:557:in `block in request_info_impl' > /usr/lib/ruby/1.9.1/benchmark.rb:295:in `measure' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/benchmark_fix.rb:30:in `add!' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:557:in `request_info_impl' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:316:in `request_info2' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:338:in `request_info3' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/s3/s3_interface.rb:182:in `request_info' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/s3/s3_interface.rb:217:in `create_bucket' > Deltacloud::ExceptionHandler::ProviderError - delta-bucket1.172.30.54.153 temporarily unavailable: (getaddrinfo: Name or service not known): > /var/lib/gems/1.9.1/gems/http_connection-1.4.1/lib/right_http_connection.rb:332:in `block in request' > /var/lib/gems/1.9.1/gems/http_connection-1.4.1/lib/right_http_connection.rb:322:in `loop' > /var/lib/gems/1.9.1/gems/http_connection-1.4.1/lib/right_http_connection.rb:322:in `request' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:557:in `block in request_info_impl' > /usr/lib/ruby/1.9.1/benchmark.rb:295:in `measure' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/benchmark_fix.rb:30:in `add!' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:557:in `request_info_impl' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:316:in `request_info2' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/awsbase/awsbase.rb:338:in `request_info3' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/s3/s3_interface.rb:182:in `request_info' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/s3/s3_interface.rb:217:in `create_bucket' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/s3/s3.rb:132:in `bucket' > /var/lib/gems/1.9.1/gems/aws-2.5.6/lib/s3/bucket.rb:28:in `create' > /home/deepika/testgit/deltacloud/server/lib/deltacloud/drivers/ec2/ec2_driver.rb:441:in `block in create_bucket' > /home/deepika/testgit/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:173:in `call' > /home/deepika/testgit/deltacloud/server/lib/deltacloud/drivers/exceptions.rb:173:in `safely' > /home/deepika/testgit/deltacloud/server/lib/deltacloud/drivers/ec2/ec2_driver.rb:434:in `create_bucket' > /home/deepika/testgit/deltacloud/server/lib/deltacloud/collections/buckets.rb:94:in `block (3 levels) in ' > /var/lib/gems/1.9.1/gems/sinatra-rabbit-1.0.6/lib/sinatra/rabbit/base.rb:387:in `instance_eval' > /var/lib/gems/1.9.1/gems/sinatra-rabbit-1.0.6/lib/sinatra/rabbit/base.rb:387:in `block in control' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:1212:in `call' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:1212:in `block in compile!' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `[]' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `block (3 levels) in route!' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:801:in `route_eval' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:785:in `block (2 levels) in route!' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:822:in `block in process_route' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:820:in `catch' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:820:in `process_route' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:784:in `block in route!' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:783:in `each' > /var/lib/gems/1.9.1/gems/sinatra-1.3.2/lib/sinatra/base.rb:783:in `route!' > I am getting similar response for describing a bucket in detail also. > I have checked the flow of the request, and figured out that the path and path_to_sign variables are not matching for eucalyptus driver. Also, the server name contains the bucket name which creates a problem. > The request reaches the method fetch_request_params(headers) inside s3_interface.rb (inside aws-2.5.6 gem) where it always satisfies the condition " if is_dns_bucket?(bucket_name) and !@params[:virtual_hosting] " > The "is_dns_bucket" method always returns true for eucalyptus request and false for the ec2 request ( I could not figured out why it happens even if the bucket name for ec2 and euca both are same. ) Therefore, ec2 request does not satisfies the if statement and succeeds while euca request gets inside the if statement where the values of path and server are changed. > I think this is the breaking point where request with euca driver bombs while ec2 driver request succeeds. > Please look into this. > Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira