Gitlab Restore action should be Backward Compatible for backups made from same Major.Minor Version
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Description
If a backup was taken of a gitlab system running 8.14.2, it is not restorable on 8.14.3. This seems an unnecessary restriction, and likely to introduce delays when a system is down and you're trying to restore it and get it back online on a new server. Why can't the restore logic import the 8.14.2 postgres database backup and re-run the 8.14.2-8.14.3 migrations?
"Switching" versions in omnibus debian and ubuntu systems is certainly no picnic. How do I even do this manually? Pin some old version with apt-get pinning?
Suppose I want to have a test lab environment and "check out 8.14.3 before I move it into production", I want to import my current production backup from 8.14.2 and run before I run on 8.14.3 in production.
Proposal
Allow migrations from any same Major.Minor version to any Patch level (8.14.2 -> 8.14.3, allowed, restoring 8.13 backup on 8.14 not allowed).
Currently you get this error: Unpacking Backup... done Gitlab version mismatch. Your current Gitlab Version (8.14.4) differs from the Gitlab Version in the backup! Please switch to the following version and try again: version: 8.14.3.
Links / references
- Will add if found.