Problem to solve
I am encountering an issue when trying to fork a project on our GitLab instance. The operation fails with the following error message:
Every fork attempt has failed: Unable to fork project 300 for repository @hashed/6d/b6/6db6eb4af1e18ab81d3878e44672185d60ca8c988c9e2f7783de220735534c33 -> @hashed/98/3b/983bd614bb5afece5ab3b6023f71147cd7b6bc2314f9d27af7422541c6558389: Failed to create fork repository. Please try again.
In the server logs, I observe the following message associated with the error:
{"component":"gitaly.UnaryServerInterceptor","error":"repository not found","error_metadata":{"relative_path":"@hashed/c3/ea/c3ea99f86b2f8a74ef4145bb245155ff5f91cd856f287523481c15a1959d5fd1.git","storage_name":"default"},"grpc.code":"NotFound","grpc.meta.method":"FindDefaultBranchName","grpc.request.repoPath":"@hashed/c3/ea/c3ea99f86b2f8a74ef4145bb245155ff5f91cd856f287523481c15a1959d5fd1.git"}
It seems that the repository is not found, and there appears to be an issue with the storage path or Gitaly data integrity.
Here are the steps I have already taken:
- Checked project permissions – they appear to be correct.
- Attempted to fork using different browsers and devices, with the same result.
- Verified disk space and instance resources, everything seems normal.
- Consulted logs and error messages, indicating an issue with the repository and retrieving the default branch name.
I would appreciate your help in understanding and resolving this issue. Do you have any additional suggestions or steps I should take to resolve this error?
Thank you in advance for your assistance.
Steps to reproduce
Upgrade to v17.11.1-ee
Configuration
Versions
- Self-managed
-
GitLab.comSaaS - Dedicated