Open aberkvam opened 1 year ago
@aberkvam Thanks for taking the time to open this issue. I've moved it to the community.aws
collection which is where the aws_ssm
connection plugin lives.
Looking at the output of ansible-galaxy collection list
you've got multiple copies of amazon.aws
and community.aws
installed. If possible, please could you uninstall them and install the latest release (5.3.0
) of both amazon.aws
and community.aws
.
Specifically, I see release 5.0.0
and 1.5.0
of community.aws
, both of which have a number of known issues. There's been some substantial work done on this plugin between releases 5.0.0
and 5.3.0
of community.aws
.
If you still see the issue (or another) after upgrading to release 5.3.0
, please include:
ansible i-00000000000000000 -m ansible.builtin.setup -i inventory/stg/ -vvvvv
(the -vvvvv
is important, there's a lot of output, but it helps us track down what's going on with a connection plugin.)ansible-galaxy collection list
again (to confirm the version that's installed)I am hitting an unrelated issue when I upgrade community.aws past 3.4.0. For the moment, all I can do it confirm the issue still occurs with community.aws 3.4.0 and amazon.aws 5.3.0. I will work on resolving my unrelated issue and report back here when I can test with the latest community.aws.
Summary
There was a "stealth" release of session-manager-plugin 1.2.458.0 today.
https://github.com/aws/session-manager-plugin/issues/64
Upgrading to session-manager-plugin 1.2.458.0 causes a 'TypeError: can only concatenate str (not "bytes") to str' error when connecting to EC2 instances.
Reverting to session-plugin-manager 1.2.398.0 fixes the error
Issue Type
Bug Report
Component Name
aws_ec2
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
No response
Steps to Reproduce
Expected Results
Actual Results
Code of Conduct