** Changed in: juju-core
Status: Fix Committed => Fix Released
--
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.
** Changed in: juju-core
Status: In Progress => Fix Committed
--
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.
T
** Branch linked: lp:~axwalk/juju-core/lp1313785-ssh-useproxy
--
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 manag
Thanks, I hadn't noticed the version difference. I can also reproduce
the issue with a 1.18.2 server.
--
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
** Changed in: juju-core
Status: Triaged => In Progress
** Changed in: juju-core
Assignee: (unassigned) => Andrew Wilkins (axwalk)
--
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/b
I have confirmed that juju 1.18.2 can ssh into my one of my units, but
juju 1.19.1 cannot:
$ juju status
environment: juju-ci3
machines:
"0":
agent-state: started
agent-version: 1.18.2
dns-name: ec2-54-84-244-38.compute-1.amazonaws.com
instance-id: i-59745278
instance-state:
That sounds like a regression, we certainly need to be able to fall back to
the old method of connecting if the server doesn't support proxying the
request.
John
=:->
On Tue, May 6, 2014 at 5:12 PM, Curtis Hovey
wrote:
> This issue might be that the 1.19.1 client cannot ssh to 1.18.1/2
> serve
This issue might be that the 1.19.1 client cannot ssh to 1.18.1/2
server. I cannot use juju ssh to get to Juju CI using this combination.
--
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/13
** Changed in: juju-core
Importance: Critical => High
--
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 not
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 mach
** Changed in: juju (Ubuntu)
Status: New => Triaged
--
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 n
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Changed in: juju-core
Milestone: None => 1.19.2
** Changed in: juju-core
Importance: High => Critical
--
You received this bug notification because you are a member of Ubu
** Also affects: juju-core
Importance: Undecided
Status: New
--
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.
13 matches
Mail list logo
