Consider increasing the reboot timeouts in the Ansible playbooks

[nathandyer]

Description

We currently have a timeout specified for two minutes, where if a server has not rebooted and reestablished a connection within that window, the Ansible task will fail. Because of variations in hardware and other installation-specific concerns, there are times when the two minute timeout is not sufficient and the task will fail prematurely.

To account for these variations in boot times and hardware speeds, it might be worth increasing the timeout (to three minutes, or even longer, depending on what folks think is reasonable).

[rabuchaim]

In the install_files/ansible-base/ansible.cfg file you can increase the timeout before starting the playbook.

interpreter_python=auto
#ask_pass=False
#ask_sudo_pass=False
display_skipped_hosts=False
timeout=120
# Use dynamic inventory script to determine local IPv4 addresses
# from site-specific vars, or Onion URLs for SSH over ATHS.
inventory=inventory-dynamic

[privilege_escalation]
agnostic_become_prompt=False

[ssh_connection]
scp_if_ssh=True
ssh_args = -o ControlMaster=auto -o ControlPersist=1200 -o ServerAliveInterval=10 -o ServerAliveCountMax=3
pipelining=True