Git-LFS auto-merge fails with BAMBOO-SSH-PROXY: [User session has timed out idling after 120000 ms.] and/or lfs.locksverify error
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
When working with Bitbucket server and Bamboo, the automerging and push process will fail if git lfs is enabled.
Diagnosis
Environment
Bamboo (any current version, tested in 6.1).
Bitbucket server (tested on 5.2.2)
Git lfs client v2.1.1
Diagnostic Steps
After configuring auto merging with one of the 2 options in Bamboo (Branch Auto Updater or Gatekeeper), git lfs will try to cal auto-merge and conclude with a push, failing with the following error:
1
2
3
4
5
6
7
Warning: Permanently added '[127.0.0.1]:55529' (RSA) to the list of known hosts.
BAMBOO-SSH-PROXY: [User session has timed out idling after 120000 ms.]
Remote "ssh://09bebce1-32dd-4553-b215-1836bfe809ea@127.0.0.1:55529/repo/repo.git" does not support the LFS locking API. Consider disabling it with:
$ git config 'lfs.https://127.0.0.1/repo/repo.git/info/lfs.locksverify' false
Error scanning for Git LFS files in "3fb9ec8950a9e0c03e293203185a9542008d5895"
fork/exec /usr/lib/git-core/git: cannot allocate memory
Cause
Two errors are presented here:
1
git config 'lfs.https://127.0.0.1/repo/repo.git/info/lfs.locksverify' falseThis is caused by a Bitbucket limitation explained here: https://jira.atlassian.com/browse/BSERV-9623. The link (and the description of the error) explains how to work around this issue.
1
BAMBOO-SSH-PROXY: [User session has timed out idling after 120000 ms.]This error happens due to a bug in the GIT LFS client version, which is v2.1.1.
Solution
Resolution
Update git lfs to version 2.2.0+ to fix this issue.
Was this helpful?