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 <cur...@canonical.com> wrote: > 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 subscribed to juju- > core. > 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 > -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
