I've created a basic Ansible play that simply copies new binaries out to the ASAs we manage. However, as you can imagine many of the lower bandwidth WAN connected sites take a bit longer for the copy operations to complete. These are hitting regulatory required SSH timeout values configured on the ASA (validated with debug ssh enabled) on the Ansible control connection despite setting a ServerAliveInterval and OpenSSH reaching out to verify the server is still there. Ansible machine is sending SSH packet type 80 and ASA is responding with SSH packet type 82, however this is not preventing an idle timeout. Once the connection is deleted via timeout, the socket is removed and the play fails.
This behavior is not experienced in a normal client connection, presumably because the stdout ! feedback is collected and displayed to the user? - just a guess here.
How can I execute long running plays without compromising my regulatory required timeout values?
Thanks.
