Bug 1131547

Summary: [RFE] Schema upgrade warning
Product: Red Hat Satellite Reporter: Shannon Hughes <shughes>
Component: WebUIAssignee: Katello Bug Bin <katello-bugs>
WebUI sub component: Katello QA Contact: Katello QA List <katello-qa-list>
Status: CLOSED NOTABUG Docs Contact:
Severity: unspecified    
Priority: unspecified CC: mmccune, pgervase, shughes, xdmoon
Version: 6.0.3Keywords: FutureFeature
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-21 15:15:53 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    

Description Shannon Hughes 2014-08-19 14:36:58 UTC 
Description of problem:

Currently there is not a warning/notification after initial login if the schema needs to be upgraded/migrated. This was very helpful in Satellite 5 to know when the schema needed to be upgraded. Suggest we add this feature to Satellite 6
Comment 1 RHEL Program Management 2014-08-19 14:53:24 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Mike McCune 2014-08-21 15:15:53 UTC 
There are 2 reasons why this isn't an issue in Sat6:

1) When you upgrade the foreman RPM in the %post there is a command to migrate the schema to the latest version so if all goes well during an upgrade the schema is automatically upgraded

2) If the upgrade during %post fails you still are unable to run the server with mismatching database schema vs the code. With Satellite 6 we rely on Ruby on Rails's schema migration tools which will not let the server run when the schema mismatches the code. If you try to start httpd you will receive errors stating that you have 'pending migrations' that need to be run and the server will fail to start.