From 4a4467ab347daf35ddbc505d8e4dde10310aaafc Mon Sep 17 00:00:00 2001 From: Will Szumski Date: Mon, 24 Jun 2024 13:07:38 +0100 Subject: [PATCH] Add workaround for rc: -13 I've commonly hit this when configuring prometheus: ``` TASK [prometheus : Get container facts] ************************************************************************************************************************************* Monday 24 June 2024 11:09:37 +0000 (0:00:08.528) 0:01:31.707 *********** fatal: [will-compute-01]: FAILED! => changed=false module_stderr: '' module_stdout: '' msg: |- MODULE FAILURE See stdout/stderr for the exact error rc: -13 fatal: [will-compute-02]: FAILED! => changed=false module_stderr: '' module_stdout: '' msg: |- MODULE FAILURE See stdout/stderr for the exact error rc: -13 ``` The ControlPersist workaround is documented in these bug reports: - https://github.com/ansible/ansible/issues/78344 - https://github.com/ansible/ansible/issues/81777 From the comments, It seems like this does not completely resolve the issue, but does decrease the frequency that you hit this. The Prometheus tasks seem particuarly susceptible as they run on every host. --- etc/kayobe/ansible.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/etc/kayobe/ansible.cfg b/etc/kayobe/ansible.cfg index b38cb8239..e6c3e9c12 100644 --- a/etc/kayobe/ansible.cfg +++ b/etc/kayobe/ansible.cfg @@ -17,3 +17,4 @@ any_unparsed_is_failed = True [ssh_connection] pipelining = True +ssh_extra_args = -o ControlPersist=1h