Bug #20004
closedKatello upgrade fails (tfm-rubygem(bastion))
Description
Katello 3.2.1.1 (Foreman 1.13.4) on RHEL7 -
Doing an yum update but gets an error:
---> Package util-linux.x86_64 0:2.23.2-33.el7_3.2 will be an update---> Package yum-rhn-plugin.noarch 0:2.0.1-6.el7 will be updated
---> Package yum-rhn-plugin.noarch 0:2.0.1-6.1.el7_3 will be an update
--> Running transaction check
---> Package kobo.noarch 0:0.5.1-1.el7 will be installed
---> Package tfm-rubygem-katello.noarch 0:3.3.2-1.el7 will be an update
--> Processing Dependency: tfm-rubygem(bastion) >= 4.0.0 for package: tfm-rubygem-katello-3.3.2-1.el7.noarch
--> Finished Dependency Resolution
Error: Package: tfm-rubygem-katello-3.3.2-1.el7.noarch (katello)
Requires: tfm-rubygem(bastion) >= 4.0.0
Installed: tfm-rubygem-bastion-3.3.4-1.fm1_13.el7.noarch (@foreman-plugins)
tfm-rubygem(bastion) = 3.3.4
Available: tfm-rubygem-bastion-3.3.2-1.fm1_13.el7.noarch (foreman-plugins)
tfm-rubygem(bastion) = 3.3.2 **************************************************************
yum can be configured to try to resolve such errors by temporarily enabling
disabled repos and searching for missing dependencies.
To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-514.el7 will be erased
---> Package tfm-rubygem-katello.noarch 0:3.3.2-1.el7 will be an update
--> Processing Dependency: tfm-rubygem(bastion) >= 4.0.0 for package: tfm-rubygem-katello-3.3.2-1.el7.noarch
--> Finished Dependency Resolution
Error: Package: tfm-rubygem-katello-3.3.2-1.el7.noarch (katello)
Requires: tfm-rubygem(bastion) >= 4.0.0
Installed: tfm-rubygem-bastion-3.3.4-1.fm1_13.el7.noarch (@foreman-plugins)
tfm-rubygem(bastion) = 3.3.4
Available: tfm-rubygem-bastion-3.3.2-1.fm1_13.el7.noarch (foreman-plugins)
tfm-rubygem(bastion) = 3.3.2
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
[root@localhost ~]#
How can I get aroun the update without breaking something?
Thanks
Files
Updated by Justin Sherrill over 7 years ago
- Status changed from New to Need more information
This looks like its attempting to upgrade to katello 3.3, was that the intent? If so, did you try following the upgrade guide at https://theforeman.org/plugins/katello/3.3/upgrade/index.html
It looks like it may be trying to pull from an incorrect version of foreman. If you are following those instructions and intending to upgrade to 3.3, you may try a 'yum clean all' first.
If that does not work, could you attach your /etc/yum.repos.d/* files?
Thanks
Updated by Justin Sherrill over 7 years ago
- Category set to Upgrades
- Translation missing: en.field_release set to 166
Updated by Kent Knudsen over 7 years ago
- File CentOS-SCLo-scl.repo CentOS-SCLo-scl.repo added
- File CentOS-SCLo-scl-rh.repo CentOS-SCLo-scl-rh.repo added
- File EPEL7_sm.repo EPEL7_sm.repo added
- File epel.repo epel.repo added
- File epel-testing.repo epel-testing.repo added
- File foreman.repo foreman.repo added
- File foreman-plugins.repo foreman-plugins.repo added
- File katello.repo katello.repo added
- File katello-client.repo katello-client.repo added
- File puppetlabs-pc1.repo puppetlabs-pc1.repo added
Justin Sherrill wrote:
This looks like its attempting to upgrade to katello 3.3, was that the intent? If so, did you try following the upgrade guide at https://theforeman.org/plugins/katello/3.3/upgrade/index.html
It looks like it may be trying to pull from an incorrect version of foreman. If you are following those instructions and intending to upgrade to 3.3, you may try a 'yum clean all' first.
If that does not work, could you attach your /etc/yum.repos.d/* files?
Thanks
For security reasons I did attempt an upgrade to 3.3 but got an fail when checking upgradeability (always 13 active tasks) and I have no clue as to how I can cancel them. In monitor view I see only 3 active jobs.
I then attempted a simple yum upgrade and that is where I am now.
My /etc/yum.repos.d/ files are attached
Updated by Justin Sherrill over 7 years ago
It looks like you are pointed to the new 3.3 repos but not the foreman 1.14 repos. Can you try running through: https://theforeman.org/plugins/katello/3.3/upgrade/index.html again and see if that helps?
Updated by Kent Knudsen over 7 years ago
Justin Sherrill wrote:
It looks like you are pointed to the new 3.3 repos but not the foreman 1.14 repos. Can you try running through: https://theforeman.org/plugins/katello/3.3/upgrade/index.html again and see if that helps?
Yes and same thing happens as last time:
[root@katello ~]# foreman-rake katello:upgrade_check This script makes no modifications and can be re-run multiple times for the most up to date results. Checking upgradeability... Checking for running tasks... [FAIL] - There are 13 active tasks. Please wait for these to complete or cancel them from the Monitor tab. [root@katello ~]#
And running yum update -y http://yum.theforeman.org/releases/1.14/el7/x86_64/foreman-release.rpm
[root@katello ~]# yum update -y http://yum.theforeman.org/releases/1.14/el7/x86_64/foreman-release.rpm Loaded plugins: product-id, search-disabled-repos, subscription-manager foreman-release.rpm | 16 kB 00:00:00 Examining /var/tmp/yum-root-_kNJTA/foreman-release.rpm: foreman-release-1.14.3-1.el7.noarch Marking /var/tmp/yum-root-_kNJTA/foreman-release.rpm as an update to foreman-release-1.13.4-1.el7.noarch Resolving Dependencies --> Running transaction check ---> Package foreman-release.noarch 0:1.13.4-1.el7 will be updated --> Processing Dependency: foreman-release = 1.13.4-1.el7 for package: foreman-plugin-1.13.4-1.el7.noarch ---> Package foreman-release.noarch 0:1.14.3-1.el7 will be an update --> Finished Dependency Resolution Error: Package: foreman-plugin-1.13.4-1.el7.noarch (@foreman) Requires: foreman-release = 1.13.4-1.el7 Removing: foreman-release-1.13.4-1.el7.noarch (installed) foreman-release = 1.13.4-1.el7 Updated By: foreman-release-1.14.3-1.el7.noarch (/foreman-release) foreman-release = 1.14.3-1.el7 Available: foreman-release-1.13.0-0.1.RC1.el7.noarch (foreman) foreman-release = 1.13.0-0.1.RC1.el7 Available: foreman-release-1.13.0-0.1.RC2.el7.noarch (foreman) foreman-release = 1.13.0-0.1.RC2.el7 Available: foreman-release-1.13.0-1.el7.noarch (foreman) foreman-release = 1.13.0-1.el7 Available: foreman-release-1.13.1-1.el7.noarch (foreman) foreman-release = 1.13.1-1.el7 Available: foreman-release-1.13.2-1.el7.noarch (foreman) foreman-release = 1.13.2-1.el7 Available: foreman-release-1.13.3-1.el7.noarch (foreman) foreman-release = 1.13.3-1.el7 ********************************************************************** yum can be configured to try to resolve such errors by temporarily enabling disabled repos and searching for missing dependencies. To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf ********************************************************************** Error: Package: foreman-plugin-1.13.4-1.el7.noarch (@foreman) Requires: foreman-release = 1.13.4-1.el7 Removing: foreman-release-1.13.4-1.el7.noarch (installed) foreman-release = 1.13.4-1.el7 Updated By: foreman-release-1.14.3-1.el7.noarch (/foreman-release) foreman-release = 1.14.3-1.el7 Available: foreman-release-1.13.0-0.1.RC1.el7.noarch (foreman) foreman-release = 1.13.0-0.1.RC1.el7 Available: foreman-release-1.13.0-0.1.RC2.el7.noarch (foreman) foreman-release = 1.13.0-0.1.RC2.el7 Available: foreman-release-1.13.0-1.el7.noarch (foreman) foreman-release = 1.13.0-1.el7 Available: foreman-release-1.13.1-1.el7.noarch (foreman) foreman-release = 1.13.1-1.el7 Available: foreman-release-1.13.2-1.el7.noarch (foreman) foreman-release = 1.13.2-1.el7 Available: foreman-release-1.13.3-1.el7.noarch (foreman) foreman-release = 1.13.3-1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@katello ~]#
Updated by Justin Sherrill over 7 years ago
Hrmm, i wonder what pulled in foreman-plugins. It doesn't look like our upgrade instructions will work with it installed. Would you be able to try removing it?
rpm -e foreman-plugins
you can reinstall it after upgrading foreman-release.
Updated by Kent Knudsen over 7 years ago
Uninstalling the foreman-plugins RPM did the trick.
After the uninstall I disabled that repo, did a yum clean all and started the upgrade procedure which completed all the way without any fuss.
Now on katello 3.3.2 - foreman 1.14.3
Thanks for any help and please close issue.
Updated by Anonymous over 7 years ago
- Status changed from Need more information to Resolved
thanks for letting us know!