Bug #15215
closedsmithfarm cannot ssh to test nodes, and therefore cannot teuthology-kill
0%
Description
I can schedule suites, but I cannot kill them. When I run, for example:
teuthology-kill -m multi -r smithfarm-2016-03-19_09:18:11-upgrade:hammer-x-hammer-pr-8052---basic-multi
I get the following output: http://paste2.org/4ENBIZyD
I guess it's because the public ssh key in /home/smithfarm/.ssh/id_rsa.pub
is not present in /home/ubuntu/.ssh/authorized_keys
on the test nodes.
Updated by David Galloway about 8 years ago
- Category set to Test Node
- Status changed from New to In Progress
- Assignee set to David Galloway
Updated by David Galloway about 8 years ago
- Status changed from In Progress to Need More Info
Nathan,
Is this the key in your pubkey file or do you need me to add another one?
Updated by David Galloway about 8 years ago
Are you running teuthology-kill from your workstation or teuthology.front?
Updated by Zack Cerza about 8 years ago
I don't see any ssh keys at all in smithfarm@teuthology.front:~/.ssh
Updated by Nathan Cutler about 8 years ago
- Status changed from Need More Info to Fix Under Review
I was confused, as usual. So if I understand correctly, I needed to generate an SSH keypair to use from teuthology.front to connect further to the infrastructure. Opened PR https://github.com/ceph/keys/pull/22 for this purpose.
Updated by David Galloway about 8 years ago
- Status changed from Fix Under Review to Resolved
Merged https://github.com/ceph/keys/pull/22
Your new pubkey will be added to your user as ansible gets run across the testnodes.