Foreman Upgrade from 1.22.1 to 1.23.0 - Dependency problems

dIELERx · September 11, 2019, 2:22pm

Problem:
Cant upgrade Foreman to latest version because of one dependency problem. I am following the upgrade guide Foreman :: Manual. The system is up to date and running the latest Foreman 1.22 packages.

Is there any other step required, which is not written down on the upgrade guide? I actually don’t know how to fix the dependency problem.

Expected outcome:
Upgrade to 1.23.0

Foreman and Proxy versions:
1.22.1

Foreman and Proxy plugin versions:

foreman-tasks 0.15.8
foreman_ansible 3.0.2
foreman_openscap 1.0.1
foreman_remote_execution 1.8.2
katello 3.12.3

Other relevant data:

yum upgrade
Plugin "pulp-profile-update" can't be imported
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: ftp.rrzn.uni-hannover.de
 * centos-sclo-rh: mirror1.hs-esslingen.de
 * epel: mirror.23media.com
 * extras: mirror1.hs-esslingen.de
 * updates: mirror.23media.com
Resolving Dependencies
--> Running transaction check
---> Package foreman.noarch 0:1.22.1-1.el7 will be updated
--> Processing Dependency: foreman-webpack-vendor-js(896a41b542bae29094f1) for package: tfm-rubygem-katello-3.12.3-1.el7.noarch
---> Package foreman.noarch 0:1.23.0-1.el7 will be an update
--> Processing Dependency: tfm-rubygem(bcrypt) < 4.0 for package: foreman-1.23.0-1.el7.noarch
--> Processing Dependency: tfm-rubygem(bcrypt) >= 3.1 for package: foreman-1.23.0-1.el7.noarch
---> Package foreman-cli.noarch 0:1.22.1-1.el7 will be updated
---> Package foreman-cli.noarch 0:1.23.0-1.el7 will be an update
---> Package foreman-debug.noarch 0:1.22.1-1.el7 will be updated
---> Package foreman-debug.noarch 0:1.23.0-1.el7 will be an update
---> Package foreman-installer.noarch 1:1.22.1-1.el7 will be updated
---> Package foreman-installer.noarch 1:1.23.0-1.el7 will be an update
---> Package foreman-installer-katello.noarch 1:1.22.1-1.el7 will be updated
---> Package foreman-installer-katello.noarch 1:1.23.0-1.el7 will be an update
---> Package foreman-postgresql.noarch 0:1.22.1-1.el7 will be updated
---> Package foreman-postgresql.noarch 0:1.23.0-1.el7 will be an update
---> Package foreman-proxy.noarch 0:1.22.1-1.el7 will be updated
---> Package foreman-proxy.noarch 0:1.23.0-1.el7 will be an update
---> Package foreman-selinux.noarch 0:1.22.1-1.el7 will be updated
---> Package foreman-selinux.noarch 0:1.23.0-1.el7 will be an update
---> Package rubygem-foreman_maintain.noarch 0:0.4.2-1.el7 will be updated
---> Package rubygem-foreman_maintain.noarch 1:0.4.5-1.el7 will be an update
---> Package rubygem-little-plugger.noarch 0:1.1.3-23.el7 will be updated
---> Package rubygem-little-plugger.noarch 0:1.1.4-1.el7 will be an update
---> Package rubygem-smart_proxy_ansible.noarch 0:2.1.2-3.fm1_22.el7 will be updated
---> Package rubygem-smart_proxy_ansible.noarch 0:3.0.1-1.fm1_23.el7 will be an update
---> Package rubygem-smart_proxy_remote_execution_ssh.noarch 0:0.2.1-1.el7 will be updated
---> Package rubygem-smart_proxy_remote_execution_ssh.noarch 0:0.2.1-2.el7 will be an update
---> Package tfm-rubygem-concurrent-ruby-edge.noarch 1:0.4.1-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-concurrent-ruby-edge.noarch 1:0.4.1-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-dynflow.noarch 0:1.2.3-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-dynflow.noarch 0:1.2.3-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-foreman-tasks.noarch 0:0.15.9-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-foreman-tasks.noarch 0:0.16.1-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-foreman-tasks-core.noarch 0:0.3.2-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-foreman-tasks-core.noarch 0:0.3.2-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-foreman_ansible.noarch 0:3.0.2-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-foreman_ansible.noarch 0:3.0.5-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-foreman_ansible_core.noarch 0:3.0.0-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-foreman_ansible_core.noarch 0:3.0.0-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-foreman_openscap.noarch 0:1.0.1-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-foreman_openscap.noarch 0:1.0.4-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-foreman_remote_execution.noarch 0:1.8.2-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-foreman_remote_execution.noarch 0:1.8.2-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-hammer_cli.noarch 0:0.17.1-1.el7 will be updated
---> Package tfm-rubygem-hammer_cli.noarch 0:0.18.0-1.el7 will be an update
---> Package tfm-rubygem-hammer_cli_foreman.noarch 0:0.17.2-1.el7 will be updated
---> Package tfm-rubygem-hammer_cli_foreman.noarch 0:0.18.0-1.el7 will be an update
---> Package tfm-rubygem-hammer_cli_foreman_bootdisk.noarch 0:0.1.3-7.el7 will be updated
---> Package tfm-rubygem-hammer_cli_foreman_bootdisk.noarch 0:0.3.0-1.el7 will be an update
---> Package tfm-rubygem-hammer_cli_foreman_remote_execution.noarch 0:0.1.0-2.fm1_22.el7 will be updated
---> Package tfm-rubygem-hammer_cli_foreman_remote_execution.noarch 0:0.1.0-2.fm1_23.el7 will be an update
---> Package tfm-rubygem-hammer_cli_foreman_tasks.noarch 0:0.0.13-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-hammer_cli_foreman_tasks.noarch 0:0.0.13-1.fm1_23.el7 will be an update
---> Package tfm-rubygem-little-plugger.noarch 0:1.1.3-23.el7 will be updated
---> Package tfm-rubygem-little-plugger.noarch 0:1.1.4-1.el7 will be an update
---> Package tfm-rubygem-net-ldap.noarch 0:0.15.0-3.el7 will be updated
---> Package tfm-rubygem-net-ldap.noarch 0:0.16.1-1.el7 will be an update
---> Package tfm-rubygem-netrc.noarch 0:0.11.0-3.el7 will be updated
---> Package tfm-rubygem-netrc.noarch 0:0.11.0-4.el7 will be an update
---> Package tfm-rubygem-parse-cron.noarch 0:0.1.4-4.fm1_22.el7 will be updated
---> Package tfm-rubygem-parse-cron.noarch 0:0.1.4-4.fm1_23.el7 will be an update
---> Package tfm-rubygem-rest-client.noarch 0:2.0.1-3.el7 will be updated
---> Package tfm-rubygem-rest-client.noarch 0:2.0.2-1.el7 will be an update
---> Package tfm-rubygem-smart_proxy_dynflow_core.noarch 0:0.2.2-1.fm1_22.el7 will be updated
---> Package tfm-rubygem-smart_proxy_dynflow_core.noarch 0:0.2.2-1.fm1_23.el7 will be an update
--> Running transaction check
---> Package foreman.noarch 0:1.22.1-1.el7 will be updated
--> Processing Dependency: foreman-webpack-vendor-js(896a41b542bae29094f1) for package: tfm-rubygem-katello-3.12.3-1.el7.noarch
---> Package tfm-rubygem-bcrypt.x86_64 0:3.1.12-1.el7 will be installed
--> Finished Dependency Resolution
Error: Package: tfm-rubygem-katello-3.12.3-1.el7.noarch (@katello)
           Requires: foreman-webpack-vendor-js(896a41b542bae29094f1)
           Removing: foreman-1.22.1-1.el7.noarch (@foreman)
               foreman-webpack-vendor-js(896a41b542bae29094f1)
           Updated By: foreman-1.23.0-1.el7.noarch (foreman)
               Not found
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

As far as I understand it correctly, Katello seems to require foreman-webpack-vendor-js and foreman-1.23.0 wants to remove it.

ekohl · September 11, 2019, 2:34pm

Katello 3.13 is currently still a release candidate so I’d recommend waiting for the GA version.

dIELERx · September 11, 2019, 2:37pm

Hmm, I am not using Katello 3.13 as its not stable yet. Is it required for Foreman 1.23? Right now I am still using 3.12.3 as it is the latest stable version.

ekohl · September 11, 2019, 2:46pm

Katello releases are always tied to a specific Foreman y-stream and has never supported more multiple Foreman y-streams. That means 3.12 is tied to Foreman 1.22 and you’ll have to wait for Katello 3.13 which is being worked on.

dIELERx · September 11, 2019, 2:47pm

Ah okay, got it. Thanks. Then I’ll wait for Katello 3.13.