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:

Currently there is not a warning/notification after initial login if the schema needs to be upgraded/migrated. This was very helpful in Satellite 5 to know when the schema needed to be upgraded. Suggest we add this feature to Satellite 6

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

There are 2 reasons why this isn't an issue in Sat6:

1) When you upgrade the foreman RPM in the %post there is a command to migrate the schema to the latest version so if all goes well during an upgrade the schema is automatically upgraded

2) If the upgrade during %post fails you still are unable to run the server with mismatching database schema vs the code. With Satellite 6 we rely on Ruby on Rails's schema migration tools which will not let the server run when the schema mismatches the code. If you try to start httpd you will receive errors stating that you have 'pending migrations' that need to be run and the server will fail to start.