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:

- ansible/ansible#78344
- ansible/ansible#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.

(cherry picked from commit 699769c)

yoga: Backport Add workaround for rc: -13 (#1108)