On Wed, May 27, 2015 at 3:04 PM, Vasiliy Tolstov <[email protected]> wrote:
> 2015-05-27 3:17 GMT+03:00 Kapil Thangavelu <[email protected]>: > > > > relation settings only propagates private ip, which juju sets, and its > imo > > bug that juju should update and invoke relation change hook if it changes > > and has the previously set value (ie. thus works w/ proxy charms). at > least > > that was my summary going in and out of the that monster thread. at the > > moment juju doesn't update the addresses it set, but it will invoke > > config-changed when addresses changed afaicr but effectively zero charms > are > > ready to handle that. > > > > re public address, unit-get public-address makes it available as info > into > > the charm, but there isn't a mechanism per-se to modify the address or > > notify wrt to that information. > > > > you can manually modify the relation settings that convey private/public > > address info with juju run ala > > https://gist.github.com/kapilt/a61efcb4eaef9e685397 > > > > might be helpful if you could clarify the context that the public address > > changed and how its causing a problem with a concrete example. > > > Thanks, if my units for unit-get public-address always return > 127.0.0.1 what can i do? > P.S. state server address really 127.0.0.1, but server have other > public addresses ipv4 and ipv6 > Which version of Juju are you running? If it's semi recent, it *should* pick up all of the addresses on the machine and choose something that is not a private network address (and if it's not, I'd suggest logging a bug).
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
