juju-info relation doesn't have public-address
Bug #1636139 reported by
Junien F
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
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_
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.
description: | updated |
tags: | added: canonical-is |
tags: | added: canonical-bootstack |
tags: | added: regression |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
To post a comment you must log in.
Note that after running juju config nrpe nagios_ address_ type=public, nrpe successfully gets his public IP addresses (presumably from unit-get)