Hmm.... We run a lot of EC2 plays from our integration tests -- originating *not* in EC2 and running almost constantly, and don't really see this -- some other providers, yes. I'd be curious if others do.
You can definitely consider running the Ansible control machine *inside* EC2, where connections will be more reliable (and also faster), which is something I usually recommend to folks. Another thing is when spinning up new instances, using the "wait_for" trick, be sure to put a sleep in after the wait_for. SSH ports can come up but not be quite ready, which gives the appearance of SSH failure. I'm wondering if that might be part of it, or if you're seeing connection issues at effectively random points or just those. On Fri, Sep 12, 2014 at 11:04 AM, Gregory Taylor <snagglepa...@gmail.com> wrote: > We use Ansible to deploy code updates across a small fleet (~8 machines). > At least a few times a week, we run into network hiccups that cause the SSH > connection to a random EC2 instance to fail, causing the entire playbook > run to fail. Sometimes this happens such that we are left with an > incomplete deploy, which is no fun. In almost all cases we can immediately > re-launch the playbook and the errant instance is fine the second time > around. These appear to be very short interruptions, and there's no rhyme > or reason as to which instance it effects. It's usually only one instance > out of our fleet at a time (though there's no pattern as to which has > connectivity issues). > > What kind of strategies is everyone using to deal with these sort of > sporadic SSH failures that cause the whole playbook run to fail prematurely? > > -- > 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 ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/c91a5b9d-3cf3-4efe-93ac-17c7e7f107e8%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/c91a5b9d-3cf3-4efe-93ac-17c7e7f107e8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgxN57onwuK3u81J%3D-6WZeEMYOfbmbThnZtvYPDy%3Djf0NQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
