[07:34] <mup> Bug #1503990 opened: apiserver/http: attachment functions not tested <juju-core:New> <https://launchpad.net/bugs/1503990>
[07:49] <mup> Bug #1503992 opened: apiserver: Digest SHA header is incorrectly formed <juju-core:New> <https://launchpad.net/bugs/1503992>
[07:58] <mup> Bug #1503992 changed: apiserver: Digest SHA header is incorrectly formed <juju-core:New> <https://launchpad.net/bugs/1503992>
[08:04] <mup> Bug #1503992 opened: apiserver: Digest SHA header is incorrectly formed <juju-core:New> <https://launchpad.net/bugs/1503992>
[16:52] <dooferlad> TheMue / voidspace: If you have a moment: http://reviews.vapour.ws/r/2854/
[16:53]  * dooferlad is done for the day
[17:00] <rogpeppe> thumper: hiya
[17:57] <perrito666> Is the core team going to happen ?
[18:05] <natefinch> perrito666: ericsnow and I were there
[18:05] <natefinch> now just me
[18:14] <perrito666> I tried, no one was when I asked
[18:30] <mgz> the core team is always happening
[18:33] <frobware> voidspace, ping
[18:34] <frobware> voidspace, any progress with the 1.9 MAAS bug?
[18:54] <mup> Bug #1504272 opened: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>
[18:57] <mup> Bug #1504272 changed: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>
[19:09] <mup> Bug #1504272 opened: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>
[19:12] <mup> Bug #1504272 changed: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>
[19:13] <voidspace> frobware: I have a fix committed (in a branch)
[19:13] <voidspace> frobware: needs a test
[19:13] <voidspace> frobware: manually confirmed to work fine with maas 1.9
[19:14] <frobware> voidspace, point me at the branch - I have a local 1.9 install and could try it.
[19:14] <frobware> voidspace, (thx!!!)
[19:14] <voidspace> frobware: however, I would still like to confirm the bug - maas 1.9 seems to work fine for me and I have yet to reproduce
[19:15] <voidspace> frobware: https://github.com/voidspace/juju/tree/1494476-maas-networking
[19:15] <mup> Bug #1504272 opened: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>
[19:16] <voidspace> frobware: works fine, including deploying containers, with MAAS Version 1.9.0 (alpha1+bzr4064+4128+417~ppa0~ubuntu14.10.1)
[19:18] <voidspace> frobware: dimitern: dooferlad is firmly of the opinion that the right cause of action is to remove juju-br0 altogether (even when addressable containers is off)
[19:18] <voidspace> frobware: dimitern: and that it's relatively easy to do - even for deployed environments that have machines with an existing juju-br0
[19:19] <voidspace> (leaving it in place for machines that have it - and so the PrepareContainerInterfaceInfo api call will need to know the bridge to use. Easy to add a new version of that api that takes the extra arg)
[19:23] <dimitern> voidspace, dropping juju-br0 without replacing it with something else that will ensure container addressability is not an option unfortunately
[20:11] <mgz> cmars: bug 1504272 btw, not sure if you want anything worded differently
[20:11] <mup> Bug #1504272: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>
[20:12] <voidspace> frobware: tell dimitern that the containers setup their own bridges that we can use
[20:12] <voidspace> frobware: he's dropped off irc
[20:12] <voidspace> frobware: anyway, a conversation for when you all return
[20:13] <frobware> voidspace, back now
[20:13] <cmars> mgz, thanks
[20:13] <frobware> voidspace, when the container starts it sets up its own bridge?
[20:14] <voidspace> frobware: no, installing kvm and lxc puts a bridge in place - containers will do that aspect of the networking themselves if we let them
[20:14] <voidspace> if you have lxc installed you'll have a bridge it created
[20:15] <voidspace> anyway, dooferlad can make his case for this when you return
[20:15] <frobware> voidspace, can you recreate the problem?
[20:15] <voidspace> frobware: not yet
[20:15] <voidspace> just putting the daughter to bed - may get a chance in a bit
[20:16] <voidspace> at the very least the new code works with maas 1.9 and when I run the script on the example that was screwed up it "does the right thing"
[20:16] <voidspace> so it *should* work :-)
[20:22] <frobware> dimitern, https://github.com/voidspace/juju/tree/1494476-maas-networking
[20:34] <mgz> abentley: we're in the hangout
[22:10] <mgz> http://reviews.vapour.ws/r/2860/ <- review please?
[22:27] <mgz> menn0: http://reviews.vapour.ws/r/2860/
[22:28] <sinzui> cherylj: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1267393
[22:28] <mup> Bug #1267393: [MIR] juju-core, juju-mongodb, gccgo, golang <gccgo-5 (Ubuntu):Fix Released> <gccgo-go (Ubuntu):Invalid by doko> <golang (Ubuntu):Incomplete> <juju-core (Ubuntu):Confirmed> <juju-mongodb (Ubuntu):Incomplete> <https://launchpad.net/bugs/1267393>
[22:44] <cherylj> hey dimitern, do you know where mfoord is with bug 1494476?
[22:44] <mup> Bug #1494476: MAAS provider with MAAS 1.9 - /etc/network/interfaces "auto eth0" gets removed and bridge is not setup <addressability> <lxc> <maas-provider>
 <juju-core:Triaged by mfoord> <juju-core 1.24:Triaged by mfoord> <juju-core 1.25:In Progress by mfoord> <https://launchpad.net/bugs/1494476>
[22:46] <dimitern> cherylj, he has a fix proposed for 1.25, I'm working on a simpler fix for 1.24
[22:47] <cherylj> dimitern: awesome, thanks