I ran into similar issues using the new ControlPersist option as well as the ProxyCommand option. A Red Hat bugzilla <https://bugzilla.redhat.com/show_bug.cgi?id=1160487> was created that has the details. I think the part in comment 1 <https://bugzilla.redhat.com/show_bug.cgi?id=1160487#c1> starting at "The commands and output below show that ControlPersist=yes does not work as expected." is what you are referring to. There is a patch for openssh-5.3p1-104.el6.src.rpm attached to the bug that is from me backporting code from the RHEL 7 openssh related to the ControlPersist option. I don't run Ansible, so I have no way of testing to see if the patch fixes your issue. However, I would be interested to know if it does.
-- Py On Wednesday, October 15, 2014 7:57:39 AM UTC-7, Dag Wieers wrote: > > Hi, > > As some of you may know, Red Hat backported the ControlPersist > functionality to the OpenSSH version that ships with RHEL6. > > This is terrific since RHEL users can now use this technique to speed up > Ansible. > > However, after some testing it seems to fail for the very first > connection. What happens is that the first connection, when the persistent > connection has not been set up yet, fails. Any subsequent connection seems > to work fine, but obviously this fails to work properly with Ansible. > > I think this is a bug, has anyone tested this ? > Or am I doing something wrong here ? > > -- > Dag > -- 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/6c530cd9-26ff-4adc-a3ef-282f2ecc7ba8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
