Project Export fails with Exhausted number of retries to export: ci_pipelines and Exhausted number of retries to export: merge_requests
Summary
This happens on a selfhosted Gitlab FOSS v17.8.0.
I am experiencing an issue when trying to export a project.
I have maintainer permissions on the project.
From the projects Settings -> General -> Advanced I click on the Project Export button.
After some time I receive an e-mail titled Project export error and the body reads:
Project <MY_PROJECT> couldn't be exported.
The errors we encountered were:
Exhausted number of retries to export: ci_pipelines
Exhausted number of retries to export: merge_requests
This happens all the time when I try to export now. But it used to work fine in the past. The last time I successfully exported is appr. 1-2 years ago.
I have Run housekeeping already but that did not change anything.
as a side note, there are other projects hosted on the same instance that have no problems with exporting.
Steps to reproduce
From the projects Settings -> General -> Advanced click on the Project Export button.
Example Project
What is the current bug behavior?
The export of the project is not possible and I am informed that it failed with the following errors:
Exhausted number of retries to export: ci_pipelines
Exhausted number of retries to export: merge_requests
What is the expected correct behavior?
The project is exported.
A tar archive is generated and a downloadlink made available via e-mail and/or the projects Settings -> General -> Advanced page.
Relevant logs and/or screenshots
I will gladly supply logs, but I don't know how to obtain them or what exactly is required.
Output of checks
Results of GitLab environment info
Components
GitLab version v17.8.0
GitLab Shell 14.39.0
GitLab Workhorse v17.8.0
GitLab API v4
GitLab KAS Unknown
Ruby 3.2.5p208
Rails 7.0.8.7
PostgreSQL (main) 14.15
PostgreSQL (ci) 14.15
Redis 7.0.15
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) ``` System information System: Debian 11 Current User: git Using RVM: no Ruby Version: 3.2.5 Gem Version: 3.5.23 Bundler Version:2.5.11 Rake Version: 13.0.6 Redis Version: 7.0.15 Sidekiq Version:7.2.4 Go Version: unknown GitLab information Version: 17.8.0 Revision: 22e6141a3e4 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 14.15 URL: https://ms-gitlab.ia-dev.softing.com HTTP Clone URL: https://ms-gitlab.ia-dev.softing.com/some-group/some-project.git SSH Clone URL: git@ms-gitlab.ia-dev.softing.com:some-group/some-project.git Using LDAP: yes Using Omniauth: no GitLab Shell Version: 14.39.0 Repository storages: - default: unix:/var/opt/gitlab/gitaly/gitaly.socket GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Gitaly - default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket - default Version: 17.8.0 - default Git Version: 2.47.0 ```
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)Checking GitLab subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 14.39.0 ? ... OK (14.39.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell-check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1 Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Reply by email is disabled in config/gitlab.yml Checking Incoming Email ... Finished Checking LDAP ... LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) User output sanitized. Found 100 users of 100 limit. Checking LDAP ... Finished Checking GitLab App ... Database config exists? ... yes Tables are truncated? ... skipped All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... 28/2 ... yes 64/3 ... yes 28/4 ... yes 12/8 ... yes 12/9 ... yes 64/10 ... yes 2/12 ... yes 61/14 ... yes 63/15 ... yes 62/18 ... yes 28/19 ... yes 21/20 ... yes 12/21 ... yes 5/22 ... yes 62/23 ... yes 64/24 ... yes 62/25 ... yes 62/26 ... yes 62/27 ... yes 62/28 ... yes 21/29 ... yes 62/30 ... yes 62/32 ... yes 28/33 ... yes 5/36 ... yes 37/37 ... yes 28/42 ... yes 61/43 ... yes 28/44 ... yes 28/45 ... yes 28/46 ... yes 32/49 ... yes 32/50 ... yes 32/52 ... yes 5/54 ... yes 32/55 ... yes 32/56 ... yes 37/57 ... yes 7/58 ... yes 38/60 ... yes 28/61 ... yes 28/62 ... yes 28/63 ... yes 28/64 ... yes 28/67 ... yes 28/68 ... yes 5/69 ... yes 63/70 ... yes 61/71 ... yes 28/72 ... yes 32/73 ... yes 63/74 ... yes 48/75 ... yes 65/76 ... yes 44/77 ... yes 50/78 ... yes 28/79 ... yes 63/80 ... yes 63/81 ... yes 63/82 ... yes 64/83 ... yes 64/84 ... yes 69/85 ... yes 63/86 ... yes 63/87 ... yes 63/88 ... yes 63/89 ... yes 63/90 ... yes 63/91 ... yes 80/92 ... yes 80/93 ... yes 80/94 ... yes 63/95 ... yes 28/96 ... yes 39/97 ... yes 63/98 ... yes 80/100 ... yes 80/101 ... yes 80/102 ... yes 80/103 ... yes 63/104 ... yes 63/107 ... yes 63/109 ... yes 80/110 ... yes 80/111 ... yes 63/112 ... yes 80/113 ... yes 63/114 ... yes 80/115 ... yes 80/116 ... yes 32/117 ... yes 80/119 ... yes 80/120 ... yes 80/121 ... yes 80/122 ... yes 63/123 ... yes 152/124 ... yes 5/125 ... yes 46/126 ... yes 37/127 ... yes 32/128 ... yes 156/129 ... yes 156/130 ... yes 64/131 ... yes 80/132 ... yes 152/133 ... yes 63/134 ... yes 63/135 ... yes 26/136 ... yes 26/137 ... yes 5/139 ... yes 63/140 ... yes 32/141 ... yes 5/142 ... yes 28/143 ... yes 5/144 ... yes 178/145 ... yes 32/147 ... yes 32/148 ... yes 32/149 ... yes 178/150 ... yes 178/152 ... yes 32/153 ... yes 155/155 ... yes 155/156 ... yes 155/157 ... yes 68/159 ... yes 179/161 ... yes 32/162 ... yes 63/163 ... yes 179/164 ... yes 80/165 ... yes 63/166 ... yes 28/167 ... yes 28/168 ... yes 7/169 ... yes 53/170 ... yes 80/171 ... yes 80/172 ... yes 365/173 ... yes 28/175 ... yes 5/176 ... yes 330/177 ... yes 63/179 ... yes 53/180 ... yes 32/181 ... yes 32/182 ... yes 178/183 ... yes 26/184 ... yes 28/185 ... yes 409/186 ... yes 63/187 ... yes 178/188 ... yes 28/189 ... yes 28/190 ... yes 428/191 ... yes 32/192 ... yes 435/193 ... yes 393/194 ... yes 28/195 ... yes 369/196 ... yes 461/197 ... yes 64/198 ... yes 61/199 ... yes 37/201 ... yes 28/202 ... yes 28/203 ... yes 63/204 ... yes 80/205 ... yes 80/206 ... yes 5/207 ... yes 5/208 ... yes 512/209 ... yes 512/210 ... yes 512/211 ... yes 512/212 ... yes 28/213 ... yes 63/214 ... yes 32/215 ... yes 461/217 ... yes 28/218 ... yes 28/219 ... yes 544/220 ... yes 5/221 ... yes 28/222 ... yes 36/223 ... yes 36/224 ... yes 36/225 ... yes 36/226 ... yes 179/227 ... yes Redis version >= 6.2.14? ... yes Ruby version >= 3.0.6 ? ... yes (3.2.5) Git user has default SSH configuration? ... yes Active users: ... 114 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Checking GitLab App ... Finished Checking GitLab subtasks ... Finished(we will only investigate if the tests are passing)