I am not able to reproduce this.
juju ssh will now ssh to machine 0's public address directly, and then
proxy through that to machine 0's internal address. This is to support
environments where machines do not have unique public addresses (i.e.
with load balancing).
Can you please ssh to the machine directly and then check whether you
can resolve ip-172-31-21-242.us-west-2.compute.internal. If that does
not resolve, that would indicate a problem with EC2. If it *does*
resolve, then please try "juju ssh" again with --debug and attach the
output.
** Changed in: juju-core
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313785
Title:
Can't SSH with "juju ssh" command to EC2 instance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1313785/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
