# Ansible 2.4.2.0 EPEL fails on CentOS 7.4.1708.  Known problem?

**URL:** <https://forum.ansible.com/t/ansible-2-4-2-0-epel-fails-on-centos-7-4-1708-known-problem/26438>\
**Category:** Ansible Project\
**Created:** [January 8, 2018, 3:19pm UTC](https://forum.ansible.com/t/ansible-2-4-2-0-epel-fails-on-centos-7-4-1708-known-problem/26438 "2018-01-08T15:19:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oscar\_Hodgson](https://avatars.discourse-cdn.com/v4/letter/o/8dc957/32.png) [@Oscar\_Hodgson](https://forum.ansible.com/u/Oscar_Hodgson)\
**Post date:** [January 8, 2018, 3:19pm UTC](https://forum.ansible.com/t/ansible-2-4-2-0-epel-fails-on-centos-7-4-1708-known-problem/26438/1 "2018-01-08T15:19:16Z")

</div>

I have a work-around available, just checking. The CentOS 6.9 EPEL ansible 2.4.2.0 works.

Setting up a group of 20+ CentOS 7 boxes and using ansible on one “master” to manage the group.

SSH from the master to the clients works fine. tcpdump on the workers shows ping and SSH connections, but no evidence of IP traffic from ‘ansible -m ping’ from the master. ‘ansible -m ping’ from a CentOS 6.9 host works.

All CentOS 7 machines running distro’s python 2.7.5. CentOS 6.9 alternative is running distro’s python 2.6.6.

Is this a known problem?

I’m considering my options (i.e., switch the master only or all to CentOS 6.9) but thought I’d check first …

Thanks.

Oscar

---

<div class="post-metadata">

**Author:** ![James\_Tanner](https://avatars.discourse-cdn.com/v4/letter/j/53a042/32.png) [@James\_Tanner](https://forum.ansible.com/u/James_Tanner)\
**Post date:** [January 8, 2018, 9:18pm UTC](https://forum.ansible.com/t/ansible-2-4-2-0-epel-fails-on-centos-7-4-1708-known-problem/26438/2 "2018-01-08T21:18:04Z")

</div>

Please provide an example -vvvv output.

---

<div class="post-metadata">

**Author:** ![Oscar\_Hodgson](https://avatars.discourse-cdn.com/v4/letter/o/8dc957/32.png) [@Oscar\_Hodgson](https://forum.ansible.com/u/Oscar_Hodgson)\
**Post date:** [January 11, 2018, 7:18pm UTC](https://forum.ansible.com/t/ansible-2-4-2-0-epel-fails-on-centos-7-4-1708-known-problem/26438/3 "2018-01-11T19:18:39Z")

</div>

\<sigh\>

The same problem occurred after the machines has been flipped to CentOS 6.9.

SELINIX=disabled or /sbin/restorecon -R -v /etc/ssh/ on the ansible node resolved the issue.

Thank you for the inspiration to dig deeper. I reckon I’ve gotten used to ansible ‘just working’.

Oscar