Bug 1459358

Summary:	[RFE] Have a warning in Satellite 6.x that a satellite upgrade is required if a yum update only was done
Product:	Red Hat Satellite	Reporter:	Kathryn Dixon <kdixon>
Component:	Upgrades	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikhil Kathole <nkathole>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3.0	CC:	bkearney, cdonnell, chrobert, fgarciad, hmore, inecas, jcallaha, jpathan, ktordeur, mbacovsk, mvanderw, rjerrido
Target Milestone:	Unspecified	Keywords:	FutureFeature, PrioBumpGSS
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-20 15:56:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	260381, 1115190, 1385841

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