I am aware that this is 5 years old but I had a similar problem that was caused by my ~/.ssh/config file. This post is what helped me find my solution.
If anyone else is having this issue, add ssh_args = -F /dev/null to your /etc/ansible/ansible.cf On Saturday, July 12, 2014 at 8:12:53 AM UTC-7, Chris Jones wrote: > > Matt THANKS! > > I thought it was Fedora as a node that was causing an issue but your > suggest was spot on! I had a SSH_AGENT script in the .bashrc file so I > removed it and it worked. > > Thanks > > On Saturday, July 12, 2014 10:09:03 AM UTC-4, Matt Martz wrote: >> >> Typically this is caused by having something in your .bashrc or similar >> that is echoing text. See >> http://www.snailbook.com/faq/sftp-corruption.auto.html >> >> >> On Sat, Jul 12, 2014 at 8:45 AM, Chris Jones <cjo...@cloudm2.com> wrote: >> >>> Thanks. As I stated in the opening post, the password-less ssh is >>> working from the controller to the node as expected so I would expect >>> ansible to work. >>> >>> I also included the output from -vvvv which shows ansible is trying to >>> work but ALWAYS returns 'FAILED => failed to transfer file to >>> /home/cjones/.ansible/tmp/.../(whatever module I try): Received message too >>> long ...' >>> >>> These are two virgin VMs setup with yum updates, ansible installed via >>> pip, python 2.7.5, centos 7 (controller) and fedora 20 (node) [note: >>> started the other way but had the same issues so we thought we would try >>> making centos 7 the controller and fedora the node]. Maybe we kill fedora >>> all together but I thought it would work with fedora. >>> >>> Ansible is currently on both VMs but I understand it does not have to be >>> (see previous paragraph note on why it is installed on both). >>> >>> Also, when I look at the .ansible/tmp/... on the node machine the tmp >>> directories exist from each command I run but nothing is in any directory. >>> >>> I'm at a lost!!!!! >>> >>> thanks >>> >>> >>> On Saturday, July 12, 2014 9:32:15 AM UTC-4, Brian Coca wrote: >>>> >>>> The way ssh with keys works is that the machine you want to logon FROM >>>> has to have a private key, hosts you want to log TO have to have the >>>> public >>>> version of that key. >>>> >>>> to test that it is working just use the ssh command itself, if that >>>> works, ansible should work also. >>>> >>>> >>>> -- >>>> Brian Coca >>>> Stultorum infinitus est numerus >>>> 011000010111001001100101011011100010011101110100001000000111 >>>> 100101101111011101010010000001110011011011010110000101110010 >>>> 0111010000100001 >>>> Pedo mellon a minno >>>> >>> -- >>> 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-proje...@googlegroups.com. >>> To post to this group, send email to ansible...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/ansible-project/d182bdb2-17fd-4d65-9efd-7143ef4e130e%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/ansible-project/d182bdb2-17fd-4d65-9efd-7143ef4e130e%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Matt Martz >> ma...@sivel.net >> http://sivel.net/ >> > -- 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/c352a720-f246-4005-af36-18e20c19e94e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
