[00:53] <axw> babbageclunk: I am now
[00:56] <babbageclunk> axw: have you bootstrapped on the maas that thumper pointed us at?
[00:56] <axw> babbageclunk: nay
[00:57] <axw> babbageclunk: still working through basic lxc to lxd conversion bits, was intending to move onto LXC/LXD on MAAS next
[00:57] <babbageclunk> axw: d'oh - I can't get to the nodes that it deploys, and I was hoping you'd know how.
[00:58] <axw> babbageclunk: I'll try it straight after standup
[00:58] <babbageclunk> ok
[01:20] <thumper> wallyworld: got a few minutes for a chat?
[01:23] <axw> babbageclunk: hmm yeah not sure how we're supposed to get to that network. trying to sleuth
[01:27] <babbageclunk> axw: Can we use lxc on xenial?
[01:28] <axw> babbageclunk: in what capacity?
[01:28] <axw> babbageclunk: I've done some testing of lxc-to-lxd on xenial hosts
[01:28] <babbageclunk> axw: I was just about to try bootstrapping 1.25 locally.
[01:29] <babbageclunk> axw: Actually I've got a 1.9 vmaas, I'll use that
[01:50] <axw> babbageclunk: can you please take a look at https://github.com/juju/1.25-upgrade/pull/11? you can pretty much ignore the first commit I think, it's just a copy of the lxc-to-lxd script from the lxc repo
[02:24] <babbageclunk> axw: hmm, bootstrapped ok, but I keep getting this error when I try to deploy anything: ERROR cannot retrieve charm "cs:trusty/mysql-38": cannot get archive: cannot open archive data for cs:trusty/mysql-38: blob not found
[02:25] <babbageclunk> axw: any ideas?
[02:26] <axw> babbageclunk: hmm nope sorry
[02:28] <blahdeblah> babbageclunk: turn on your work IRC :-P
[02:36] <thumper> menn0: ping?
[02:37] <menn0> thumper: pong
[02:37] <thumper> 1:1?
[02:37] <menn0> thumper: sorry, coming
[02:45] <babbageclunk> axw: oops - I think I got silently disconnected after asking that (I tried turning off my vpn). S
[02:46] <babbageclunk> axw: did you reply?
[02:46] <axw> babbageclunk: I did, but only to say I don't know why that would happen
[02:46] <babbageclunk> axw: ah bums. Not having much luck today.
[02:59] <axw> babbageclunk: would you please review https://github.com/juju/1.25-upgrade/pull/11 (ignore first commit, it's just a copy from lxc repo) and https://github.com/juju/1.25-upgrade/pull/12 (ignore first two commits, they're from #11)
[03:20] <babbageclunk> axw: sure
[03:51] <babbageclunk> axw: delightfully a reboot seems to have fixed my deploy problem
[03:51] <axw> babbageclunk: cool.
[04:11] <babbageclunk> axw: reviewed, sorry for holdup
[04:11] <axw> babbageclunk: np, thank you
[04:13] <axw> babbageclunk: is there a reason we should not error out if any of the "stop-agents" or "start-agents" SSH commands fail?
[04:13] <axw> babbageclunk: atm just warning, feels like it should be a failure...
[04:14] <babbageclunk> axw: Not that I can see - I'd say we definitely want it to be failure.
[04:14] <axw> babbageclunk: cool, will change it later today. going for a ride in a moment
[08:09] <menn0> jam: ping
[22:32] <mwhudson> veebers: are you the correct person to goad into doing sru verification of the juju-mongodb update?
[22:33] <mwhudson> veebers: https://bugs.launchpad.net/ubuntu/xenial/+source/juju-mongodb3.2/+bug/1699354
[22:33] <mup> Bug #1699354: upgrade juju-mongodb3.2 to 3.2.15 <verification-needed> <verification-needed-xenial> <verification-needed-zesty> <juju-mongodb3.2 (Ubuntu):Fix Released by mwhudson> <juju-mongodb3.2 (Ubuntu Xenial):Fix Committed by mwhudson> <juju-mongodb3.2 (Ubuntu Yakkety):Won't Fix by mwhudson>
[22:33] <mup> <juju-mongodb3.2 (Ubuntu Zesty):Fix Committed by mwhudson> <https://launchpad.net/bugs/1699354>
[22:39] <veebers> mwhudson: Either me or balloons have done some in the past. I think we would just need to re-do some SRU testing jobs to do so.
[22:48] <mwhudson> veebers: in any case, can i leave it with you? :)
[23:07] <veebers> mwhudson: sure, we'll get back to you in the next couple of days :-)