Foreman 2.0rc1 install problems

Support
1

Problem:
As always I’m early with the new foreman installation. This time I run into a dependency problem.

–> Finished Dependency Resolution
Error: Package: tfm-ror52-rubygem-turbolinks-2.5.4-1.el7.noarch (@foreman-rails-1.20-rhel7)
Requires: tfm-ror52-rubygem(coffee-rails)
Removing: tfm-ror52-rubygem-coffee-rails-4.2.2-1.el7.noarch (@foreman-rails-1.20-rhel7)
tfm-ror52-rubygem(coffee-rails) = 4.2.2
Obsoleted By: tfm-rubygem-coffee-rails-4.2.2-5.el7.noarch (foreman-2.0-rhel7)
Not found

We need a new turbolink package. Is repo http://yum.theforeman.org/rails/foreman-2.0/ obsolete ? It is empty.

Foreman and Proxy versions:
Foreman 1.24 -> Foreman 2.0

Distribution and version:
lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 7.7 (Maipo)
Release: 7.7
Codename: Maipo

Other relevant data:
Attached repos from Sattelite

rhel-x86_64-server-7
rhel-x86_64-server-7-rhscl-1
rhel-x86_64-server-extras-7
rhel-x86_64-server-optional-7
rhel-x86_64-server-rh-common-7
rhel-x86_64-server-supplementary-7
rhn-tools-rhel-x86_64-server-7

Addinial Repos
EPEL
Cenos-SCL
copy of Foreman 2.0 repo
copy of Foreman 2.0 plugins repo

2

Yes, all packages were added to the main repository. turbolinks has been removed. The foreman-release package should have all the repositories you need though for rhel you also need the rhscl repository enabled prior to installation.

It is still on the TODO to update the installation/upgrade manual.

3

Hi,

I was only able to update when I removed the turbolink packages via

rpm -e --nodeps tfm-ror52-rubygem-turbolinks-2.5.4-1.el7.noarch

There was no way to resolve the dependency problem.

4

We’ve moved all packages from tfm-ror52-* to tfm-*. I suspect that we had tfm-rubygem-turbolinks obsolete tfm-ror52-rubygem-turbolinks. Then we dropped turbolinks and had tfm obsolete tfm-rubygem-turbolinks. This means yum doesn’t know how to obsolete it. The solution is probably to have tfm also obsolete tfm-ror52-rubygem-turbolinks.

5

https://projects.theforeman.org/issues/29181