Matt Martz
Matt Martz
I've verified this behavior. ``` TASK [setup] ******************************************************************************** ok: [ubu14] TASK [debug] ******************************************************************************** ok: [ubu14] => { "ansible_facts.service_mgr": "upstart" } TASK [command] ****************************************************************************** changed: [ubu14] => {"changed": true, "cmd": ["apt-get",...
I've attempted to reproduce this over the course of the day, using specifically the reproducers in: * https://github.com/ansible/ansible/issues/33058#issuecomment-352395300 * https://github.com/ansible/ansible/issues/33058#issuecomment-846581347 Plus some random `.tar`, `.tar.gz`, and `.tgz` files that I...
fwiw, it looks like for the `ansible.netcommon.libssh` connection plugin to work, would also require `ansible.netcommon` 3.1.1 or newer based on this commit https://github.com/ansible-collections/ansible.netcommon/commit/130c49ea32afea5807e2c733599a3e6a4da8baaa `ansible==6.3.0` includes `ansible.netcommon==3.1.0` I'm unsure of the...
After spending several hours on this for a related issue, I can confirm that `2.14.0.dev0` and `ansible.netcommon==3.1.1` do indeed pass the variables to configure paramiko correctly. However, the reason `ansible_ssh_common_args`...
The pull request listed above addresses this. It adds those ssh arg variables back, though listed as deprecated. It also adds a variable for the `proxy_command` config. The deprecations and...
This commit https://github.com/ansible/ansible/pull/78613/commits/03654a2a499b34c385efafeb3379db4c16101c38 effectively disabled the tests.
> * in [handler notified multiple times when using include_role #73643](https://github.com/ansible/ansible/issues/73643) the handler is called 4 times as opposed to twice as in `devel`, which I think is expected that...
Your patch breaks other behavior, so it's not the correct change in any case. It breaks the output of the linear strategy with this reproducer: ``` . ├── 40317.yml │...
Can you clarify what you experience errantly happening with that reproducer? I ran it, and it completed, but not exactly positive what in the output should be considered an issue.