When running win_shell module in our playbooks with async or become, we are
sometimes left with ansible exec_wrapper and a child conhost process that
won't return and keeps eating resources on the node. Since we are using
ansible through ZUUL to run Continuous Integration, we quickly fill up
workers with hanging wrappers, leaving them with 100% Processor utilization.
Anyone seen this and have any hints on what to do?
Ansible 2.9
The decoded commandline of the hanging process:
&chcp.com 65001 > $null
$exec_wrapper_str = [System.Console]::In.ReadToEnd()
$split_parts = $exec_wrapper_str.Split(@("`0`0`0`0"), 2,
[StringSplitOptions]::RemoveEmptyEntries)
Set-Variable -Name json_raw -Value $split_parts[1]
$exec_wrapper = [ScriptBlock]::Create($split_parts[0])
&$exec_wrapper
Running over winrm with certificates to both windows7 and
windows-server-2019 machines
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/c8bdbd48-48ba-4265-8818-d1f2fa9065f4n%40googlegroups.com.
