When I saw this discussion thread, I was thrilled because I am using
OEL6.5 with OpenSSH-5.3. Since that is equivalent to RHEL6.5, that meant
that there should be an update to OpenSSH for OEL too. Sure enough, there
is (openssh-5.3p1-104.el6.x86_64). But when I installed it, I could no
longer use Ansible to copy files to other servers. I did not make any
other changes (ssh_args, scp_if_ssh, control_path, and pipelining are all
still commented out), and my ssh_config does not include any of the
"Control*" parameters. Output from my quick tests are below:
Without "scp_if_ssh":
sinudy36-> ansible sinudm07 -m copy -a "src=testfile dest=/var/tmp"
sinudm07 | FAILED >> {
"failed": true,
"md5sum": "d41d8cd98f00b204e9800998ecf8427e",
"msg": "\u001b]2;pdxmft @ :/home/pdxmft\u0007/usr/bin/python: can't
open file '\u001b]2': [Errno 2] No such file or directory\r\n/bin/sh:
pdxmft: command not found\r\n",
"parsed": false
}
With "scp_if_ssh":
sinudy36-> ansible sinudm07 -m copy -a "src=testfile dest=/var/tmp"
sinudm07 | FAILED => failed to transfer file to
/home/pdxmft/.ansible/tmp/ansible-tmp-1414615053.51-185971585352740/source:
scp:
/home/pdxmft/.ansible/tmp/ansible-tmp-1414615053.51-185971585352740/source:
No such file or directory
This is identical to what I observed when I tried to specify ssh
instead of paramiko (-c ssh) and prior to upgrading OpenSSH. I opened
another thread about that yesterday (Cannot copy a file to a server when
using ssh) before I saw this thread, but at that time I had to specify "-c
ssh" in the command line to get this reaction while here it just happens
regardless of what I do. Meanwhile normal scp and sftp from the command
line functions just fine; I get the failures only when I try to use Ansible
to copy files.
Something about the way that Ansible is calling scp or sftp appears to
trigger this bug in the latest version of OpenSSH. This will be a major
problem as it now means I cannot upgrade OpenSSH for any reason and still
be able to use Ansible. For now I have rolled back to
openssh-5.3p1-94.el6. I hope somebody finds a solution soon.
-Mark
On Wednesday, October 29, 2014 5:16:15 AM UTC-7, Adam Miller wrote:
>
> On Fri, Oct 24, 2014 at 8:59 PM, Michael DeHaan <[email protected]
> <javascript:>> wrote:
> > I've filed a github for now to include (in 1.8) a check to auto-disable
> > pipelining on RHEL 6.6+ (but not EL7), which should resolve most of the
> > confusion.
> >
> > We also may make it print a warning if it was on.
> >
> > But yeah, bugzilla seems appropriate.
> >
> > Bugzilla from someone with a nice friendly Red Hat TAM even more so :)
> >
> >
>
> I've submitted a ticket to my team's TAM through Red Hat support
> channels, if/when there is a public bugzilla as a side effect I'll
> link it here.
>
> -AdamM
>
> >
> > On Fri, Oct 24, 2014 at 7:24 PM, Todd Zullinger <[email protected]
> <javascript:>> wrote:
> >>
> >> Jacob Weber wrote:
> >>>
> >>> Just to clarify -- I was seeing the same results as Kevin, not Todd.
> >>> Removing "pipelining = True" from my config fixed the problem.
> >>
> >>
> >> I've since updated to 1.7.2 from epel-testing and I see the same
> results
> >> as you and Kevin. I've disabled pipelining as well for now, but it's
> >> definitely a performance hit (better to be slower and accurate though).
> >>
> >>> But I hope they're able to fix this issue in OpenSSH....did someone
> >>> report it?
> >>
> >>
> >> I haven't seen anything myself. I don't have a RHEL contract so I was
> >> hoping someone that did might file a ticket so it's more likely to get
> >> attention.
> >>
> >> --
> >> Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> If the world didn't suck, we'd all fall off.
> >>
> >> --
> >> 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] <javascript:>.
> >> To post to this group, send email to [email protected]
> <javascript:>.
> >> To view this discussion on the web visit
> >>
> https://groups.google.com/d/msgid/ansible-project/20141024232415.GE2838%40zaya.teonanacatl.net.
>
>
> >>
> >> 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] <javascript:>.
> > To post to this group, send email to [email protected]
> <javascript:>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgwojcjpMkpjHMNzgHV7hdzd8AV3YLC-TqBZMHFNBx4n2g%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/6fd8148c-a2f0-40af-a835-6fa7dec02f80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
