centos 6.5 issue

[Mike Simonson]

Hi,

I am using ansible to provision a vagrant box that's running with virtualbox on a centos 6.5 host.

Apparently there is an issue with the config.ssh.forward_agent option.

I am a bit at loss to know if the issue is caused by vagrant or by ansible.

Every time I try to provision I get

fatal: [default] => using -c ssh on certain older ssh versions may not support ControlPersist, set ANSIBLE_SSH_ARGS="" (or ssh_args in [ssh_connection] section of the config file) before running again
 

I tried both recommendation to no avail and I can't find any significant difference between that centos box and my machine ubuntu 14.04 in the ssh config.
It works perfectly fine on my machine.

Is this because ssh on centos 6.5 is in version 5.3 with fix backport ?
Does anyone has any experience with vagrant and ansible on centos ?

Thanks

[Michael DeHaan]

Since you are using CentOS as a control machine you will want to select paramiko as a transport or set the ssh arguments in ansible.cfg

I'm not sure how far Vagrant complicates this, as this isn't the Vagrant list, but there are plenty of users here that could probably help answer that question.

--Michael

--
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/999bbd63-22cf-42b2-afd8-884288ac14cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Dick Davies]

CentOS 6.x doesnt support ControlPersist, so it will use paramiko.

I installed CentOS 7 to use as my Ansible deploy VM just for this
feature, speeds
things up on our 30 node / 50 role stack significantly.

> https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgzASs-hEd9GAPKpTn01tF9CSrwBdeRPqtEQpxBxcHmNLg%40mail.gmail.com.

[Michael DeHaan]

Excellent, accelerated mode would have also been a good answer for 6.5 - though I definitely prefer the native SSH transport when possible.

Switch on pipelining if you haven't already, it should approximately double in speed again (search for pipelining in ansible.cfg)

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAK5eLPTq%3DCg8qnXNhk%2B%2B%3Dp1geiGtUSWuOX0R7%3DxBvHymDBThaA%40mail.gmail.com.

[Nigel Metheringham]

Michael DeHaan wrote:
> Excellent, accelerated mode would have also been a good answer for 6.5 -
> though I definitely prefer the native SSH transport when possible.

My Centos 6 control machine has an updated ssh client, built from the
Fedora ssh rpm (the server side has been left as is).

However that was a stop gap measure, and I'll replace it with a Centos 7
box when I get some round tuits.

Nigel.

--
[ Nigel Metheringham ------------------------------ ni...@dotdot.it ]
[ Ellipsis Intangible Technologies ]

[Mohammad Asshad]

Hi,

I had the same problem earlier, and updated yum update openssh, issue has been resolved.

Regards,

Asshad

  

  

This email may contain information, which is confidential and/or privileged. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents is prohibited. If you have received this electronic transmission in error, please notify the sender by telephone or return email and delete the material from your computer.

Star Media Group Berhad

[Formerly known as Star Publications (Malaysia) Berhad]

Tel: +60 (3) 79671388

Web: http://thestar.com.my