Open markussiebert opened 2 years ago
Files identified in the description: None
If these files are inaccurate, please update the component name
section of the description or use the !component
bot command.
With release 5.2.0 there were a significant number of fixes for the aws_ssm connection plugin. If possible please could you retry and see if they've fixed the issues you were seeing.
Summary
I see errors, when using ansible.windows.win_command / win_shell with the ssm connection plugin.
It seems, as if the win_command is executed in end endless loop while win_shell runs at least twice (I use it to execute a ps1 script)
The shellscript I run with win_shell or win_command extracts a zip file placed in the same directory as the ps1 script, works on the data and deletes it afterwards.
I get the error message, the there is no zip file next to the ps1 script (error is written by the script)
but looking on the instance while the win_shell / win_command is executed, I can see that the zipfile is executed and there are successfull runs (but even others). The win_shell / win_command never finishes.
I don't get the error when using winrm connection
Maybe it has something to do with the
export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
I have to do in order to make the ssm plugin running?
Issue Type
Bug Report
Component Name
ssm connect plugin
Ansible Version
Collection Versions
AWS SDK versions
Configuration
OS / Environment
Target Win Server 2019,
Executed on Mac
Steps to Reproduce
Expected Results
win_shell shoud run like it does with winrm
Actual Results
Code of Conduct