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:

We should have some method, executed ($how?) that

* Checks the appropriate schema version per Satellite packages installed
* Checks to see what schema version is currently running on an existing satellite.

If a mismatch is encountered, a warning is thrown that reads something like

WARNING: Schema Mismatch! Satellite package indicate schema xxx.yyz should be used, you are using schema xxx.yyy.  Please follow appropriate upgrade steps from documentation"

$how - I am not sure.  Is it something you'd want to run periodically?  Almost certainly something that might be useful in foreman-debug, and perhaps `katello-service status` as well...

Rationale:

Doing something like

`katello-service stop && yum -y update && katello-service start` w/o running `katello-installer --upgrade` may put the system in a state of confusion.  We should be able to determine  (and perhaps check from time to time) whether everything is just so.

Satellite 5 has a batch job which loooks for out of date schemas. Perhaps we look at this type of model.

Per 6.3 planning, moving out non acked bugs to the backlog

this issue also has related bugs like https://bugzilla.redhat.com/show_bug.cgi?id=1459358

Per meeting with rjerrido We are going to focus on fixing https://bugzilla.redhat.com/show_bug.cgi?id=1459358 which is the root cause, not on this.