<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary After restoring a backup to your existing instance, you can no longer create new projects in GitLab unless you first clear the gitaly repository storage prior to the restore. It looks like this was caused a while back when we removed the step that deletes all gitaly repos from restore: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/18390 ### Steps to reproduce 1. Take a backup of a running instance 2. Create a new project and ensure it has a repository by adding a file 3. Restore the backup to the same instance 4. Try to create a new project ### Example Project From https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2553 we've been seeing this error for months whenever we run the tests multiple times against the same environment. (The environment does a restore of know state prior to running tests) ### What is the current *bug* behavior? Regardless of the name of your new project, it will try to use the hashed storage location based on project id, which will match the already existing hashed location from you had created after the backup/prior to the restore. ### What is the expected *correct* behavior? During the restore, old repositories should have been deleted from gitaly. ### Relevant logs and/or screenshots ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->