3 ms·
Literally going through this right now. Performing the upgrade from 13 to 14, following the required upgrade path. In the past, you could go from current versi
by cpitman 5y ago
Literally going through this right now. Performing the upgrade from 13 to 14, following the required upgrade path.
In the past, you could go from current version -> latest z release -> X.0 release of the next major -> latest minor release of Z. As long as gitlab completed the db migrations and came up, you were (relatively) ok to continue to the next upgrade.
Turns out 14 introduces a brand new upgrade failure case. Starting with 14, upgrades can include async db migrations that must complete before you continue upgrading. But once you start upgrading, it's too late, things are hosed, so now I'm falling back to a backup and starting over.