Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating buckets via S3 sometimes results in NoSuchBucket errors, and then fails to get deleted on teardown #11344

Open
sagihirshfeld opened this issue Feb 10, 2025 · 1 comment
Assignees
Labels
MCG Multi Cloud Gateway / NooBaa related issues Squad/Red

Comments

@sagihirshfeld
Copy link
Contributor

E           botocore.errorfactory.NoSuchBucket: An error occurred (NoSuchBucket) when calling the PutObject operation: The specified bucket does not exist.
E           AssertionError: s3-bucket-4ccb8adac3d84b328b2872db4c8908 was not deleted within 60 seconds.
  • I couldn't reproduce this manually, but we're seeing this issue rather frequently in regression analysis.
  • This only happens with buckets that were created via S3. Look at the reason that tests fail in test_bucket_policy.py - only test_anonymous_read_only and test_public_website are showing these errors, and these are the only tests that are creating the bucket via S3 and not OC.

Examples:

@sagihirshfeld
Copy link
Contributor Author

Further investigation is required on whether this is due to an automation issue or a product bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MCG Multi Cloud Gateway / NooBaa related issues Squad/Red
Projects
None yet
Development

No branches or pull requests

1 participant