Forced push fails due to locking issue on the server
I had the following issue twice now. It happens if you make to forced pushes in a row. It seems it cannot lock the repo because the previous git process is still working on it or failed to give back the log.
This happens on gitlab.com @jacobvosmaer Could you look into the looks if you see something suspicious?
Counting objects: 13, done. Delta compression using up to 4 threads. Compressing objects: 100% (13/13), done. Writing objects: 100% (13/13), 1.54 KiB | 0 bytes/s, done. Total 13 (delta 11), reused 0 (delta 0) remote: error: cannot lock ref 'refs/heads/api-delete-tag': Unable to create '/var/opt/gitlab/git-data/repositories/gitlab-org/gitlab-ce.git/refs/heads/api-delete-tag.lock': File exists. remote: remote: If no other git process is currently running, this probably means a remote: git process crashed in this repository earlier. Make sure no other git remote: process is running and remove the file manually to continue. To https://gitlab.com/gitlab-org/gitlab-ce.git ! [remote rejected] api-delete-tag -> api-delete-tag (failed to update ref) error: failed to push some refs to 'https://gitlab.com/gitlab-org/gitlab-ce.git'