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'

I just got the exact same issue on my own project, but it occurred after a normal push. Here is the error message on the first and subsequent pushes:

GitLab_error.txt

I don't know how to fix it, as I don't have access to the file system on GitLab.

mentioned in issue gitlab-com/support-forum#448 (closed)

mentioned in issue #19974 (closed)

There could be many things going on at GitLab.com repository backend:

• git fsck is running this will create a lock file and it really takes some time to finish
• git gc is running this will also create a lock file and it can take up some time as well
• NFS cache is still seeing the lock file since we are using cache=positive option with NFS.

Anyway, until we are moved to CephFS and still on NFS, you should just retry a couple of times since it is self healing.

moved to gitlab#3940

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in merge request !14785