What happened?In the past (pre-2017-10) most people who were on RHEL or CentOS or similar RHEL based systems used to install Ansible from the EPEL repository. This way the package was updates regularly and it was ensured that it met the quite high packaging standards of the EPEL project. However, a few days ago someone noticed that the EPEL repositories no longer contain an Ansible rpm package:
This caused some confusion and questions about the reasons behind that move.I'm running RHEL 7.3, and have installed the latest epel-release-latest-7.noarch.rpm. However, I'm unable to install ansible from this repo.
EPEL repository policyTo better understand what happened it is important to understand EPEL’s package policy:
EPEL strives to never replace or interfere with packages shipped by Enterprise Linux.While the idea of EPEL is to provide cool additional packages for RHEL, they will never replace anything that is shipped.
Change at Red Hat Enterprise LinuxThat philosophy regularly requires that the EPEL project removes packages: each time when RHEL adds a package EPEL needs to check if they are providing it, and removes it. And a few weeks ago exactly that happened: Ansible was included in RHELs extras repository. The reasons behind that move is that the newest incarnation of RHEL now comes along with so called system roles – which require Ansible to execute them.
But where to get it now?Ansible is now directly available to RHEL users as mentioned above. Also, CentOS picked up Ansible in their extras repository, and there are plenty of other ways available. The only case where something actually changes for people is when the EPEL repository is activated – but the extras repository is not.
Filed under: Ansible, Cloud, Debian & Ubuntu, Fedora & RHEL, HowTo, Linux, Microsoft, Shell, SUSE, Technology