[EXTDAM-82] (Test only) S3: Error after creating new bucket Created: 26/Feb/20  Updated: 18/Mar/20  Resolved: 10/Mar/20

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Jesus Alonso Assignee: Yen Lac Tue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.5h
Original Estimate: Not Specified

Issue Links:
dependency
depends upon EXTDAM-46 S3: performance improvements Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: DAMs backend
Sprint: Add-Ons 33
Story Points: 1

 Description   

In occasions, a NoSuchBucketException appears right after creating a bucket and the bucket does not appear in the tree.

The reason is that S3 is eventually consistent and while the bucket has been successfully created in region A, it is not yet created in the default region where we obtain the regions for buckets.

This will be fixed adding a map of buckets-region.



 Comments   
Comment by Jesus Alonso [ 02/Mar/20 ]

This is fixed in EXTDAM-46

Generated at Mon Feb 12 01:51:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.