Foreman yum dependency after a Katello 3.4 -> 3.5 upgrade

I did an update from Katello 3.4 -> 3.5 yesterday and ran into what looks
like it might be a packaging issue.

The original symptom was that remote execution was broken. It took me a
little while but then I realized that I still had the 1.15 remote execution
packages installed instead of the 1.16 equivalents.

[root@rich-form-01-pv yum.repos.d]# rpm -qa | grep fm1_15
tfm-rubygem-dynflow-0.8.30-1.fm1_15.el7.noarch
tfm-rubygem-foreman_remote_execution-1.3.7-1.fm1_15.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.0.6-1.fm1_15.el7.noarch
tfm-rubygem-concurrent-ruby-edge-0.2.3-1.fm1_15.el7.noarch

I check and I did have the correct 1.16 repos defined but yum update showed
everything as up to date. When I tried to manually install the 1.16
version, I got this

[root@rich-form-01-pv ~]# yum install
https://yum.theforeman.org/plugins/1.16/el7/x86_64/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm
Loaded plugins: fastestmirror
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm
> 434 kB 00:00:00
Examining
/var/tmp/yum-root-5i1ybr/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm:
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch
/var/tmp/yum-root-5i1ybr/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm:
does not update installed package.
Error: Nothing to do

So I ended up removing my remote 1.15 remote execution package and
installing the 1.16 equivalents. That got remote execution working but
then I ran an orphan check as a sanity check and found some additional
packages that don’t seem to be right.

[root@rich-form-01-pv yum.repos.d]# package-cleanup --orphans
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile

  • base: mirror.riverfrontnetworks.com
  • epel: mirror.steadfast.net
  • extras: mirror.beyondhosting.net
  • updates: mirror.rackspace.com
    java-client-1.0-1.noarch
    katello-client-bootstrap-1.4.0-2.el7.noarch
    katello-default-ca-1.0-1.noarch
    katello-server-ca-1.0-1.noarch
    kernel-3.10.0-514.el7.x86_64
    kernel-3.10.0-514.16.1.el7.x86_64
    kernel-3.10.0-514.21.1.el7.x86_64
    kernel-3.10.0-514.26.2.el7.x86_64
    pulp-client-1.0-1.noarch
    python-nectar-1.5.4-1.el7.noarch
    rich-form-01-pv.ipa.snapbs.com-apache-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-foreman-client-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-foreman-proxy-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-foreman-proxy-client-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-puppet-client-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-qpid-broker-1.0-2.noarch
    rich-form-01-pv.ipa.snapbs.com-qpid-client-cert-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-qpid-router-client-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-qpid-router-server-1.0-1.noarch
    rich-form-01-pv.ipa.snapbs.com-tomcat-1.0-1.noarch
    tfm-rubygem-concurrent-ruby-edge-0.2.3-1.fm1_15.el7.noarch
    tfm-rubygem-dynflow-0.8.30-1.fm1_15.el7.noarch
    tfm-rubygem-net-ssh-4.0.1-2.el7.noarch
    tfm-rubygem-safemode-1.3.2-1.el7.noarch
    tfm-rubygem-scoped_search-4.1.2-1.el7.noarch

I don’t understand the last 5 packages in this list. Some of these
definitely have 1.16 equivalents but it seems like some kind of dependency
isn’t right as I can’t upgrade or remove and reinstall without blowing up a
lot of packages. I’m pretty sure when I did the 3.3 -> 3.4 upgrade the
orphans list didn’t have any Foreman or Katello packages (except certs).

Any ideas what may be going on with those packages during an upgrade?

Regards,
–Tony