-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Host Key Verification Failed (bitbucket) #142
Comments
Hi @spaquet Hmm... 🤔 Could you paste entire workflow file and error log? |
Here is the workflow file:
|
But looks like it went through this morning. |
🤔
|
answer to your question #1: the value I have in secret.KNOWN_HOSTS is the following: I extracted this value using the following command |
@shimataro workflow# This is a basic workflow to help you get started with Actions
name: CI
# Controls when the action will run. Triggers the workflow on push or pull request
# events but only for the master branch
on:
push:
branches: [ master ]
pull_request:
branches: [ master ]
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# This workflow contains a single job called "build"
build:
name: Test Bitbucket Clone
# The type of runner that the job will run on
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
# Add ssh key to access Bitbucket
- name: Install SSH key
uses: shimataro/ssh-key-action@v2
with:
key: ${{ secrets.BITBUCKET_CHAT }} # your private key
known_hosts: ${{ secrets.KNOWN_HOSTS }}
- run: git clone [email protected]:xxxretrorocketxxx/test-bucket.git ; echo `cat ~/.ssh/known_hosts`
- run: echo `cat ./test-bucket/README.md` known_hostsConfigure SSH and two-step verification | Bitbucket Cloud | Atlassian Support
実行結果known_hostsに余計な文字を入れている等しか思いつかないです。 |
I'm actually using an Access Key (Read Only) as this information has to be shared with external providers and services. But that should not affect the KNOWN_HOSTS. Logs for
|
But logs for It's like
|
@retrorocket could you try with an access key (https://support.atlassian.com/bitbucket-cloud/docs/add-access-keys/) and I will try removing node js as it's the main difference between our workflows. |
Same error after removing node.js from the test. |
@retrorocket 報告ありがとうございます!マジで謎ですね。。。 @spaquet Thank you for the details.
Is there some other causes? 🤔 |
@shimataro agree. I tried @retrorocket code, and it fails the same way.
|
@spaquet Could you test it in the following steps:
If it works, the cause may be in your project (workflow file) or bitbucket repo. Check the difference between your project/repo and mine carefully. If fails, please share the forked repo with me. |
Thanks @shimataro I will review it tomorrow. |
I've had to
|
Some further detail.. Branch - https://github.com/jacktuck/test-clone-bitbucket-in-actions/tree/test Notice
The latter is hashed because |
Hi, @jacktuck It seems to be better to append LF to |
Thanks @shimataro. Just had a look at the merged PR - I don't think it's necessary to prepend a newline. Did you have a chance to see #150 ? |
@jacktuck |
I have come across a very similar issue, and was confused because I was using the same configuration in another repo with no issues. Maybe it working for other people, but in my case, it's impossible for me to set |
I have a package hosted in a private bitbucket repository and I'm using your script the following way:
- name: Install SSH key uses: shimataro/ssh-key-action@v2 with: key: ${{ secrets.BITBUCKET_ACCESS_KEY }} known_hosts: ${{ secrets.KNOWN_HOSTS }}
and KNOWN_HOST value is:
bitbucket.org ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAubiN81eDcafrgMeLzaFPsw2kNvEcqTKl/VqLat/MaB33pZy0y3rJZtnqwR2qOOvbwKZYKiEO1O6VqNEBxKvJJelCq0dTXWT5pbO2gDXC6h6QDXCaHo6pOHGPUy+YBaGQRGuSusMEASYiWunYN0vCAI8QaXnWMXNMdFP3jHAJH0eDsoiGnLPBlBp4TNm6rYI74nMzgz3B9IikW4WVK+dc8KZJZWYjAuORU3jc1c/NPskD2ASinf8v3xnfXeukU0sJ5N6m5E8VLjObPEO+mN2t/FZTMZLiFqPWc/ALSqnMnnhwrNi2rbfg/rd/IpL8Le3pSBne8+seeFVBoGqzHM9yXw==
However,
yarn install
always fails with "Host Key Verification Failed".(I went reading #56 but still the same)
The text was updated successfully, but these errors were encountered: