Bug #33281
closed
Restore should run "upgrade" steps after the data restore finished
Description
When you restore a backup, you need to restore "the same version", however, this is not as easy as it sounds as you might have a 2.5.2 backup, but restoring to a 2.5.3 as that's the latest release available.
This can result in certain upgrade steps not being run and thus diverge application and database.
To ease that scenario, f-m should run the installer after the config files and databases etc are in place and whatever else "upgrade" steps are defined (for foreman before 2.1 you'd run installer --upgrade and be done, in newer foremans you run installer and then foreman-rake upgrade:run if Katello is present)
To save time, we could look at the metadata of the backup, and only add the upgrade steps if the versions don't match.
Updated by Evgeni Golov about 3 years ago
Ref: https://docs.theforeman.org/nightly/Administering_Red_Hat_Satellite/index-foreman-el.html#restoring-from-a-full-backup_admin says " The Foreman instance must have the same host name, configuration, and be the same minor version (X.Y) as the original system." (emphasis mine), so it's not even required to have the same .z
Updated by Evgeni Golov almost 3 years ago
- Has duplicate Bug #33307: Restore should run the installer after data was restored added
Updated by The Foreman Bot almost 3 years ago
- Status changed from New to Ready For Testing
- Assignee set to Evgeni Golov
- Pull request https://github.com/theforeman/foreman_maintain/pull/553 added
Updated by Evgeni Golov almost 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_maintain|6089aa60271d1036604c135c89ec5263da5d198b.