Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@deltacloud.apache.org
Date: Tue, 14 Aug 2012 01:10:38 +1100 (NCT)
From: "Marios Andreou (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: <883846147.1812.1344867038246.JavaMail.jiratomcat@arcas>
In-Reply-To: <233503957.1782.1344866679222.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (DTACLOUD-300) creating an new bucket from
 us-east1 and accessing it from different locations like us-west1 throws bad
 uri error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Marios Andreou updated DTACLOUD-300:
------------------------------------

    Attachment: 0001-Fixes-DTACLOUD_300-ProviderError-bad-URI-accessing-u.patch

should resolve issue please test
                
> creating an new bucket from us-east1 and accessing it from different locations like us-west1 throws bad uri error
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-300
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-300
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Client (Ruby), Native/Frontend
>         Environment: OS- Fedora 16, 17, RHEL6.x
> commit - 4ca9433f7f5c0239d6b6eda6cc239d18e66b2a3c
>            Reporter: Ramesh A
>            Assignee: Marios Andreou
>         Attachments: 0001-Fixes-DTACLOUD_300-ProviderError-bad-URI-accessing-u.patch, Bad-URI.png
>
>
> Reproduction steps;
> ================
> 1. Create a new bucket in us-east-1
> 2. change the provider to different location say, us-west-1 and try to access the above created bucket
> Result:
> =====
> Throws "Deltacloud::ExceptionHandler::ProviderError - bad URI(is not URI?):" 

--
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