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.
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
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
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