juju-info relation doesn't have public-address

[Junien F]

Hi,

It looks like the juju-info relation doesn't have the public-address in the relation data anymore. This is problematic for charms that rely on it, for example nrpe with export_nagios_checks to true.

Steps to reproduce :
juju deploy cs:ubuntu
juju deploy cs:nrpe
juju add-relation ubuntu nrpe
juju run --unit nrpe/0 "relation-get -r general-info:0 - ubuntu/0"

Expected result :
private-address: 192.168.x.x
public-address: 1.2.3.4

Actual result :
private-address 192.168.x.x

juju 2.0.0-trusty-amd64

At least Azure and AWS appear to be impacted. Note that "juju run --unit ubuntu/0 'unit-get public-address'" returns the expected public address.

[Junien F (axino)]

Note that after running juju config nrpe nagios_address_type=public, nrpe successfully gets his public IP addresses (presumably from unit-get)

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.