Error occurred while running Task 'Checkout Default Repository(1)

Question

Anyone seen this before?

Caused by: com.atlassian.bamboo.plugins.git.GitCommandException: command ['C:\Program Files\Git\cmd\git.exe' submodule update --init --recursive] failed with code 128. Working directory was [D:\Bamboo\Build\AAAA-V70-BP]., stderr:
Warning: Permanently added '[127.0.0.1]:50231' (RSA) to the list of known hosts.
471f1917-2db7-497c-8b18-3f41500e9f0f@127.0.0.1: Permission denied (password).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Unable to fetch in submodule path 'XXX'; trying to directly fetch 120a9635f4051b1d00f02de3048f0b77dde6e4f8:
Warning: Permanently added '[127.0.0.1]:50231' (RSA) to the list of known hosts.
471f1917-2db7-497c-8b18-3f41500e9f0f@127.0.0.1: Permission denied (password).
fatal: Could not read from remote repository.

Note: these are plans with submodules!

We see these kind of errors on multiple agents at irregular intervals and with multiple buildplans.

So for a single buildplan, the builds are successful and others fail due to the failure mentioned above.

Paul Moors · Answer

Hi Eduardo,

Thank you for your reply.

I will do all the checks you mentioned to verify if the configuration is not interfering with the connection.

Still I'm a bit confused at this moment: when I enable 'Force Clean Build' option with the 'Source Code Checkout' task, the problem seems solved.
Can you explain that?

Eduardo Alvarenga · Answer

Hello @Paul Moors

Welcome to the Atlassian Community!

The error relates to the SSH connection to the Git repository. As Bamboo uses a local SSH-PROXY, it will first connect to 127.0.0.1 at a random port, and then a Java thread will connect to the final Git Server.

In your case, it appears you have some SSH configuration that may be interfering with the connection. Please check your $HOME/.ssh/config and validate that no special configurations are causing the issue.

It's possible that the Git repository designated as a submodule doesn't have the credentials that Bamboo uses to connect to the main repository, as explained here. To address this, you should check your default Repository Settings in Bamboo, navigate to Advanced Options, and then copy and add the provided SSH public key to the Repository configuration used as a submodule. If you're using a version of Bamboo earlier than 8.1.1, you can find an alternative setup in this KB.

* Checkout of Git repository with submodules failed in Bamboo.

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--