ansible.builtin.win_ping: Default Windows temp directory resolution broken with 2.19

TL;DR

Add Ansible's bootstrap wrapper file to the AV internal exclusion list.

Steps

1. Issue ansible/ansible#85864 (closed, 21 comments): ### Summary When we update from ansible-core 2.18.9 to 2.19.2 the win_ping module breaks because it does not seem to correctly resolve the Windows temporary directory (see logs) and therefore the payload cannot be copied to the remote server. ### Issue Type Bug Report ### Component Name pip ### Ansible Version ```console $ ansible --version ansible [core 2.19.2] config file = None configured module search path = ['[HOME]/...', '/usr/share/ansible/plugins/modules'] ansible python module location = [HOME]/...
2. Default Windows temp directory resolution broken with ansible 2.19: the root cause is antivirus (McAfee/Trellix Endpoint Security) killing the bootstrap wrapper mid-run. Add Ansible's bootstrap wrapper file to the AV internal exclusion list. To debug, copy the ansible-local-* temp dir off the host while the task runs, or set ANSIBLEKEEPREMOTE_FILES=1. Note a separate report traced to the AWS SSM connection plugin, which is not Ansible-supported, so take those to the plugin maintainers.

When to use

You are seeing this: Note a separate report traced to the AWS SSM connection plugin, which is not Ansible-supported, so take those to the plugin maintainers. Use this skill when you run into "ansible.builtin.win_ping: Default Windows temp directory resolution broken with 2.19".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: ansible-core 2.18.9, 2.19.2. If you are on something much newer or older, the details may have shifted.

Why this happens

Issue ansible/ansible#85864 (closed, 21 comments): ### Summary When we update from ansible-core 2.18.9 to 2.19.2 the win_ping module breaks because it does not seem to correctly resolve the Windows temporary directory (see logs) and therefore the payload cannot be copied to the remote server. ###

Edge cases

• Note a separate report traced to the AWS SSM connection plugin, which is not Ansible-supported, so take those to the plugin maintainers.

In the GitHub issue gh:ansible/ansible#85864 (https://github.com/ansible/ansible/issues/85864), the problem reported was: Issue ansible/ansible#85864 (closed, 21 comments): ### Summary When we update from ansible-core 2.18.9 to 2.19.2 the winping module breaks because it does not seem to correctly resolve the Windows temporary directory (see logs) and therefore the payload cannot be copied to the remote server. ### Issue Type Bug Report ### Component Name pip ### Ansible Version ```console $ ansible --version ansible [core 2.19.2] config file = None configured module search path = ['[HOME]/...', '/usr/share/ansible/plugins/modules'] ansible python module location = [HOME]/... The verified resolution was: Default Windows temp directory resolution broken with ansible 2.19: the root cause is antivirus (McAfee/Trellix Endpoint Security) killing the bootstrap wrapper mid-run. Add Ansible's bootstrap wrapper file to the AV internal exclusion list. To debug, copy the ansible-local-* temp dir off the host while the task runs, or set ANSIBLEKEEPREMOTEFILES=1. Note a separate report traced to the AWS SSM connection plugin, which is not Ansible-supported, so take those to the plugin maintainers.