juju status of units report private address (172.x.x.x) instead of public fqdn

[David Fischer]

> juju --version

1.16.4-saucy-amd64

Example:

> juju status

environment: dev
machines:
  "0":
    agent-state: started
    agent-version: 1.16.4
    dns-name: ec2-54-194-136-26.eu-west-1.compute.amazonaws.com
    instance-id: i-c723928b
    instance-state: running
    series: raring
    hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
  "1":
    agent-state: started
    agent-version: 1.16.4
    dns-name: ec2-54-194-113-27.eu-west-1.compute.amazonaws.com
    instance-id: i-f02392bc
    instance-state: running
    series: raring
    hardware: arch=amd64 cpu-cores=2 cpu-power=500 mem=1740M root-disk=8192M
  "2":
    agent-state: started
    agent-version: 1.16.4
    dns-name: ec2-54-194-116-206.eu-west-1.compute.amazonaws.com
    instance-id: i-25a38c6a
    instance-state: running
    series: raring
    hardware: arch=amd64 cpu-cores=2 cpu-power=500 mem=1740M root-disk=8192M
  "3":
    agent-state: started
    agent-version: 1.16.4
    dns-name: ec2-54-194-99-114.eu-west-1.compute.amazonaws.com
    instance-id: i-3620917a
    instance-state: running
    series: raring
    hardware: arch=amd64 cpu-cores=2 cpu-power=500 mem=1740M root-disk=8192M
  "4":
    agent-state: started
    agent-version: 1.16.4
    dns-name: ec2-54-194-116-220.eu-west-1.compute.amazonaws.com
    instance-id: i-05975d4a
    instance-state: running
    series: raring
    hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
  "5":
    agent-state: started
    agent-version: 1.16.4
    dns-name: ec2-54-194-117-0.eu-west-1.compute.amazonaws.com
    instance-id: i-2e209162
    instance-state: running
    series: raring
    hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
  "6":
    agent-state: started
    agent-version: 1.16.4
    dns-name: ec2-54-194-134-201.eu-west-1.compute.amazonaws.com
    instance-id: i-39568076
    instance-state: running
    series: raring
    hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
services:
  oscied-orchestra:
    charm: local:raring/oscied-orchestra-30
    exposed: true
    relations:
      api:
      - oscied-webui
      publisher:
      - oscied-publisher
      storage:
      - oscied-storage
      transform:
      - oscied-transform
    units:
      oscied-orchestra/0:
        agent-state: started
        agent-version: 1.16.4
        machine: "1"
        open-ports:
        - 80/tcp
        - 5672/tcp
        - 27017/tcp
        public-address: ec2-54-194-113-27.eu-west-1.compute.amazonaws.com
  oscied-publisher:
    charm: local:raring/oscied-publisher-30
    exposed: true
    relations:
      publisher:
      - oscied-orchestra
    units:
      oscied-publisher/0:
        agent-state: started
        agent-version: 1.16.4
        machine: "5"
        open-ports:
        - 80/tcp
        public-address: ec2-54-194-117-0.eu-west-1.compute.amazonaws.com
  oscied-storage:
    charm: local:raring/oscied-storage-30
    exposed: false
    relations:
      peer:
      - oscied-storage
      storage:
      - oscied-orchestra
      - oscied-transform
      - oscied-webui
    units:
      oscied-storage/0:
        agent-state: started
        agent-version: 1.16.4
        machine: "2"
        open-ports:
        - 111/tcp
        - 24007/tcp
        - 24009/tcp
        public-address: ec2-54-194-116-206.eu-west-1.compute.amazonaws.com
  oscied-transform:
    charm: local:raring/oscied-transform-30
    exposed: false
    relations:
      storage:
      - oscied-storage
      transform:
      - oscied-orchestra
    units:
      oscied-transform/0:
        agent-state: started
        agent-version: 1.16.4
        machine: "3"
        public-address: ec2-54-194-99-114.eu-west-1.compute.amazonaws.com
  oscied-webui:
    charm: local:raring/oscied-webui-30
    exposed: true
    relations:
      api:
      - oscied-orchestra
      storage:
      - oscied-storage
    units:
      oscied-webui/0:
        agent-state: started
        agent-version: 1.16.4
        machine: "6"
        open-ports:
        - 80/tcp
        public-address: 172.31.26.177

[Curtis Hovey (sinzui)]

This issue may release to bug 1258240 where the private address is first available and it is used instead of the public address. I understand the fix for the other bug may address this issue if the root issue reporting address changes.

[Curtis Hovey (sinzui)]

Hi Andrew. what are your thoughts about the root cause of this bug? I am inclined to test this issue when the hp ip/boostrap bug is fixed to see if we can treat this bug as a duplicate.

[David Fischer (david-fischer-ch)]

Thank you all for your work.

[Andrew Wilkins (axwalk)]

@sinzui: I'm not 100% sure, but I don't *think* they're the same (though they may be similar). My understanding is that the unit's address will come from its machine. The machine's addresses should be updated by the "addressupdater" worker, which fires off periodically.

I think it'd be good to get rogpeppe's input here, as he did the addressupdater work IIRC.

[Guillaume Martres (smarter)]

Any news on this?
Thanks.

[Andrew Wilkins (axwalk)]

@smarter: no progress on diagnosis of the original issue, however the implementation details of unit addresses have changed recently. In 1.18, I expect this bug will be fixed.

[Ian Booth (wallyworld)]

Fixed in 1.18