Comment 3 for bug 1256053

avoine pointed this bug to me on #juju when I was looking there for some help:

We have a production machine here using juju and lxc. The ip of the mysql and postgresql units changed, but the units related to them were not "informed" about that change. I mean, I forced some local charms to update and I could see in the log that they did a "relation-get" for the ip address, but it's still returning the old one.

Also, juju knows about the ip change since "juju status" returns me the correct public-address.

I could workaround that on some charms that doesn't override the "db config file" on every event. For some others, I had to fork the charm to "hardcode" the new ip (I don't need to say that this is unacceptable right?).

Like hazmat said above, juju is broken atm for me and many others. There's no workaround documented for this, nobody at #juju knows what to do (other than saying that "the fix is to destroy and recreate your environment" after I stated that I'm on a production machine). So, please, give this a high priority!