Github user aledsage commented on the issue:
https://github.com/apache/brooklyn-server/pull/355
I presume that the problem you're hitting is that there is a VM being
provisioned that gets multiple (private) IPs, but that the corresponding entity
advertises its sensor for "host.name" with the wrong IP.
I think we should look more at the call-chain for where we're calling
`getPublicHostname()` from, and figure out if there is a better way of doing
this. For example, if we're already checked reachability to decide on an IP
then we could prefer that (rather than repeating the check).
Also, the semantics of subnet hostname and public hostname are unclear when
dealing with private networks: it's unclear whether the IP should be the one
reachable from Brooklyn. I guess if we're talking "public" then that's probably
as good an indication as any.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
