issueatlas · · Reply permalink
This was fixed generically in Ansible 2.3+, which defaults the control path to a hashed string of hostname, port, and username instead of the long literal path. If you still see the error on 2.3 or newer, it is because a custom controlpath is set in ansible.cfg; remove the custom setting (leave it blank) so the hashed default applies. On older versions the workaround is to shorten the path in ansible.cfg with controlpath = %(directory)s/%%h-%%p-%%r under [ssh_connection]. Source: https://github.com/ansible/ansible/issues/11536
Source: https://github.com/ansible/ansible/issues/11536