Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,033
Community Members
 
Community Events
168
Community Groups

Unable to checkout for aws codecommit

We upgraded to Bamboo version 8.1.9 build 80117 today.

Everything looks fine, except for the Bamboo Plans which uses AWS CodeCommit repositories. See error below

com.atlassian.bamboo.plugins.git.GitCommandException:

command [/usr/local/bin/git ls-remote ssh://2656138a-fec9-43dd-935f-8f3265a2cbd7@127.0.0.1:42394/v1/repos/cws-ecomm-api] failed with code 128. Working directory was [/app/atlassian/atlassian-bamboo/temp]., stderr: Authenticating remote session failed stdout: Warning: Permanently added '[127.0.0.1]:42394' (RSA) to the list of known hosts. BAMBOO-SSH-PROXY: [SSH proxy tried to connect to [APKAZTUTIMPY4ZVUUNOM@git-codecommit.eu-west-1.amazonaws.com/52.95.120.42:22]: and failed due to the following error: [Authenticating remote session failed]: KeyExchange signature verification failed for key type=ssh-rsa] fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.


Tried cloning one of the repo using Bamboo server manually using the existing keys and also newly created keys and I was able to clone it

However, when I tried to update the ssh key in the repository definition in Bamboo, saved the setting and tried to test the connection I am having the issue shown bellow.

 

Warning: Permanently added '[127.0.0.1]:42394' (RSA) to the list of known hosts.
BAMBOO-SSH-PROXY: [SSH proxy tried to connect to [APKAZTUTIMPY7CHRVUVX@git-codecommit.eu-west-1.amazonaws.com/52.95.112.172:22]: and failed due to the following error: [Authenticating remote session failed]: KeyExchange signature verification failed for key type=ssh-rsa]
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

 

1 answer

Hello @Rainielle Maglaya,

Thank you for reaching out to Atlassian Support and also here at Community!

This issue is being tracked by the following bug:

We encourage you to add yourself as a watcher to be kept informed about the state of the bug moving forward. If our development team updates the ticket, you'll be notified via email.

Sincerely,

Eduardo Alvarenga
Atlassian Support APAC

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events