-
Notifications
You must be signed in to change notification settings - Fork 341
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
amazon.aws.s3_bucket not working with Storagegrid #542
Comments
Files identified in the description:
If these files are inaccurate, please update the |
Thanks for taking the time to report this issue. This issue was fixed by #154. The version of s3_bucket shipped with Ansible 2.9 is now very out of date and no longer receiving updates. You can use a more recent version of the collection by directly installing the collections: https://docs.ansible.com/ansible/latest/user_guide/collections_using.html |
I already got latest Version installed |
The stacktrace you provided includes:
2.0.0 included a similar but different issue (#508), so if you've installed 2.0.0 and you're getting a different exception, it's possible you're hitting that. |
What you can try is referring to the module by its fully qualified name and using "amazon.aws.s3_bucket" instead of "s3_bucket" or explicitly telling Ansible to give the collection priority by using the collections keyword |
Solves 494: added destructor to ssm connection plugin Reviewed-by: https://github.com/apps/ansible-zuul
Summary
Running this against our StorageGrid doesn't work:
StorageGrid does not have the "Payer Feature" implemented so I guess this is the Problem. But on the other hand the Module has StorageGrid listed as supported
Issue Type
Bug Report
Component Name
s3_bucket
Ansible Version
Collection Versions
AWS SDK versions
Configuration
$ ansible-config dump --only-changed
OS / Environment
CentOS 7
Steps to Reproduce
Expected Results
I would expect it to create a Bucket
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: