Comment 4 for bug 1646329

Revision history for this message
Alex Kang (thkang0) wrote :

I have the same problem as above the bug.

I am using juju 2.0.2-xenial-amd64 and deploy openstack with MAAS 2.1.2

At first step, it looked fine to deploy machines and openstack.

But it comes up with ssh bug when I try to connect one of nova-compute machines

juju --debug ssh nova-compute/0
13:39:32 INFO juju.cmd supercommand.go:63 running juju [2.0.2 gc go1.6.2]
13:39:32 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "--debug", "ssh", "nova-compute/0"}
13:39:32 INFO juju.juju api.go:72 connecting to API addresses: [10.10.1.50:17070]
13:39:32 INFO juju.api apiclient.go:530 dialing "wss://10.10.1.50:17070/model/59543072-caf8-40d4-8bf9-2f7de34aa536/api"
13:39:32 INFO juju.api apiclient.go:466 connection established to "wss://10.10.1.50:17070/model/59543072-caf8-40d4-8bf9-2f7de34aa536/api"
13:39:32 DEBUG juju.juju api.go:263 API hostnames unchanged - not resolving
13:39:32 DEBUG juju.cmd.juju.commands ssh_common.go:263 proxy-ssh is false
13:39:32 INFO juju.network hostport.go:274 dialed "192.168.122.1:22" successfully
13:39:32 DEBUG juju.cmd.juju.commands ssh_common.go:367 using target "nova-compute/0" address "192.168.122.1"
13:39:32 DEBUG juju.utils.ssh ssh.go:292 using OpenSSH ssh client
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 ECDSA key sent by the remote host is
SHA256:EBOclSl+7NMqLKwKzzq7j3ihwnP8l9Rp5SVMtcyAprk.
Please contact your system administrator.
Add correct host key in /tmp/ssh_known_hosts843183779 to get rid of this message.
Offending RSA key in /tmp/ssh_known_hosts843183779:7
  remove with:
  ssh-keygen -f "/tmp/ssh_known_hosts843183779" -R 192.168.122.1
ECDSA host key for 192.168.122.1 has changed and you have requested strict checking.
Host key verification failed.
13:39:32 DEBUG juju.api monitor.go:35 RPC connection died
13:39:32 INFO cmd supercommand.go:465 command finished

and juju shows status of nova-compute/0

nova-compute/0 unknown lost 5 10.10.1.56

but it is trying to connect my local virbr interface (192.168.122.1)