I can confirm that switching to paramiko appears to solve the problem in my case. This seems like a bit of a shame openssh is the recommended way to go (more features).
On Mon, Jun 8, 2015 at 8:05 PM, Shay Rojansky <[email protected]> wrote: > I was just looking into that, is that a reliable workaround? > > Will try soon and report the results. > > On Mon, Jun 8, 2015 at 8:02 PM, Brian Coca <[email protected]> wrote: > >> have you tried switching to paramiko as your connection? >> >> On Mon, Jun 8, 2015 at 1:00 PM, Shay Rojansky <[email protected]> wrote: >> > I have this issue as well: running a play which delegates some action >> to the >> > same host pretty consistently fails with the above error. Findings are >> > exactly the same as below, including the -f 1 behavior. >> > >> > Any ideas on workarounds? >> > >> > >> > On Friday, May 29, 2015 at 3:36:33 PM UTC+3, Christian Rusa wrote: >> >> >> >> I can confirm this problem. >> >> >> >> In my case it is a playbook which creates a configuration file for the >> >> server on the backupserver. >> >> >> >> If I run this playbook against 1 host it works. >> >> If I run it against a group of hosts it fails. >> >> If I run it against a group of host using -f 1 as parameter it works. >> >> >> >> Error is always the SSH Error: Shared connection to xxxxx closed. >> >> >> >> Ansible version is 1.9-0.git201503262158~unstable >> >> >> >> >> >> >> >> >> >> On Monday, May 11, 2015 at 4:47:14 PM UTC+2, Cory Wagner wrote: >> >>> >> >>> I didn't try with serial, but I have not had an issue when running the >> >>> same playbook against one or two delegates. >> >>> >> >>> On Thursday, April 30, 2015 at 9:35:57 AM UTC-5, Brian Coca wrote: >> >>>> >> >>>> this sounds like a probably race condition with the per host forks >> >>>> interfering with each other, try setting serial: 1 to confirm. >> >>>> >> >>>> >> >>>> >> >>>> -- >> >>>> Brian Coca >> > >> > -- >> > 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/e459b939-0395-4d33-acc9-224ee29f0fe9%40googlegroups.com >> . >> > >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> Brian Coca >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Ansible Project" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/ansible-project/wMRlm3JtDeo/unsubscribe >> . >> To unsubscribe from this group and all its topics, 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/CAJ5XC8k9R6zc6B6nRK8pHFdDiFHUJ7_BnR_BhFpv%3D376csn%3Dyw%40mail.gmail.com >> . >> 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 [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/CADT4RqAYdqmv633nCYs4%3DMc_feHPz%2B43cs4xtBikPqnRqPNOjA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
