A generic retry would be phenomenal. Right now on the openshift side, we've found success with this config:
# config file for ansible -- http://ansible.com/ # ============================================== [defaults] forks = NNN host_key_checking = False remote_user = root roles_path = roles/ gathering = smart fact_caching = jsonfile fact_caching_connection = $HOME/ansible/facts fact_caching_timeout = 600 log_path = $HOME/ansible.log nocows = 1 callback_whitelist = profile_tasks [privilege_escalation] become = True [ssh_connection] ssh_args = -o ControlMaster=auto -o ControlPersist=600s control_path = %(directory)s/%%h-%%r pipelining = True timeout = 10 We give the ansible host as much memory as we possibly can (often 64G or so) for very large deployments where we want a lot of parallelism. On Wed, Aug 3, 2016 at 11:58 AM, Ryan Groten <[email protected]> wrote: > I've had moderate success by changing the ControlPersist in ssh_args > parameter in ansible.cfg: > > ssh_args = -o ControlMaster=auto -o ControlPersist=300s > > That said, on big playbooks with a couple hundred hosts/tasks I generally > still have at least one or two generic connection failures. Like you it > happens on different tasks/hosts every time for me. > > > On Friday, 29 July 2016 10:49:17 UTC-6, Jeff Richards wrote: >> >> Hi, >> >> Is there any way, in Ansible 1.9.6, of having Ansible retry a failed >> connection attempt x times at y intervals? We are seeing flaky network >> behavior when deploying on AWS, with apparently random ssh failures causing >> runs to break. >> >> It's never in the same place twice so it would be nice if we could have >> Ansible back off and retry before bailing. >> >> If not in 1.9.6 (which we're stuck on for another few months .. >> .OpenShift reasons), how about 2.x? >> >> Jeff >> > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/5901060b-8862-4531-9260-5f414e4d9199%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/5901060b-8862-4531-9260-5f414e4d9199%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- -- Jeremy Eder -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CABxNGQbDSL8%2BovrKvYbyMJ_Simak2QWcNVA2_emKTxfcvxi2rQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
