On Wed, 15 Oct 2014 21:01:55 -0400 Todd Zullinger <[email protected]> wrote:
> With pipelining = True commented out on el6, things still fail for me
> on the first run. They do fail with a different error, but perhaps
> that's just due to slightly different code paths with pipelining on
> and off, I haven't looked at the ansible code at all.
>
> In case it matters, I adjusted the control_path variable to avoid
> using ~/.ansible since $HOME is on NFS in my environment.
>
> With pipelining disabled:
>
> $ ansible web -m ping -o
> ...
> web12 | FAILED => failed to resolve remote temporary directory
> from /var/tmp/ansible-tmp-1413420275.15-6744099385111: `mkdir
> -p /var/tmp/ansible-tmp-1413420275.15-6744099385111 && chmod
> a+rx /var/tmp/ansible-tmp-1413420275.15-6744099385111 &&
> echo /var/tmp/ansible-tmp-1413420275.15-6744099385111` returned empty
> string
>
> With pipelining enabled:
>
> $ ansible web -m ping -o
> ...
> web12 | FAILED >> {"failed": true, "msg": "", "parsed": false}
>
> This is still using openssh-5.3p1-100.el6.x86_64 which was a scratch
> build that Petr made per RHBZ #953088. I have not checked whether
> there are any differences in the -104 packages included in the latest
> RHEL updates (and they haven't made it to my CentOS mirror yet).
>
> This is also with ansible-1.6.10-1.el6 from EPEL. I have not yet
> updated to 1.7.x (I see 1.7.2-1 is in epel-testing now, so I'll
> prbably wait for that to hit stable).
ansible-1.7.2-1.el6.noarch
openssh-5.3p1-104.el6.x86_64
with pipeline disabled:
% ansible -m ping -o junk02\*
junk02.phx2.fedoraproject.org | success >> {"changed": false, "ping": "pong"}
with pipeline enabled:
% ansible -m ping -o junk02\*
junk02.phx2.fedoraproject.org | FAILED >> {"failed": true, "msg": "", "parsed":
false}
kevin
signature.asc
Description: PGP signature
