ace> hopefully the fix is correct, so we never have the issue again
<sinzui> voidspace: abentley  might want to bu you beer
<voidspace> sinzui: hah
<voidspace> sinzui: no, I meant the fix that wallyworld has allegedly committed to 1.25 and master
<voidspace> not that I've done it
<voidspace> he hasn't committed it to 1.24 though, which is where we need it
<sinzui> voidspace: CI tests 1.20 upgrades to the candidate we test. abentley is updating the test to use upload-tools as needed. so your change is exactly what we are looking to test
<voidspace> right
<voidspace> so we need 1.20 and onwards fixed really
<voidspace> might be worth abentley pinging wallyworld about it
<sinzui> voidspace: yeah, we can do a 1.20 release if we need to. We just need to make several jobs non-voting before hand to check to deal with unsupported features
<voidspace> sinzui: although a 1.20 to 1.22 upgrade works I believe, 1.24 is the problematic version
<voidspace> sinzui: so just fixing 1.22 on would suffice
<voidspace> which is one less release at least
<sinzui> voidspace: we can test/release 1.22 at anytime. we have special PPA setup for its distrubution too
<voidspace> cool
<voidspace> I've added a comment to the bug
<mup> Bug #1510651 opened: Agents are "lost" after terminating a state server in an HA env <juju-core:New> <https://launchpad.net/bugs/1510651>
<voidspace> frobware: our proposed fix for getting rid of ignore-machine-addresses can't work
<voidspace> frobware: it's effectively what we're already doing
<voidspace> frobware: we might need to prefer a provider fallback address over an exact match machine address
<voidspace> frobware: I'll discuss it with dimiter tomorrow
<voidspace> frobware: meanwhile, the fix for containers has landed on 1.25 and is landing on master
<voidspace> frobware: and I've tested on both 1.25 and master
<abentley> voidspace: pong
<voidspace> abentley: unping
<voidspace> abentley: it's about the wily issue and upgrades
<voidspace> abentley: see the above conversation if you want... :-)
<voidspace> 