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 1459358 - [RFE] Have a warning in Satellite 6.x that a satellite upgrade is required if a yum update only was done
Summary: [RFE] Have a warning in Satellite 6.x that a satellite upgrade is required if...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Nikhil Kathole
URL:
Whiteboard:
: 1316246 (view as bug list)
Depends On:
Blocks: 260381 GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker CEE_Sat6_Top_BZs, GSS_Sat6_Top_Bugs
TreeView+ depends on / blocked
 
Reported: 2017-06-06 23:33 UTC by Kathryn Dixon
Modified: 2022-03-13 14:18 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-20 15:56:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1184568 0 high CLOSED [RFE] If the update process for Satellite 6 requires additional manual steps, the process should include a script to do ... 2022-03-13 13:55:55 UTC
Red Hat Bugzilla 1245771 0 high CLOSED [RFE] Method by which to check for schema version discrepancies for debugging purposes. 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1512600 0 medium CLOSED [RFE] Implement a yum version lock type of protections against upgrades 2023-12-15 15:59:51 UTC
Red Hat Issue Tracker SAT-4993 0 None None None 2021-09-09 12:22:49 UTC
Red Hat Knowledge Base (Article) 2053393 0 None None None 2017-09-07 21:15:11 UTC
Red Hat Knowledge Base (Solution) 1169393 0 None None None 2017-08-16 13:14:09 UTC
Red Hat Knowledge Base (Solution) 1280993 0 None None None 2017-08-16 13:17:58 UTC
Red Hat Knowledge Base (Solution) 1571383 0 None None None 2017-08-16 13:14:43 UTC
Red Hat Knowledge Base (Solution) 1579883 0 None None None 2017-08-16 13:13:09 UTC
Red Hat Knowledge Base (Solution) 2059173 0 None None None 2017-08-16 13:13:44 UTC
Red Hat Knowledge Base (Solution) 2146501 0 None None None 2017-08-16 13:12:25 UTC
Red Hat Knowledge Base (Solution) 2525481 0 None None None 2017-08-16 13:17:07 UTC
Red Hat Knowledge Base (Solution) 2531831 0 None None None 2017-08-16 13:17:32 UTC

Internal Links: 1184568 1245771 1512600

Description Kathryn Dixon 2017-06-06 23:33:51 UTC 
Description of problem:

Satellite upgrades are a two step process. Since customers are at a high risk for not running both, we are asking that after a yum update on the satellite a warning is shown that they must complete the upgrade or the Satellite will not be functional.


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. yum update on satellite 6
2. do not run the katello-installer --upgrade or satellite-installer --scenario satellite --upgrade


Actual results: Satellite is half updated and will have multiple failures in hammer ping


Expected results: a banner or warning on the satellite page that says "finish the upgrade with satellite-installer --scenario satellite --upgrade"


Additional info: This is a feature gap between Satellite 5 and Satellite 6. If a update is done on Satellite 5 a banner will come across the screen and state please perform a database schema upgrade.

See also https://bugzilla.redhat.com/show_bug.cgi?id=1184568
Comment 1 Craig Donnelly 2017-06-06 23:40:46 UTC 
It would be nice to implement this based on the foreman schema_migrations table as a versioning system, but that would require there to be a insert into that table for every update to the Satellite version.

Personally, I would propose that like Satellite 5, we create a new table to accurately track the versions of database and when the `--upgrade` occurred that lead to the version of schema being inserted into the database.

We could then make accurate use of the version in the "schema_version" table to relate to the version of a package, for instance the 'satellite' package, perhaps a comparison with the expected 'foreman' and 'tfm-rubygem-katello' packages as well to then say, hey: the three package/plugin versions do not match the latest inserts in the "schema_version" table of the database, you need to perform a `--upgrade`!

We could show this in the Satellite WebUI (notify), forcefully send an email to the administrator accounts, or any other notification mechanism.
Comment 3 Ivan Necas 2017-06-08 08:23:56 UTC 
I would suggest, as the first step, to implement this into the incomming foremain-maintain health checking tool. The idea is this would be the GOTO tool before even reaching to the support. The next step would then be to get the periodic run of the health checking tool to produce corresponding notifications in the web ui.
Comment 4 Bryan Kearney 2018-06-22 13:24:45 UTC 
*** Bug 1316246 has been marked as a duplicate of this bug. ***
Comment 5 Bryan Kearney 2019-12-20 15:56:17 UTC 
This was delivered in Satellite 6.6
Note You need to log in before you can comment on or make changes to this bug.