Bug #6363
closedHost key errors in the nightlies
100%
Description
log: ubuntu@teuthology:/a/teuthology-2013-09-20_01:35:04-upgrade-small-next-testing-basic-vps/7253
2013-09-20T03:00:03.174 DEBUG:teuthology.task.internal:connecting to ubuntu@vpm116.front.sepia.ceph.com
2013-09-20T03:00:03.341 ERROR:teuthology.run_tasks:Saw exception from tasks.
Traceback (most recent call last):
File "/home/teuthworker/teuthology-next/teuthology/run_tasks.py", line 31, in run_tasks
manager = run_one_task(taskname, ctx=ctx, config=config)
File "/home/teuthworker/teuthology-next/teuthology/run_tasks.py", line 19, in run_one_task
return fn(**kwargs)
File "/home/teuthworker/teuthology-next/teuthology/task/internal.py", line 190, in connect
keep_alive=True),
File "/home/teuthworker/teuthology-next/teuthology/orchestra/connection.py", line 46, in connect
timeout=60,
File "/usr/lib/python2.7/dist-packages/paramiko/client.py", line 321, in connect
raise BadHostKeyException(hostname, server_key, our_server_key)
BadHostKeyException: Host key for server vpm116.front.sepia.ceph.com does not match!
seeing a lot of such errors in the nightlies lately, where the test fails to run.
This seems to happen all the time, when someone accidentally tries to ssh to vpm machine from teuthology as user teuthworker, removing the conflicting entry resolves the issue.
We need to find a way to get rid of this.
Updated by Sandon Van Ness over 10 years ago
My vote is adding the following to ~teuthworker/.ssh/config:
Host *
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null
It should prevent this from happening its simply a question of whether or not this would effect anything on teuthology. AFAIK teuthology just stores the keys in the db and verifies them with paramiko anyway and it doesnt really use known_hosts to begin with but when entries do get put in their by someone manually ssh'ing while su'd to the teuthworker user it does break things so paramiko does atleast look at known_hosts for key verification even though I haven't seen it add keys when it connects.
Updated by Sandon Van Ness over 10 years ago
And this happened with vpm116 yet again. Different key this time. I am curious what is running ssh commands from teuthworker outside of teuthology... to the same vps.
Updated by Sandon Van Ness about 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Zack and I went at this from a few sides and this hasn't come up again.