Description of problem:
The installation of ansible-tower-setup in a CFME 5.9.2 upgrade installs several non-Red Hat yum repositories such as epel-7, ansible-el7, pgdg-96-centos and jlaska-rabbitmq. If a subsequent yum update is performed then packages will be installed from these repositories, overwriting the correct and tested packages from the cf-me repository.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update a CFME 5.9.1 appliance to CFME 5.9.2
2. Perform a 'yum repolist', and notice the extra repositories
3. Perform a 'yum update' and notice that inappropriate packages such as 2.5.2-1.el7 would be installed
Additional repositories should not be installed.
I meant to write "Ansible 2.5.2-1.el7 would be installed"
This is the expected behavior of the Tower setup playbooks. CFME is supposed to pass skip-tags arguments to setup.sh to suppress this. Can we verify that those arguments are being passed?
Please review if a solution doc is needed for cfme appliances behind a Satellite. Since those repositories will not be available.
In Tower 3.2.0 the installer was refactored and the tasks that install the yum repos were moved into a separate Ansible role.
From an old Slack conversation I can see that the argument currently being passed by CFME to the installer is: --skip-tags=packages.
I believe the solution is to apply the same --skip-tags tag CFME is using where this new role is included in the Tower installer.
We have updated the Tower installer so that it will correctly respect --skip-tags=packages again. The fix will be in Tower 3.1.7/3.2.5, which will be going out today or tomorrow.
We have resolved build issues that prevented us from getting 3.1.7/3.2.5 in brew. 3.1.7 now exists and 3.2.5 will be in progress shortly. These versions should properly respect --skip-tags=packages again.
*** Bug 1582757 has been marked as a duplicate of this bug. ***
Fixed and verified in 220.127.116.11.20180606184006_8d120c0. ansible installer respects --skip-tags=packages. No additional repos is not added.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.