Error on Gitlab CE version 13.6 No repository

Hai Everyone. This is my first time i write bugs about gitlab CE. Right now i had a problem show No Repository on Gitlab Project eventhough i had the activity on it. So it’s like the repository can not be read or missplace by DB or paths. Before it, it only happen on my certain group but after i restart the server it goes to all the project that being place in our Gitlab CE on our premise. Server : Centos 8, Gitlab 13.6.1, Gitlab shell 13.13.0, PostgreSQL 11.9. First Problem: Merge request seems failed. And gitlab runner failed also. After restart all problem are happen on the server.

The Screenshot for it.
capture1

And i had try to follow some this instruction : A number of hashed_storage_project_migrate jobs failed / Projects show "The repository for this project does not exist" - #4 by maltem-za, other like Upgrade to GitLab 13.4.0 (b0481767fe4) killed all repositories - #24 by arhi.

It still not working for me. for Log in sidekiq: {"severity":"INFO","time":"2021-11-26T18:30:03.669Z","queue":"cronjob:pages_domain_ssl_renewal_cron","class":"PagesDomainSslRenewalCronWorker","retry":0,"version":0,"queue_namespace":"cronjob","jid":"b71dbec0399a6dfd36da5920","created_at":"2021-11-26T18:30:03.567Z","meta.caller_id":"Cronjob","correlation_id":"d0a01eb7c50d3da4d543dbc663ccd0bc","enqueued_at":"2021-11-26T18:30:03.571Z","pid":3415367,"message":"PagesDomainSslRenewalCronWorker JID-b71dbec0399a6dfd36da5920: done: 0.0828 sec","job_status":"done","scheduling_latency_s":0.014866,"redis_calls":2,"redis_duration_s":0.002169,"redis_read_bytes":2,"redis_write_bytes":206,"redis_queues_calls":2,"redis_queues_duration_s":0.002169,"redis_queues_read_bytes":2,"redis_queues_write_bytes":206,"db_count":1,"db_write_count":0,"db_cached_count":0,"duration_s":0.0828,"cpu_s":0.032892,"completed_at":"2021-11-26T18:30:03.669Z","db_duration_s":0.00701} {"severity":"INFO","time":"2021-11-26T18:31:02.191Z","queue":"cronjob:schedule_merge_request_cleanup_refs","class":"ScheduleMergeRequestCleanupRefsWorker","retry":0,"version":0,"queue_namespace":"cronjob","jid":"2d5df2d4656fd1e56077ceaa","created_at":"2021-11-26T18:31:02.189Z","meta.caller_id":"Cronjob","correlation_id":"af0ddb8175096f8c19f577a4cd1b51fa","enqueued_at":"2021-11-26T18:31:02.190Z","pid":3415367,"message":"ScheduleMergeRequestCleanupRefsWorker JID-2d5df2d4656fd1e56077ceaa: start","job_status":"start","scheduling_latency_s":0.001207} {"severity":"INFO","time":"2021-11-26T18:31:02.291Z","queue":"cronjob:schedule_merge_request_cleanup_refs","class":"ScheduleMergeRequestCleanupRefsWorker","retry":0,"version":0,"queue_namespace":"cronjob","jid":"2d5df2d4656fd1e56077ceaa","created_at":"2021-11-26T18:31:02.189Z","meta.caller_id":"Cronjob","correlation_id":"af0ddb8175096f8c19f577a4cd1b51fa","enqueued_at":"2021-11-26T18:31:02.190Z","pid":3415367,"message":"ScheduleMergeRequestCleanupRefsWorker JID-2d5df2d4656fd1e56077ceaa: done: 0.099369 sec","job_status":"done","scheduling_latency_s":0.001207,"redis_calls":3,"redis_duration_s":0.0014260000000000002,"redis_read_bytes":205,"redis_write_bytes":322,"redis_cache_calls":1,"redis_cache_duration_s":0.00097,"redis_cache_read_bytes":203,"redis_cache_write_bytes":110,"redis_queues_calls":2,"redis_queues_duration_s":0.000456,"redis_queues_read_bytes":2,"redis_queues_write_bytes":212,"extra.schedule_merge_request_cleanup_refs_worker.merge_requests_count":0,"db_count":1,"db_write_count":0,"db_cached_count":0,"duration_s":0.099369,"cpu_s":0.007013,"completed_at":"2021-11-26T18:31:02.291Z","db_duration_s":0.000587}

Let me know if someone had the same issue and finally can fix it. Thank you.

Warm Regards,

Melki

I have the exact same case.

What I have tried:

  • Migrate all legacy storage to hashes - no legacy storage found anymore
  • Clear registration tokes
  • Clear cache

Data is on the server but is not visible from UI as @melkisaputro0 point the picture “repository: does not exist”

I don’t see anything in the logs to point me to the root cause. Any suggestions …