Matt Martz
Matt Martz
The workaround is to downgrade to an older paramiko. As of now, there is no active work being done to add a work around in the paramiko plugin. Assuming that...
> Is there a plan to push workaround for this (limit paramiko version), until paramiko ssh logic itself is rewritten? We do not have a hard dependency on paramiko in...
Did you encounter some issue that resulted in this PR? forks shouldn't be doing anything with stdout or stderr, and if plugins are, they likely need to be fixed. As...
Assuming we do accept this for devel, it is not directly backportable to older versions since `Display` only got a lock as part of devel/2.14. To clarify my comment about...
`version_added` test is failing, and that is expected, since we'll backport this to 2.14.
Please run your playbook with at least `-vvv` and provide the full output. Feel free to restrict to just a single host and a single task that replicates the behavior....
Relevant Logs... ``` Attempting python interpreter discovery 9394 1652948516.40136: _low_level_execute_command(): starting 9394 1652948516.40143: _low_level_execute_command(): executing: /bin/sh -c 'echo PLATFORM; uname; echo FOUND; command -v '"'"'python3.10'"'"'; command -v '"'"'python3.9'"'"'; command -v...
Ok, after a whole lot of testing, I've been able to verify this. It only happens if the distro is not listed in `INTERPRETER_PYTHON_DISTRO_MAP` (regardless of version, the distro key...
I believe this issue is actually a duplicate of https://github.com/ansible/ansible/issues/47023
!component =lib/ansible/executor/task_executor.py