[HASSETS-9] S3 App: Unique Name Error Created: 03/Sep/20  Updated: 17/Jan/24  Resolved: 17/Jan/24

Status: Closed
Project: Hybrid Assets
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: Bug Priority: Major
Reporter: Thomas Comiotto Assignee: Andrew Warinner
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File bucket.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:

 Description   

Creating a new bucket in the S3 app sometimes fails with a "Unique Name Error" - without obvious reason.

Steps to reproduce:

  1. Open S3 app (connected to SwitchEngines)
  2. Create a bucket named "test"
  3. You get the error: The bucket name you choose must be unique across all existing bucket names in amazon S3


 Comments   
Comment by Andrew Warinner [ 17/Sep/20 ]

This is probably a limitation of the AWS API: bucket names in S3 must be globally unique since S3 is a "regionless" service.

Investigate whether this is being enforced by the AWS S3 libraries or by Ceph. 

Possible adjustments: 

  • Better error message
Comment by Lars Fischer [ 16/Jan/24 ]

Tested with 1.1.5 and an appropriate error message is displayed:

Generated at Mon Feb 12 02:07:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.