juju ssh uses old/invalid known_hosts data

Bug #1633554 reported by Joel Griffiths
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Invalid
Undecided
Unassigned

Bug Description

2.0-rc3-0ubuntu1~16.04.1~juju1

I've been deploying and destroying openstack (machines and applications) to the same Juju controller. Unfortunately, it doesn't look like the known_hosts data is getting cleaned up between runs. On the plus side, logging in once with the "--no-host-key-checks=true" option seems to fix the data.

me@myhost:~$ juju ssh glance/4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:Frpe++XF3hV8wNYVrkUzkRK/LB1+v5wq0SUrZC66CS8.
Please contact your system administrator.
Add correct host key in /tmp/ssh_known_hosts126800645 to get rid of this message.
Offending RSA key in /tmp/ssh_known_hosts126800645:7
  remove with:
  ssh-keygen -f "/tmp/ssh_known_hosts126800645" -R 192.168.86.3
RSA host key for 192.168.86.3 has changed and you have requested strict checking.
Host key verification failed.
me@myhost:~$

Revision history for this message
Joel Griffiths (joelgriffiths) wrote :

I think this is unrelated to Juju. It looks like a switch was sharing that IP with a container.

Changed in juju-core:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.