[Bug 1313785] [NEW] Can't SSH with "juju ssh" command to EC2 instance.
Alex Lomov
lomov.as at gmail.com
Mon Apr 28 15:20:20 UTC 2014
Public bug reported:
After updating juju to 1.19.1-trusty-amd64 version I can't ssh with juju
command.
Here are details: https://gist.github.com/allomov/11374976
I am working with aws btw (ec2 environment type).
The error message is: "ssh: Could not resolve hostname ip-172-31-21-242
.us-west-2.compute.internal: Name or service not known".
Also I can SSH with standard SSH command:
"ssh -i ~/.juju/ssh/juju_id_rsa ubuntu at ec2-54-186-183-60.us-west-2.compute.amazonaws.com"
It seems that `juju ssh` tries to us private DNS name.
** Affects: juju (Ubuntu)
Importance: Undecided
Status: New
** Tags: ssh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in 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/ubuntu/+source/juju/+bug/1313785/+subscriptions
More information about the Ubuntu-server-bugs
mailing list