juju-info relation doesn't have public-address

Bug #1636139 reported by Junien Fridrick
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description


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

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 Fridrick (axino)
description: updated
Junien Fridrick (axino)
tags: added: canonical-is
JuanJo Ciarlante (jjo)
tags: added: canonical-bootstack
tags: added: regression
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0.1
Revision history for this message
Junien Fridrick (axino) wrote :

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

Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers