Comment 4 for bug 1313785

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: running
    series: precise
    hardware: arch=amd64 cpu-cores=1 cpu-power=200 mem=3840M root-disk=8192M
  "6":
    agent-state: started
    agent-version: 1.18.2
    dns-name: ec2-54-86-142-177.compute-1.amazonaws.com
    instance-id: i-fa1903da
    instance-state: running
    series: precise
    hardware: arch=amd64 cpu-cores=2 cpu-power=650 mem=17408M root-disk=8192M
services:
  jenkins:
    charm: cs:precise/jenkins-9
    can-upgrade-to: cs:precise/jenkins-10
    exposed: true
    units:
      jenkins/0:
        agent-state: started
        agent-version: 1.18.2
        machine: "6"
        open-ports:
        - 8080/tcp
        public-address: ec2-54-86-142-177.compute-1.amazonaws.com

$ juju ssh jenkins/0
nc: getaddrinfo: Name or service not known
ssh_exchange_identification: Connection closed by remote host
ERROR subprocess encountered error code 255