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.
DescriptionBrad Buckingham
2016-05-13 02:01:13 UTC
Created attachment 1156958[details]
Satellite upgrade installer log
Description of problem:
Attempting to upgrade to an early version of Satellite 6.2 Beta (internal build) from 6.1 is resulting in an error during foreman_migrate.
Version-Release number of selected component (if applicable):
Satellite 6.2 Snap 11
How reproducible:
Always
Steps to Reproduce:
1. install Satellite 6.1
2. update packages to Satellite 6.2
3. patch system to include fixes for bug 1334961, bug 1335675 & bug 1335699
4. satellite-installer --scenario satellite --upgrade --force
Actual results:
# foreman-installer --upgrade
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_databases...
Upgrade Step: update_http_conf...
Upgrade Step: migrate_pulp...
Upgrade Step: start_httpd...
Upgrade Step: migrate_candlepin...
Upgrade Step: migrate_foreman...
Upgrade step migrate_foreman failed. Check logs for more information.
Expected results:
No error during the migrate_foreman step.
Additional info:
Note: see attached log for complete installer run.
In the /var/log/foreman-installer/satellite.log, the following is observed:
...[snip]...
[ INFO 2016-05-13 00:17:14 main] Upgrade Step: migrate_foreman...
[ERROR 2016-05-13 00:17:47 main] rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:
Some backend services are not running: {:status=>"FAIL", :services=>{:pulp=>{:status=>"FAIL", :message=>"404 Resource Not Found"}, :pulp_auth=>{:status=>"FAIL", :message=>"Skipped pulp_auth check after failed pulp check"}, :candlepin=>{:status=>"FAIL", :message=>"Connection refused - connect(2) for \"localhost\" port 8443"}, :candlepin_auth=>{:status=>"FAIL", :message=>"A backend service [ Candlepin ] is unreachable"}, :foreman_tasks=>{:status=>"ok", :duration_ms=>"6"}}}/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.28/db/migrate/20150930183738_migrate_content_hosts.rb:297:in `up'
...[snip]...
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.28/db/migrate/20150930183738_migrate_content_hosts.rb:297:in `up'
...[snip]...
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:1501