Foreman Maintain

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1647202

Description of problem:

After Upgrading from Satellite 6.3 to Satellite 6.4 the
gofer-2.12.1-1.el7sat.noarch & katello-agent-3.3.5-3.el7sat.noarch packages get installed in the satellite 6.4 server as satellite-tools-repository-6.4 also gets enabled but during a fresh installation of satellite 6.4 cannot see the same scenario , neither the tools repository gets enabled nor both the packages.

Version-Release number of selected component (if applicable):

satellite-6.4.0-15.el7sat.noarch
gofer-2.12.1-1.el7sat.noarch
katello-agent-3.3.5-3.el7sat.noarch

How reproducible:

During upgrade from Satellite 6.3 -> Satellite 6.4

Steps to Reproduce:

1.Upgrade through the regular method using foreman-maintain commands from Satellite 6.3 -> 6.4.
2.Run the below commands to confirm after successful upgrade.

1. rpm -qa | grep gofer
2. rpm -qa | grep katello-agent
3. yum repolist

Actual results:
#rpm -qa | grep gofer
gofer-2.12.1-1.el7sat.noarch -<<< Not required
python-gofer-2.12.1-1.el7sat.noarch
python-gofer-proton-2.12.1-1.el7sat.noarch
python-gofer-qpid-2.12.1-1.el7sat.noarch

#rpm -qa | grep katello-agent
katello-agent-3.3.5-3.el7sat.noarch -<<< Not required

#yum repolist

rhel-7-server-satellite-tools-6.4-rpms/x86_64 -<<< Not required
rhel-7-server-ansible-2.6-rpms/x86_64
rhel-7-server-rpms/7Server/x86_64
rhel-7-server-satellite-6.4-rpms/x86_64
rhel-7-server-satellite-maintenance-6-rpms/x86_64
rhel-server-rhscl-7-rpms/7Server/x86_64

Expected results:

#rpm -qa | grep gofer
python-gofer-2.12.1-1.el7sat.noarch
python-gofer-proton-2.12.1-1.el7sat.noarch
python-gofer-qpid-2.12.1-1.el7sat.noarch

#rpm -qa | grep katello-agent
No output

#yum repolist

rhel-7-server-ansible-2.6-rpms/x86_64
rhel-7-server-rpms/7Server/x86_64
rhel-7-server-satellite-6.4-rpms/x86_64
rhel-7-server-satellite-maintenance-6-rpms/x86_64
rhel-server-rhscl-7-rpms/7Server/x86_64

Additional info:
We can understand that during upgrade the issue is happening while during fresh installation we cannot see any deviation. I have tested the same scenario on the test environment.