Pages Deploy job failing with "Exclusive lease for object_storage_migrate:Ci::JobArtifact is already taken"
Summary
I am using Gitlab Pages to generate a site using Jekyll. Lately, the deploy job has been constantly failing with this error message: Exclusive lease for object_storage_migrate:Ci::JobArtifact is already taken
.
The artifacts size is rather large (over 500 Mio) so I assume this is related. I have no intention of reducing that size, the site is an image gallery so the size will only grow as time passes. On the other hand, the problem only appeared 5 days ago, and did not follow any modification either on the repo contents or on my Gitlab setup (no upgrade or config change around that date).
My Gitlab instance is a Gitlab CE 14.4.2. I am using object storage for the artifacts, with a Minio server on a different machine (with 10 Mo/s bandwidth between Gitlab and Minio). Pages storage uses the default configuration (the configuration values are not present in my gitlab.rb
).
This causes 2 problems:
- The site is not refreshed, and new posts don't appear
- I receive a total of 5 email notifications: one "fixed pipeline" when the
pages
job succeeds and 4 "failed pipeline" for each failedpages:deploy
I have already tried unchecking "Skip outdated deployment jobs" which I saw mentioned in another issue with the same problem, however it did not work.
Steps to reproduce
- Create a project for Gitlab Pages
- Add files until the artifacts archive produced by the
pages
job exceeds 500 Mio
What is the current bug behavior?
pages:deploy
fails 4 times in a row, preventing the site from being updated and causing the notifications to be sent
Upon hovering the deploy job card in the Pipeline view, a bubble appears with the error message "Exclusive lease for object_storage_migrate:Ci::JobArtifact is already taken"
What is the expected correct behavior?
pages:deploy
succeeds, the site is correctly refreshed and no email notification is sent
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 20.04 Current User: git Using RVM: no Ruby Version: 2.7.4p191 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.6 Redis Version: 6.0.16 Git Version: 2.33.0. Sidekiq Version:6.2.2 Go Version: unknown GitLab information Version: 14.4.2 Revision: 1ce86e92f81 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 12.7 URL: https://[REDACTED] HTTP Clone URL: https://[REDACTED]/some-group/some-project.git SSH Clone URL: git@[REDACTED]:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers: github, gitlab, bitbucket, twitter, google_oauth2 GitLab Shell Version: 13.21.1 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 13.21.1 ? ... OK (13.21.1) Running /opt/gitlab/embedded/service/gitlab-shell/bin/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: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... 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? ... skipped (no tmp uploads folder yet) Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 4/9 ... yes 4/13 ... yes 4/14 ... yes 4/15 ... yes 4/16 ... yes 4/19 ... yes 8/21 ... yes 11/22 ... yes 11/23 ... yes 11/24 ... yes 11/25 ... yes 4/26 ... yes 11/27 ... yes 11/28 ... yes 4/31 ... yes 5/32 ... yes 11/33 ... yes 4/34 ... yes 13/40 ... yes 13/41 ... yes 14/42 ... yes 14/43 ... yes 14/44 ... yes 14/45 ... yes 15/47 ... yes 16/48 ... yes 4/49 ... yes 4/50 ... yes 4/51 ... yes 4/52 ... yes 16/53 ... yes 4/54 ... yes 11/55 ... yes 19/56 ... yes 20/57 ... yes 4/58 ... yes 4/59 ... yes 20/60 ... yes 11/61 ... yes 4/62 ... yes 4/63 ... yes 16/64 ... yes 4/65 ... yes 25/66 ... yes 4/68 ... yes 4/69 ... yes 11/71 ... yes 4/72 ... yes 11/73 ... yes 4/74 ... yes 4/75 ... yes 11/76 ... yes Redis version >= 5.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.4) Git version >= 2.33.0 ? ... yes (2.33.0) Git user has default SSH configuration? ... yes Active users: ... 8 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