We did something similar to LFlo after a few rounds of attempting to recomplete the upgrade on ubuntu server.
We were confused because checking the remaining processes with the following command resulted in 0:
sudo gitlab-rails runner -e production 'puts Gitlab::BackgroundMigration.remaining'
Using the other combinations of commands didn’t seem to help, but this in exactly this order did solve it for us:
sudo gitlab-rake gitlab:background_migrations:finalize[CopyColumnUsingBackgroundMigrationJob,push_event_payloads,event_id,'[["event_id"]\, ["event_id_convert_to_bigint"]]']
sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart
We think @LFlo may have the better commands overall but we solved the problem just before his post was up, so didn’t get to try it.
Thank you to everyone on this thread. We would not have solved this without you and now we have more time to search for the appropriate replacement to Gitlab. Issues like these have caused us to look elsewhere.