-
Notifications
You must be signed in to change notification settings - Fork 342
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
s3_object: NoSuchTagSet when s3 endpoint does not support tags #1607
Comments
alinabuzachis
added
needs_verified
Some one might want to take a look at this and reproduce it to confirm
jira
and removed
needs_triage
labels
Jun 13, 2023
Files identified in the description:
If these files are inaccurate, please update the |
ansibullbot
added
bug
This issue/PR relates to a bug
module
module
python3
traceback
labels
Jul 12, 2023
bingopriya
added a commit
to bingopriya/amazon.aws
that referenced
this issue
Jul 27, 2023
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Oct 19, 2023
…ags (#1813) s3_object - fix NoSuchTagSet error when S3 endpoint doesn't support tags SUMMARY is_boto3_error_code only supports being passed a string or list. In the refactor of s3_object it was passed a tuple, so the errors weren't being cleanly caught. ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_object ADDITIONAL INFORMATION fixes: #1607 Reviewed-by: Alina Buzachis
patchback bot
pushed a commit
that referenced
this issue
Oct 19, 2023
…ags (#1813) s3_object - fix NoSuchTagSet error when S3 endpoint doesn't support tags SUMMARY is_boto3_error_code only supports being passed a string or list. In the refactor of s3_object it was passed a tuple, so the errors weren't being cleanly caught. ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_object ADDITIONAL INFORMATION fixes: #1607 Reviewed-by: Alina Buzachis (cherry picked from commit 985d8b1)
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Oct 20, 2023
…ags (#1813) (#1814) [PR #1813/985d8b1c backport][stable-6] s3_object - fix NoSuchTagSet error when S3 endpoint doesn't support tags This is a backport of PR #1813 as merged into main (985d8b1). SUMMARY is_boto3_error_code only supports being passed a string or list. In the refactor of s3_object it was passed a tuple, so the errors weren't being cleanly caught. ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_object ADDITIONAL INFORMATION fixes: #1607 Reviewed-by: Mark Chappell
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this issue
Oct 24, 2023
Update contributing to sync with amazon.aws Fixes: ansible-collections#1607 SUMMARY Update CONTRIBUTING.md to sync with amazon.aws and pick up various recent improvements (See also ansible-collections#924) ISSUE TYPE Docs Pull Request COMPONENT NAME CONTRIBUTING.md ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
As of Amazon AWS collection v6, the s3_object module fails with
NoSuchTagSet
when putting an object to an S3 endpoint that does not support object tagging. If I revert to 5.5.0, the same task works without error. Both 6.0.x and 6.1 exhibit the error. The reproduction task below works if I remove the Wasabi endpoint and run against AWS.Issue Type
Bug Report
Component Name
s3_object
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
MacOS Ventura 13.4
Steps to Reproduce
Note that I changed the profile & bucket names for privacy.
Expected Results
I expected the object to be uploaded to the bucket.
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: