Bug 1333769

Summary: foreman-installer upgrade fails on connecting to Capsule
Product: Red Hat Satellite Reporter: Roman Plevka <rplevka>
Component: UpgradesAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, ehelms, mbacovsk
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-3.0.0.28-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:01:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/foreman-installer/katello.log none

Description Roman Plevka 2016-05-06 11:41:16 UTC
Description of problem:
running foreman-installer --upgrade on sat6.2.0 Beta (upgrading to GA10) fails with:

# foreman-installer --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_foreman failed. Check logs for more information.
/usr/lib/ruby/gems/1.8/gems/kafo-0.7.3/lib/kafo/logger.rb:108:in `error': wrong number of arguments (87 for 1) (ArgumentError)

the /var/log/foreman-installer/katello.log indicates it failed on connection refused to internal capsule (however, that one was already down as installer stopped the services) - I'll attach the log to the BZ

Version-Release number of selected component (if applicable):
6.2.0 GA10


Steps to Reproduce:
1. yum upgrade
2. foreman-installer --upgrade

Actual results:
Upgrade step migrate_foreman failed. Check logs for more information.

Expected results:
Upgrade works well

Comment 1 Roman Plevka 2016-05-06 11:42:06 UTC
Created attachment 1154590 [details]
/var/log/foreman-installer/katello.log

Comment 4 Martin Bacovsky 2016-05-10 14:46:33 UTC
The attempt to connect to capsule is triggered by the migration where it shouldn't be. The cause and fix is same as in BZ#1333774.

Comment 5 Bryan Kearney 2016-05-11 14:16:39 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14982 has been closed

Comment 6 Roman Plevka 2016-05-27 14:29:29 UTC
VERIFIED
on sat6.2.0 Beta (GA13.1)

Upgrade now passes with no errors.


<pre>
# satellite-installer --upgrade --scenario satellite
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_databases...
Upgrade Step: update_http_conf...
Upgrade Step: migrate_pulp...
Upgrade Step: fix_pulp_httpd_conf...
Upgrade Step: start_httpd...
Upgrade Step: start_qpidd...
Upgrade Step: start_pulp...
Upgrade Step: migrate_candlepin...
Upgrade Step: start_tomcat...
Upgrade Step: fix_katello_settings_file...
Upgrade Step: migrate_foreman...
Upgrade Step: migrate_gutterball...
Upgrade Step: remove_nodes_distributors...
Upgrade Step: Running installer...
Installing             Done                                               [100%] [............................................................]
  The full log is at /var/log/foreman-installer/satellite.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: elasticsearch_message...
Upgrade Step: remove_docker_v1_content (this may take a while) ...
Katello upgrade completed!

</pre>

Comment 7 Bryan Kearney 2016-07-27 11:01:44 UTC
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