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.
Bug 1880637 - [6.8] satellite-installer always runs upgrade steps
Summary: [6.8] satellite-installer always runs upgrade steps
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.8.0
Assignee: Amit Upadhye
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-18 20:37 UTC by Mike McCune
Modified: 2023-12-15 19:26 UTC (History)
3 users (show)

Fixed In Version: rubygem-foreman_maintain-0.6.13, foreman-installer-2.1.2.7,foreman-installer-2.1.2.7-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:09:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30898 0 Normal Closed Execute 'foreman-rake upgrade:run' after installer run 2021-01-25 06:38:07 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:09:24 UTC

Description Mike McCune 2020-09-18 20:37:52 UTC 
Satellite 6.8 and later has integrated upgrade checks that determines when the 'upgrade steps' should be run. Previous versions had the user needing to pass in the --upgrade flag to kick off the upgrade steps.


With 6.8, they appear to be run every time, which can take considerably longer than a standard run, especially in a customer environment:

# satellite-installer 
Package versions are locked. Continuing with unlock.
Preparing installation Done                                              
Executing: foreman-rake upgrade:run
=============================================
Upgrade Step 1/3: katello:correct_repositories. This may take a long while.
Processing Repository 1/1: repo1 (1)

=============================================
Upgrade Step 2/3: katello:correct_puppet_environments. This may take a long while.
=============================================
Upgrade Step 3/3: katello:clean_backend_objects. This may take a long while.
0 orphaned consumer id(s) found in candlepin.
Candlepin orphaned consumers: []
0 orphaned consumer id(s) found in pulp.
Pulp orphaned consumers: []
foreman-rake upgrade:run finished successfully!
...


# satellite-installer 
Package versions are locked. Continuing with unlock.
Preparing installation Done                                              
Executing: foreman-rake upgrade:run
=============================================
Upgrade Step 1/3: katello:correct_repositories. This may take a long while.
Processing Repository 1/1: repo1 (1)

=============================================
Upgrade Step 2/3: katello:correct_puppet_environments. This may take a long while.
=============================================
Upgrade Step 3/3: katello:clean_backend_objects. This may take a long while.
0 orphaned consumer id(s) found in candlepin.
Candlepin orphaned consumers: []
0 orphaned consumer id(s) found in pulp.
Pulp orphaned consumers: []
foreman-rake upgrade:run finished successfully!
...
Comment 4 Mike McCune 2020-09-21 16:05:20 UTC 
Split out the comment #2 into a new bz:

https://bugzilla.redhat.com/show_bug.cgi?id=1881150
Comment 5 Bryan Kearney 2020-09-22 16:03:23 UTC 
Upstream bug assigned to aupadhye
Comment 6 Bryan Kearney 2020-09-22 16:03:24 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30898 has been resolved.
Comment 10 Mike McCune 2020-09-30 14:37:36 UTC 
I'd recommend running foreman-maintain upgrade as well to verify that it *does* call the upgrade steps:

# foreman-maintain upgrade run -y --target-version=6.8.z --whitelist="repositories-validate,repositories-setup"

ensure that "foreman-rake upgrade:run" is run in the above as f-m is responsible for the upgrade execution.
Comment 12 Devendra Singh 2020-09-30 15:04:26 UTC 
Thanks Mike and Amit. 

Verified the forman-maintain upgrade and upgrade steps on 6.8.0 Snap17.
Comment 15 errata-xmlrpc 2020-10-27 13:09:06 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 (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
Note You need to log in before you can comment on or make changes to this bug.