-
Notifications
You must be signed in to change notification settings - Fork 340
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
ec2_instance fails to check TagSpecification for None #1148
Comments
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
needs_triage
plugins
plugin (any type)
python3
traceback
labels
Oct 10, 2022
Thanks for taking the time to open this issue. I'm surprised this only just popped up. The issue was introduced by #548 and released in 2.1.0, almost a year ago! |
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Oct 11, 2022
…n if None (#1151) ec2_instance - update build_run_instance_spec to skip TagSpecification if None SUMMARY fixes: #1148 When no tags are supplied, build_run_instance_spec currently includes 'TagSpecification': None. This results in botocore throwing an exception. Also renames instance_role to iam_instance_profile (keeping the original as an alias). While this could be split off, I'll just perform a partial backport for the bugfix when backporting to 4.x, while working through some unit tests the inaccuracy of the parameter name was apparent. ISSUE TYPE Bugfix Pull Request COMPONENT NAME plugins/modules/ec2_instance.py ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None> Reviewed-by: Gonéri Le Bouder <goneri@lebouder.net>
patchback bot
pushed a commit
that referenced
this issue
Oct 12, 2022
…n if None (#1151) ec2_instance - update build_run_instance_spec to skip TagSpecification if None SUMMARY fixes: #1148 When no tags are supplied, build_run_instance_spec currently includes 'TagSpecification': None. This results in botocore throwing an exception. Also renames instance_role to iam_instance_profile (keeping the original as an alias). While this could be split off, I'll just perform a partial backport for the bugfix when backporting to 4.x, while working through some unit tests the inaccuracy of the parameter name was apparent. ISSUE TYPE Bugfix Pull Request COMPONENT NAME plugins/modules/ec2_instance.py ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None> Reviewed-by: Gonéri Le Bouder <goneri@lebouder.net> (cherry picked from commit a9ad180)
tremble
added a commit
to tremble/amazon.aws
that referenced
this issue
Oct 12, 2022
…n if None (ansible-collections#1151) ec2_instance - update build_run_instance_spec to skip TagSpecification if None SUMMARY fixes: ansible-collections#1148 When no tags are supplied, build_run_instance_spec currently includes 'TagSpecification': None. This results in botocore throwing an exception. Also renames instance_role to iam_instance_profile (keeping the original as an alias). While this could be split off, I'll just perform a partial backport for the bugfix when backporting to 4.x, while working through some unit tests the inaccuracy of the parameter name was apparent. ISSUE TYPE Bugfix Pull Request COMPONENT NAME plugins/modules/ec2_instance.py ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis <None> Reviewed-by: Gonéri Le Bouder <goneri@lebouder.net>
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Oct 13, 2022
…n if None (#1151) (#1160) [PR #1151/a9ad1808 backport][stable-5] ec2_instance - update build_run_instance_spec to skip TagSpecification if None This is a backport of PR #1151 as merged into main (a9ad180). SUMMARY fixes: #1148 When no tags are supplied, build_run_instance_spec currently includes 'TagSpecification': None. This results in botocore throwing an exception. Also renames instance_role to iam_instance_profile (keeping the original as an alias). While this could be split off, I'll just perform a partial backport for the bugfix when backporting to 4.x, while working through some unit tests the inaccuracy of the parameter name was apparent. ISSUE TYPE Bugfix Pull Request COMPONENT NAME plugins/modules/ec2_instance.py ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None>
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
When I try to launch an ec2 instance using
amazon.aws.ec2_instance
from collection version 3.4.0 through 5.0.0 inclusive it fails botocore validation withThis actually isn't directly my bug, I found it while triaging a StackOverflow question
The work-around appears to be to explicitly add
tags: {}
to the task parameters, but the DX is terrible if one does not know to do thatIssue Type
Bug Report
Component Name
ec2_instance
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
macOS 12.6
Steps to Reproduce
Expected Results
I expected an instance to launch
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: