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

Marios Andreou updated DTACLOUD-196:
------------------------------------

    Attachment:     (was: 
0001-Fix-for-DTACLOUD_196.-This-forces-use-of-the-DEFAULT.patch)
    
> Deltacloud API displays buckets/blobs belonging to different 
> locations(endpoints)
> ---------------------------------------------------------------------------------
>
>                 Key: DTACLOUD-196
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-196
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Client (Ruby), Server
>         Environment: Deltacloud API 0.5.0
> OS - Fedora 15, 16, RHEL, 6.1
> Setup - EC2
> commit - c13da7b50bbbbdc529b42207f58dbe5099006ad1
>            Reporter: Ramesh A
>            Assignee: Ramesh A
>         Attachments: 
> 0001-Fix-for-JIRA-DTACLOUD_196-Use-correct-endpoint.patch, 
> Error-southeast.png, Error-useast1.png, ap-southeast-1-console-log.txt, 
> us-east-1-console-log.txt
>
>
> Deltacloud API displays buckets/blobs belonging to different 
> locations(endpoints)
> Reproduction Steps:
> ==============
> 1. Change the provider account from default to say ap-northeast-1
> 2. Click on Buckets and create a bucket by providing the location as 
> ap-northeast-1 (i.e, endpoint)
> 3. Click on the created bucket and click on create blob
> 4. Enter the below mentioned blob details and create the blob
>      Blob Name:  Ramesh-Test-Blob
>      Blob Data:  2.txt (empty file uploaded from the home directory)
>      Metadata Key: rananda   
>      Metadata Value:  2
> Scenario - 1: ( for any other providers other than us-east-1)
> ==========
> a. Now change the   provider to say ap-southeast-1.
> b. Click on the buckets
> Expected Result:
> =============
> 1. Should not display bucket which are created in the other providers or 
> endpoints(but displays in this case)
> 2. Click on the bucket 
> Actual Results:
> ============
> 1. Displays buckets belonging to different endpoints
> 2. Clicking on the bucket name throws error stating 
> "Deltacloud::ExceptionHandler::ProviderError - bad URI(is not URI?):"
> Refer "Error-southeast.png" and "ap-southeast-1-console-log.txt" for further 
> information
> Scenario - 2: (for us-east-1 provider)
> ===========
> a. Now change the   provider to say us-east-1
> b. Click on the buckets.
> Expected Result:
> =============
> 1. Should not display bucket which are created in the other providers or 
> endpoints(but displays in this case)
> 2. Click on the bucket.
> 3. Click on the blobs link which was created above
> Actual Results:
> ============
> 1. Displays buckets belonging to different endpoints
> 2. Clicking on the bucket displays the bucket details and also show the 
> attached blob to this bucket
> 3. Clicking on the blob link throws error stating 
> "Deltacloud::ExceptionHandler::ProviderError - NilClass is not a valid input 
> stream. It must walk like either a String, an IO, or a Source."
> Refer "Error-useast1.png" and "us-east-1-console-log.txt" for further details

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