$ sudo gitlab-rake gitlab:env:info
System information
System: Ubuntu 20.04
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.7.5p203
Gem Version: 3.1.4
Bundler Version:2.2.33
Rake Version: 13.0.6
Redis Version: 6.2.6
Sidekiq Version:6.4.0
Go Version: unknown
GitLab information
Version: 14.10.0-ee
Revision: ad109bc62af
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 12.7
URL: https://gitlab.xxxxxxx.com
HTTP Clone URL: https://gitlab.xxxxxxx.com/some-group/some-project.git
SSH Clone URL: [email protected]:some-group/some-project.git
Elasticsearch: no
Geo: no
Using LDAP: no
Using Omniauth: yes
Omniauth Providers:
GitLab Shell
Version: 13.25.1
Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories
GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell
sudo gitlab-rake db:migrate
and it said it was expecting the project namespaces backfill task to be marked complete but it wasn’t, and to run this command:
sudo gitlab-rake gitlab:background_migrations:finalize[ProjectNamespaces::BackfillProjectNamespaces,projects,id,‘[null,“up”]’]
Running gitlab-ctl reconfigure then suceeded.
Migdsb, you are my hero. I had exactly the same problem with the same error messages migrating from 14.8.2 to 14.10.0 and your solution worked perfectly for me. I cannot thank you enough!
Keep yourself safe!
I am glad I found this post, as it let us successfully complete our upgrade and reconfigure!
I won’t go over the whole story, but I will back-link to the gitlab.com issue that I found first, where I described what we went through:
In my case, what I do is overwrite the boot command with tail -f /dev/null and once the container is up and running, I run an interactive bash.
In order to interact with gitlab-ctl you must start the service: /opt/gitlab/embedded/bin/runsvdir-start
Once up and running you can run the solution.
First of all, you should run the gitlab-ctl reconfigure command since by overwriting the boot command you are recreating the container.
Once the reconfigure has completed with error, you can confirm that it is the migration error by running the command: gitlab-rake db:migrate
If the error is the command, run the command gitlab-rake gitlab:background_migrations:finalize[ProjectNamespaces::BackfillProjectNamespaces,projects,id,’[null,“up”]’]" to finish the task.
Once complete, you can run gitlab-ctl reconfigure again and it should work fine.
Hope this can help you.
Thanks, this was exactly what I was looking for and moved me one step ahead. Only that I am getting a very strange error now when attempting to start the Gitlab services -
/opt/gitlab/embedded/bin/runsvdir-start: line 37: /proc/sys/fs/file-max: Read-only file system
Must be something related to our docker environment, I reckon. Test setup is docker-desktop under Windows, I don’t dare to move to production setup that is running docker under ArchLinux. I will have to investigate further.
Would be really cool if that problem could be solved in the next Gitlab version, as we would rather like to focus on our measurement device software development.
For my case, from 14.9.3 to 14.10.0 on a Docker installation, this worked for me, after migration failed with the command (yours may be a little different):
docker run --detach
–hostname {your_subdomain}
–publish 80:80
–name gitlab
–restart unless-stopped
–volume $HOME/docker/volumes/gitlab/config:/etc/gitlab:Z
–volume $HOME/docker/volumes/gitlab/logs:/var/log/gitlab:Z
–volume $HOME/docker/volumes/gitlab/data:/var/opt/gitlab:Z
–shm-size 256m
gitlab/gitlab-ce:14.10.0-ce.0
docker exec gitlab bash
gitlab-rake db:migrate
gitlab-rake gitlab:background_migrations:finalize[ProjectNamespaces::BackfillProjectNamespaces,projects,id,’[null,“up”]’]
gitlab-rake db:migrate
gitlab-ctl reconfigure
docker restart gitlab
Hope it helps to fellow colleagues in the Docker ecosystem . . .
@migdsb Thanks, saved my day! 
On Ubuntu 18.04 I had to type the rake command a little bit different:
gitlab-rake gitlab:background_migrations:finalize[ProjectNamespaces::BackfillProjectNamespaces,projects,id,'[null\,"up"]']
Note the backslash after the null!
