[02:48] <mup> Bug #1532932 changed: Unable to bootstrap the lxd provider on vivid <2.0-count> <adoption> <juju-release-support> <juju-core:Fix Released> <https://launchpad.net/bugs/1532932>
[03:39] <mup> Bug #1571254 changed: Can't deploy multiseries charms in bundles <juju-core:Invalid> <https://launchpad.net/bugs/1571254>
[04:36] <mup> Bug #1544850 changed: unit-test failure: cloudImageMetadataSuite.TestFindMetadata <ci> <intermittent-failure> <test-failure> <unit-tests> <juju-core:Expired> <https://launchpad.net/bugs/1544850>
[04:36] <mup> Bug #1545216 changed: upgrade-mongo panic: juju home hasn't been initialized <ci> <mongodb> <test-failure> <upgrade-mongo> <juju-core:Expired> <https://launchpad.net/bugs/1545216>
[18:23] <mup> Bug #1571254 opened: Can't deploy multiseries charms in bundles <juju-core:New> <https://launchpad.net/bugs/1571254>
[22:05] <mup> Bug #1570963 changed: Model Controller refuses deployment with error code 400 <juju-core:New> <https://launchpad.net/bugs/1570963>
[23:51] <menn0> wallyworld: morning
[23:51] <wallyworld> hey
[23:51] <menn0> wallyworld: is it a known thing that juju no longer works on vivid
[23:52] <wallyworld> could be. vivid is out of support anyway
[23:52] <menn0> wallyworld: with master I now get:
[23:52] <menn0> $ juju bootstrap local lxd --config ~/canonical/juju-local.yaml --upload-tools
[23:52] <menn0> ERROR cannot find network interface "lxdbr0": route ip+net: no such network interface
[23:52] <menn0> ERROR invalid config: route ip+net: no such network interface
[23:52] <menn0> and there's no current lxd packages for vivid
[23:52] <wallyworld> not surprised
[23:52] <menn0> time to upgrade my laptop I guess
[23:52] <wallyworld> yep
[23:53] <menn0> I was holding out until xenial was final :)
[23:53] <wallyworld> i've been on xenial for a while, it works fine
[23:53] <menn0> wallyworld: next question, I'm looking at this replicaset voting bug. the issue seems to be that the mongodb on the new controller hosts can't find the replicaset config.
[23:54] <menn0> wallyworld: this familiar error from mongodb: replSet can't get local.system.replset config from self or any seed (EMPTYCONFIG)
[23:54] <menn0> wallyworld: the replicaset is fine on the bootstrap node though
[23:55] <wallyworld> joy
[23:55] <menn0> wallyworld: i'm trying to find where the new controller nodes get added to the replicaset and I haven't found it yet. any pointers?
[23:55] <wallyworld> i have nfi sorry :-(
[23:55] <wallyworld> oh wait
[23:56] <wallyworld> in state somewhere i think there is code to manage that, let me check
[23:56] <wallyworld> menn0: oh, and there's a peergrouper worker
[23:56] <wallyworld> i think that worker responds to the changes in state
[23:58] <wallyworld> menn0: addmachine.go in state has func (st *State) EnableHA
[23:58] <wallyworld> that sets up the desired replicaset state
[23:58] <wallyworld> and the worker then acts on it
[23:59] <menn0> wallyworld: ok, thanks. I'll keep digging from there.
[23:59] <wallyworld> sorry, that's all i know