Bug 696663

Summary:	make sure the customer runs schema-upgrade script when upgrading to sat541
Product:	Red Hat Satellite 5	Reporter:	Tomas Lestach <tlestach>
Component:	Upgrades	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED ERRATA	QA Contact:	Martin Minar <mminar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	540	CC:	jhutar, mkoci, mminar, slukasik
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	satellite-schema-5.4.0.12-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-17 02:43:22 UTC	Type:	---
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:	677501

Description Tomas Lestach 2011-04-14 14:58:55 UTC

Description of problem:
If a customer upgrades from sat540+ to sat541, it's necessary for him to run the schema-upgrade script. If he just runs 'yum update' he might get a newer application code without the necessary db schema changes.

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

Expected results:
An e-mail that simply checks rpm output of satellite-schema with rhn-schema-version and emails if different. cron.daily seems to be a good place.

Comment 1 Milan Zázrivec 2011-04-15 08:17:33 UTC

New daily cron job which will remind by email in case a satellite-schema
upgrade is available (part of satellite-schema package):

satellite.git SATELLITE-5.4: a3e4e774951d4fc9e94e50c12c65a9539087c349

Comment 5 Šimon Lukašík 2011-06-06 09:31:38 UTC

Verified in stage with satellite-schema-5.4.0.13-1

Testing procedure:
 - all the upgrade scenarios contains a schema upgrade
 - the cronjob is installed
 - the mail is sent & received, when a versions mismatch

Comment 6 Clifford Perry 2011-06-17 02:43:22 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

https://rhn.redhat.com/errata/RHEA-2011-0875.html