Comment 2 for bug 1646329

Hi John --

> (I presume that all of these machines actually have multiple
> network interfaces, and multiple potential addresses.)

In the case of what I presented above, 10.96.* are floating IP addresses, the openstack instance itself doesn't even have an interface bound to that IP. Openstack takes care of the routing above it.

10.100.* is the private IP range inside the cloud and does map to a real interface on the system. It also is another range I can see on my corporate VPN. The juju command line client seems to be dynamically calculating that it thinks it can connect to the 10.100.* range for these machines, maybe through a direct socket test or something. I don't know. I believe this to be where the bug lies. Since, it can connect the socket, but it's actually the *wrong* host.

So, going further, SSH attempts to connect to 10.100.* and it's the wrong machine (the one on the corporate VPN). This action attempts to verify the key, and that fails.