Missing private address property from unit.info
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Amulet |
New
|
Wishlist
|
Unassigned |
Bug Description
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:
p d.sentry.
{'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:
Even though there is no "private address" persay, perhaps amulet could alias this on the local provider?
and on clouds, missing private-address is a far larger problem, as several charms reference the private address during the relationship lifecycle.
description: | updated |
description: | updated |
summary: |
- Missing private address property when testing on local provider + Missing private address property from unit.info |
description: | updated |
Changed in amulet: | |
importance: | Undecided → Wishlist |
When I juju ssh to tomcat/1 I was able to find a command that gives the private address: juju-hp- mbruzek- machine- 5:~$ juju-run tomcat/1 "unit-get private-address"
ubuntu@
10.4.189.86
However the equivalent command in Amulet does not produce the same output: unit['tomcat/ 1'].run( 'juju-run tomcat/1 "unit-get private-address"')
addr, rc = d.sentry.