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:

The pre-upgrade script is not an integral part of the installation,
which can lead to being skipped, followed by running into another
issues related to this.

Steps to Reproduce:

1. refresh satellite repositories to the new version
2. run yum update -y, satellite-installer --upgrade

Actual results:

No pre-upgrade check is performed about sanity of the system

Expected results:

Pre-upgrade checks are run before proceeding with the upgrade. This
assumes https://bugzilla.redhat.com/show_bug.cgi?id=1184568 is
addressed, especially regarding rpm version locking, to minimize the
impact the initial yum update.

Pre-upgrade checks are run when running "foreman-maintain upgrade run", closing this BZ.