Skip to main content

Fix failed Bitbucket Code Manager code deployments in Puppet Enterprise

Nick Walker
  • Updated

Deploying code from a Bitbucket control repo fails when the r10k_remote parameter does not include ssh:// at the beginning of the SSH URL.

Error messages

Original exception: Failed to authenticate SSH session: Unable to send userauth-publickey request

Unable to determine current branches for Git source 'puppet' (/etc/puppetlabs/code-staging/environments) Original exception: Invalid credential type

These errors indicate that Code Manager is not able to connect to your Git repo.

Version and installation information

PE version: All supported
Installation type: Any

Solution

For Code Manager to pull code from your Bitbucket repos, the r10k_remote parameter value must include ssh:// at the beginning of the SSH URL, so that it matches the format of Bitbucket’s SSH URLs. For example: ssh://git@githost.domain.com/pup/puppet.git

  1. On the primary server, verify that your r10k_remote includes ssh:// by running cat /etc/puppetlabs/r10k/r10k.yaml.

  2. If the remote’s SSH URL does not include ssh://, update the value in either Hiera or the console.

Did this solve your problem?
1 out of 5 found this helpful

How can we improve this article?

2 comments

Date Votes
  • David Sandilands

    This appeared to be required on v2021.4.0 and Bitbucket self hosted and v7.16.0

    0
  • Suzie Baunsgard

    Thanks David, it sounds like this one would be pretty easy to update, I'll get in touch with you. 

    0

Please sign in to leave a comment.

Related articles