Gitlab returns "No Repository" even though the repository exists in the git_data_dirs path(s)

Question

Summary

After backup and migrate, some repositories return "No Repository" error in the web console, and cannot be cloned. The repository is verified to exist as specified in the git_data_dirs folder.

As a test I can clone the "No repository" project from the repositories/ folder directly, so there seems to be nothing wrong with the repo itself.

Steps to reproduce

Not sure how it can be reproduced, but here are the steps i've gone through:

• backup project on primary server
• restore tarball on new server
• go to project path in the new server's web dashboard, and get "No Repository".

The steps I've taken to diagnose the problem. Say the project is called myapp/myapp.foo.git:

• Go to http://newgitserver.local/myapp/myapp.foo.git
• Get "No Repository"

• Look at git_data_dirs in /etc/gitlab/gitlab.rb:

  git_data_dirs({ "default": { "path": "/var/opt/gitlab/git-data"}, "silo": {"path": "/mnt/reposbackup/git-data"} })

• Note that my project is available in both the folders: /var/opt/gitlab/git-data/repositories/myapp/myapp.foo.git AND /mnt/reposbackup/git-data/repositories/myapp/myapp.foo.git

• Try restarting the server - same result
• Try sudo gitlab-ctl reconfigure - same result
• Try restarting the runsv services: sudo systemctl restart gitlab-runsvdir - same result

I've also looked at the database and the 'projects.repository_storage' value seems correct. Even changing it to 'default' vs 'silo' (which is my alternate dir) does not seem to work.

I'm trying to understand how gitlab makes a determination of where the repository is, since the check for repo-path seems to be what's failing.

SOLUTION

Run sudo gitlab-rake cache:clear once the migration is completed.

Answer 1

You likely need to clear the Redis cache. Try running the following command:

sudo gitlab-rake cache:clear

Rake is a general maintenance command that not a lot of users know about, as you'd never need it if you are using the pure cloud offering. It really only applies to on-premise offerings.

Sometimes the issue is purely a network connectivity issue. You can also use rake to check that as well:

sudo gitlab-rake gitlab:tcp_check[ibm.com,80]

Answer 2

Make sure that the repos are owned by git and then clear the cache.

chown -R git /var/opt/gitlab/git-data/repositories
gitlab-rake cache:clear