Gitlab Omnibus Background Migrations Continually Fail on Upgrade

upgrade gitlab

The solution was found here: https://forum.gitlab.com/t/jira-integration-page-is-not-opening-in-gitlab-integration-has-stopped-working/36247

Specifically, after running the upgrade, and executing gitalb-ctl reconfigure, run through the following steps:

sudo gitlab-rake db:migrate:status

and make sure all migrations are up. If they are, run the following two commands:

sudo gitlab-rake db:migrate:redo VERSION=20200123155929
sudo gitlab-rake db:migrate:redo VERSION=20200127090233

Related

Ways to find VPN client address on RDP connection
Google cloud loadbalancer Http-to-https with multiple backends
Timeouts on Cloud SQL and other external services when using NAT + IP Masquerade on GKE
AWS-CLI - Find ELB by Name tag
Is there any way of viewing, in AWS, what ips in a subnet have been allocated?
How can I modify an auth_token of a redis cluster if the redis engine version is below 5.0.5?
How can switch to an EC2 instance role locally as a user?
How can we limit and give space in after each special character in bash script output?
Ubuntu Firewall blocking DNS requests to VMWARE guest with outbound traffic rules added and stateful matching done
Openldap and nfserver, both work although /home/user cannot be created unless I log into the nfserver first with new ldapusers
How can a create a connection between two KVM private network? [closed]
Posftwd is double counting emails when used with Posftix and amavis