Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: I was trying upgrade from sat6.2 snap2 to snap2.1. And I was using only custom contents on my setup. And upgrade got failed at step:
[root@cloud-qe-7 ~]# foreman-installer --scenario katello --upgrade
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_databases...
Upgrade Step: migrate_pulp...
Upgrade Step: start_httpd...
Upgrade Step: migrate_candlepin...
Upgrade Step: migrate_foreman...
Upgrade Step: migrate_gutterball...
Upgrade Step: Running installer...
Installing Done [100%] [..................................................................]
The full log is at /var/log/foreman-installer/katello.log
Upgrade Step: restart_services...
Upgrade Step: db_seed...
Upgrade Step: errata_import (this may take a while) ...
Upgrade step errata_import failed. Check logs for more information.
I'm not sure if its early to perform upgrade, but here we are doing upgrade form 6.2 to 6.2 with diff snaps without lot of changes. So I think it should work.
Here are the logs from production.log:
[ INFO 2016-03-04 04:07:56 main] Upgrade Step: errata_import (this may take a while) ...
[ERROR 2016-03-04 04:08:09 main] Ignoring ruby-libvirt-0.5.2 because its extensions are not built. Try: gem pristine ruby-libvirt --version 0.5.2
/opt/theforeman/tfm/root/usr/share/gems/gems/docker-api-1.17.0/lib/docker.rb:103: warning: circular argument reference - connection
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.4/config/routes/overrides.rb:3: warning: already initialized constant Katello::WhitelistConstraint::PATHS
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.4/config/routes/overrides.rb:3: warning: previous definition of PATHS was here
rake aborted!
NameError: uninitialized constant Actions::Katello::System::GenerateApplicability
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_hooks-0.3.9/lib/foreman_hooks.rb:83:in `load_missing_constant_with_hooks'
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.4/lib/katello/tasks/upgrades/2.1/import_errata.rake:39:in `block (4 levels) in <top (required)>'
Tasks: TOP => katello:upgrades:2.1:import_errata
(See full trace by running task with --trace)
Importing Errata
Generating applicability for 1 Content Hosts
Version-Release number of selected component (if applicable):
upgrade from sat6.2 snap2 to sat6.2 snap2.1
How reproducible:
always
Steps to Reproduce:
1. foreman-installer --scenario katello --upgrade
2.
3.
Actual results:
Upgrade step errata_import failed. Check logs for more information.
Expected results:
upgrade should work atleast between one snap of 6.2 to other.
Additional info:
Verified with sat6.2 beta snap6
I upgraded Sat 6.2 from snap5 to snap6 and upgrade was completed successfully. I don't find any issue neither on console nor in logs.
~]# foreman-installer --scenario katello --upgrade
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_databases...
Upgrade Step: migrate_pulp...
Upgrade Step: start_httpd...
Upgrade Step: migrate_candlepin...
Upgrade Step: migrate_foreman...
Upgrade Step: migrate_gutterball...
Upgrade Step: Running installer...
Installing Done [100%] [..................................................................]
The full log is at /var/log/foreman-installer/katello.log
Upgrade Step: restart_services...
Upgrade Step: db_seed...
Upgrade Step: import_package_groups (this may take a while) ...
Upgrade Step: import_rpms (this may take a while) ...
Upgrade Step: import_distributions (this may take a while) ...
Upgrade Step: import_puppet_modules (this may take a while) ...
Upgrade Step: import_subscriptions (this may take a while) ...
Upgrade Step: remove_elasticsearch...
Upgrade Step: remove_docker_v1_content (this may take a while) ...
Katello upgrade completed!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1500