# centos 6.5 issue **URL:** \ **Category:** Ansible Project\ **Tags:** ubuntu\ **Created:** [July 28, 2014, 1:43pm UTC](https://forum.ansible.com/t/centos-6-5-issue/15791 "2014-07-28T13:43:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Mike\_Simonson](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@Mike\_Simonson](https://forum.ansible.com/u/Mike_Simonson)\ **Post date:** [July 28, 2014, 1:43pm UTC](https://forum.ansible.com/t/centos-6-5-issue/15791/1 "2014-07-28T13:43:20Z")
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 ---
**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\ **Post date:** [July 28, 2014, 2:14pm UTC](https://forum.ansible.com/t/centos-6-5-issue/15791/2 "2014-07-28T14:14:48Z")
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 ---
**Author:** ![Dick\_Davies](https://avatars.discourse-cdn.com/v4/letter/d/b9e5f3/32.png) [@Dick\_Davies](https://forum.ansible.com/u/Dick_Davies)\ **Post date:** [July 31, 2014, 10:41am UTC](https://forum.ansible.com/t/centos-6-5-issue/15791/3 "2014-07-31T10:41:25Z")
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. ---
**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\ **Post date:** [July 31, 2014, 1:03pm UTC](https://forum.ansible.com/t/centos-6-5-issue/15791/4 "2014-07-31T13:03:57Z")
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) ---
**Author:** ![Nigel\_Metheringham](https://avatars.discourse-cdn.com/v4/letter/n/3ec8ea/32.png) [@Nigel\_Metheringham](https://forum.ansible.com/u/Nigel_Metheringham)\ **Post date:** [July 31, 2014, 1:24pm UTC](https://forum.ansible.com/t/centos-6-5-issue/15791/5 "2014-07-31T13:24:12Z")
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. ---
**Author:** ![Mohammad\_Asshad](https://avatars.discourse-cdn.com/v4/letter/m/7c8e57/32.png) [@Mohammad\_Asshad](https://forum.ansible.com/u/Mohammad_Asshad)\ **Post date:** [October 2, 2015, 8:49am UTC](https://forum.ansible.com/t/centos-6-5-issue/15791/6 "2015-10-02T08:49:29Z")
Hi, I had the same problem earlier, and updated yum update openssh, issue has been resolved. Regards, Asshad