Skip to content

GitHub SSH public key missing from test-ibm-rhel8_arm_cross_container-x64-1 #3680

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

Closed
targos opened this issue Apr 15, 2024 · 5 comments · Fixed by #4051
Closed

GitHub SSH public key missing from test-ibm-rhel8_arm_cross_container-x64-1 #3680

targos opened this issue Apr 15, 2024 · 5 comments · Fixed by #4051
Labels

Comments

@targos
Copy link
Member

targos commented Apr 15, 2024

Related to #3678, as I redeployed all Docker containers on the host.

I disconnected the agent for now.

https://ci.nodejs.org/computer/test%2Dibm%2Drhel8%5Farm%5Fcross%5Fcontainer%2Dx64%2D1/

@richardlau
Copy link
Member

In https://ci.nodejs.org/job/node-cross-compile/configure there's some scripting that's supposed to add to the known_hosts:

grep -q ^$TEMP_REPO_SERVER ~/.ssh/known_hosts || (ssh-keyscan -t rsa $TEMP_REPO_SERVER >> ~/.ssh/known_hosts)

but looking at, e.g. https://ci.nodejs.org/job/node-cross-compile/nodes=cross-compiler-rhel8-armv7-gcc-10-glibc-2.28/47396/console, the attempt to git checkout is happening before that script is run.

I've manually added the key to the known_hosts file -- we're going to have to update it again when we migrate the tmp binary git repository from Equinix Metal (#3597).

@richardlau
Copy link
Member

Done the same for test-digitalocean-rhel8_arm_cross_container-x64-2.

@targos
Copy link
Member Author

targos commented May 1, 2024

In https://ci.nodejs.org/job/node-cross-compile/configure there's some scripting that's supposed to add to the known_hosts

Do you know why it's not added by Ansible?

@richardlau
Copy link
Member

No. I'm +1 for adding the known_host via Ansible to the machines that need to access the temporary binary git repo.

@richardlau
Copy link
Member

Hit this after I wiped and re-Ansibled the containers on the x64 Docker hosts.
e.g. https://ci.nodejs.org/job/node-cross-compile/52659/nodes=cross-compiler-rhel9-armv7-gcc-12-glibc-2.28/console

11:44:15  > git fetch --tags --force --progress -- [email protected]:binary_tmp.git +refs/heads/jenkins-node-test-commit-arm-fanned-e9ea0c6c86fc3e287d4d5591ad73d2cc79d61d69:refs/remotes/jenkins_tmp/_jenkins_local_branch # timeout=20
11:44:16 ERROR: Error cloning remote repo 'jenkins_tmp'
11:44:16 hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- [email protected]:binary_tmp.git +refs/heads/jenkins-node-test-commit-arm-fanned-e9ea0c6c86fc3e287d4d5591ad73d2cc79d61d69:refs/remotes/jenkins_tmp/_jenkins_local_branch" returned status code 128:
11:44:16 stdout: 
11:44:16 stderr: No ED25519 host key is known for 67.158.54.159 and you have requested strict checking.
11:44:16 Host key verification failed.
11:44:16 fatal: Could not read from remote repository.
11:44:16 
11:44:16 Please make sure you have the correct access rights
11:44:16 and the repository exists.

I've opened #4051 to add the entry to known_hosts. After running the updated docker-host playbook, https://ci.nodejs.org/job/node-cross-compile/52660/ (still running) has got past where it failed before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants