Comment 0 for bug 1293831

Revision history for this message
Charles Butler (lazypower) wrote : Missing private address property when testing on local provider

The output of what i can receive from a unit does not contain private-address as a callable property.

When introspecting with ipdb, i see the following:

{'public-address': '10.0.3.47', 'service': 'nagios', 'subordinates': {'nagios-sentry/0': {'public-address': '10.0.3.47', 'agent-state': 'started', 'agent-version': '1.17.5.1', 'upgrading-from': 'local:precise/nagios-sentry-0', 'open-ports': ['9001/tcp']}}, 'unit': '0', 'agent-state': 'started', 'agent-version': '1.17.5.1', 'machine': '4', 'open-ports': ['80/tcp']}

Even though there is no "private address" persay, perhaps amulet could alias this?

This may belong as a bug against juju-local , and please close this bug as invalid if that is the case and I will report it elsewhere.