@DerAstronaut usually problems occur during the upgrades for one of a few reasons:
- Depending on which version you are running, an upgrade path needs to be followed so that you don’t miss certain db migrations, or other important things like when postgres is upgraded in one of the gitlab releases. From 12.9.3 what I had, I had to go to 12.10.14 first before 13.0.0 and a whole host of others to get to the latest version successfully.
- After each upgrade, you need to check that no migrations are currently running - the command can be found in the gitlab upgrade guide. These need to finish before continuing the upgrade process.
So, without knowing what you did during your upgrade, it could be that you missed an important version which required some migrations to occur, or, the upgrade process was continued when migrations were still running on the server - these can take a while, most are quick, but others could take hours.
I played it safe, as I wasn’t sure of the upgrade path from 12.9.3, I basically upgraded every single release from 12.9.3 to the latest upgrade. So all remaining 12.x.x release, all 13.0.x releases, all 13.1.x releases, and so on. As you can imaging it was time consuming doing around 50 or more package upgrades, and finished in two days, since I ran 25 per day. Depending on server specs, an upgrade process can take 5 - 10 mins for each package, not including if we have to wait for migrations to finish.
And usually once each upgrade has finished, I wait for gitlab to start itself up which can take a couple of minutes, and then visit my URL in the browser. If it loads, great all looking good. I check the repositories are still listing files, I use
gitlab-ctl status to make sure all services are running, and then continue the upgrade process. You could always do git pull and push as well if you wish to verify this in addition to what I wrote above.
Generally, if you follow those steps, you shouldn’t have an issue with the upgrade process. Oh, and one more thing, just make sure the VPS also has enough ram to run gitlab as well. This could potentially also have negative effects on upgrades if something cannot finish running. Minimum requirements show 4GB, but I think 8GB is far better for a more stable system.