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: Satellite-installer failed with argument error while upgrading the satellite from 6.7 to 6.8
Version-Release number of selected component (if applicable):
6.8
How reproducible:
always
Steps to Reproduce:
1. Prepared the environment to perform the satellite-upgrade from 6.7 to 6.8
2. Configure all the repository
3. Execute the pre-check and it has completed successfully.
# foreman-maintain upgrade run --whitelist="disk-performance,repositories-validate, repositories-setup" --target-version 6.8 -y
Checking for new version of satellite-maintain...
Nothing to update, can't find new version of satellite-maintain.
Running Checks before upgrading to Satellite 6.8
================================================================================
Skipping pre_upgrade_checks phase as it was already run before.
To enforce to run the phase, use `upgrade run --phase pre_upgrade_checks`
Running Procedures before migrating to Satellite 6.8
================================================================================
disable active sync plans:
\ Total 0 sync plans are now disabled. [OK]
--------------------------------------------------------------------------------
Add maintenance_mode chain to iptables: [OK]
--------------------------------------------------------------------------------
Stop applicable services:
Stopping the following service(s):
rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflowd, elasticsearch, httpd, puppetserver, foreman-proxy
\ All services stopped [OK]
--------------------------------------------------------------------------------
Running preparation steps required to run the next scenarios
================================================================================
Check if tooling for package locking is installed: [OK]
--------------------------------------------------------------------------------
Running Migration scripts to Satellite 6.8
================================================================================
Setup repositories: [SKIPPED]
--------------------------------------------------------------------------------
Unlock packages: [OK]
--------------------------------------------------------------------------------
Update package(s) : [OK]
--------------------------------------------------------------------------------
Procedures::Installer::Upgrade: [FAIL]
Failed executing LANG=en_US.utf-8 satellite-installer, exit status 1:
Executing: foreman-maintain packages -h
Executing: foreman-maintain packages is-locked --assumeyes
Executing: foreman-maintain service start --only=postgresql
could not change directory to "/root"
/usr/share/foreman-installer/hooks/boot/03-foreman-maintain-extensions.rb:25:in `stop_services': wrong number of arguments (given 0, expected 1) (ArgumentError)
from /usr/share/foreman-installer/hooks/pre/30-el7_upgrade_postgresql.rb:4:in `postgresql_12_upgrade'
from /usr/share/foreman-installer/hooks/pre/30-el7_upgrade_postgresql.rb:20:in `block (4 levels) in load'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/hooking.rb:34:in `instance_eval'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/hooking.rb:34:in `block (4 levels) in load'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/hook_context.rb:16:in `instance_exec'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/hook_context.rb:16:in `execute'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/hooking.rb:51:in `block in execute'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/hooking.rb:49:in `each'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/hooking.rb:49:in `execute'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/kafo_configure.rb:424:in `run_installation'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/kafo_configure.rb:155:in `execute'
from /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:63:in `run'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/kafo_configure.rb:118:in `run'
from /opt/theforeman/tfm/root/usr/share/gems/gems/clamp-1.1.2/lib/clamp/command.rb:132:in `run'
from /opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/kafo_configure.rb:162:in `run'
from /usr/sbin/satellite-installer:8:in `<main>'
--------------------------------------------------------------------------------
Scenario [Migration scripts to Satellite 6.8] failed.
Actual results:
Upgrade failed.
Expected results:
upgrade should complete successfully.
Additional info:
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 (Important: Satellite 6.8 release), 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/RHSA-2020:4366