| 2014-03-17 22:51:41 |
Charles Butler |
bug |
|
|
added bug |
| 2014-03-17 22:53:01 |
Charles Butler |
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:
{'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. |
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.unit['nagios/0'].info
{'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. |
|
| 2014-03-18 05:24:22 |
Charles Butler |
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.unit['nagios/0'].info
{'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. |
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.unit['nagios/0'].info
{'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? |
|
| 2014-03-20 14:13:21 |
Charles Butler |
summary |
Missing private address property when testing on local provider |
Missing private address property from unit.info |
|
| 2014-03-20 14:14:04 |
Charles Butler |
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.unit['nagios/0'].info
{'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? |
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.unit['nagios/0'].info
{'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 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. |
|
| 2014-04-17 21:20:57 |
Marco Ceppi |
amulet: importance |
Undecided |
Wishlist |
|
