Skip to content
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

ssh connection problems #188

Open
jonazpiazu opened this issue Jan 29, 2018 · 6 comments
Open

ssh connection problems #188

jonazpiazu opened this issue Jan 29, 2018 · 6 comments

Comments

@jonazpiazu
Copy link
Contributor

When running the job kinetic_rosdistro-cache I get several errors over the ssh connection:

16:40:23 SSH: Connecting from host [xxx]
16:40:23 SSH: Connecting with configuration [rosdistro_cache] ...
16:40:23 SSH: Caught exception [Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [rosdistro_cache]. Message [Auth fail]]] Sleeping for [5,000]ms before trying again
16:40:28 SSH: Connecting with configuration [rosdistro_cache] ...
16:40:28 SSH: Caught exception [Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [rosdistro_cache]. Message [Auth fail]]] Sleeping for [5,000]ms before trying again
16:40:33 SSH: Connecting with configuration [rosdistro_cache] ...

I have noticed that both in the agent and in the repo , the authorized_keys file is not correctly deployed. As jenkins is the one making the connection, it should be located in /home/jenkins-agent/.ssh/ , while I find it deployed in the root's folder /root/.ssh/

@jonazpiazu
Copy link
Contributor Author

I can confirm that copying the file authorized_keys and setting the proper ownership (chown jenkins-agent.jenkins-agent /home/jenkins-agent/.ssh/authorized_keys) fixes the ssh connection error.

@nuclearsandwich
Copy link
Contributor

Thanks for the report. If you're comfortable with puppet, you're welcome to submit a PR updating the config. IF not, I'll add and test it to upcoming work.

@jonazpiazu
Copy link
Contributor Author

Sorry that my puppet knowledge tends to zero ...

@jonazpiazu
Copy link
Contributor Author

But regarding the labels, I would say it affects to agent and repo, but not master.

@nuclearsandwich
Copy link
Contributor

nuclearsandwich commented Jan 29, 2018

I would say it affects to agent and repo, but not master.

I misunderstood which host you applied the workaround for. Fixed.

@gavanderhoorn
Copy link
Contributor

Is this related to ros-infrastructure/buildfarm_deployment_config#29?

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

No branches or pull requests

3 participants