=== akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr [07:34] Bug #1503990 opened: apiserver/http: attachment functions not tested [07:49] Bug #1503992 opened: apiserver: Digest SHA header is incorrectly formed [07:58] Bug #1503992 changed: apiserver: Digest SHA header is incorrectly formed [08:04] Bug #1503992 opened: apiserver: Digest SHA header is incorrectly formed === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr [16:52] TheMue / voidspace: If you have a moment: http://reviews.vapour.ws/r/2854/ [16:53] * dooferlad is done for the day === akhavr1 is now known as akhavr [17:00] thumper: hiya === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr [17:57] Is the core team going to happen ? [18:05] perrito666: ericsnow and I were there [18:05] now just me === akhavr1 is now known as akhavr [18:14] I tried, no one was when I asked === akhavr1 is now known as akhavr [18:30] the core team is always happening === akhavr1 is now known as akhavr [18:33] voidspace, ping [18:34] voidspace, any progress with the 1.9 MAAS bug? [18:54] Bug #1504272 opened: Errors from rpc do not appear in logs

[18:57] Bug #1504272 changed: Errors from rpc do not appear in logs

=== akhavr1 is now known as akhavr [19:09] Bug #1504272 opened: Errors from rpc do not appear in logs

[19:12] Bug #1504272 changed: Errors from rpc do not appear in logs

[19:13] frobware: I have a fix committed (in a branch) [19:13] frobware: needs a test [19:13] frobware: manually confirmed to work fine with maas 1.9 [19:14] voidspace, point me at the branch - I have a local 1.9 install and could try it. [19:14] voidspace, (thx!!!) [19:14] 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] frobware: https://github.com/voidspace/juju/tree/1494476-maas-networking [19:15] Bug #1504272 opened: Errors from rpc do not appear in logs

[19:16] frobware: works fine, including deploying containers, with MAAS Version 1.9.0 (alpha1+bzr4064+4128+417~ppa0~ubuntu14.10.1) === akhavr1 is now known as akhavr [19:18] 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] frobware: dimitern: and that it's relatively easy to do - even for deployed environments that have machines with an existing juju-br0 [19:19] (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] voidspace, dropping juju-br0 without replacing it with something else that will ensure container addressability is not an option unfortunately === akhavr1 is now known as akhavr === \b is now known as benonsoftware === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr [20:11] cmars: bug 1504272 btw, not sure if you want anything worded differently [20:11] Bug #1504272: Errors from rpc do not appear in logs

[20:12] frobware: tell dimitern that the containers setup their own bridges that we can use [20:12] frobware: he's dropped off irc [20:12] frobware: anyway, a conversation for when you all return [20:13] voidspace, back now [20:13] mgz, thanks [20:13] voidspace, when the container starts it sets up its own bridge? [20:14] 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] if you have lxc installed you'll have a bridge it created [20:15] anyway, dooferlad can make his case for this when you return [20:15] voidspace, can you recreate the problem? [20:15] frobware: not yet [20:15] just putting the daughter to bed - may get a chance in a bit [20:16] 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] so it *should* work :-) [20:22] dimitern, https://github.com/voidspace/juju/tree/1494476-maas-networking [20:34] abentley: we're in the hangout === mwenning is now known as mwenning-appt === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr [22:10] http://reviews.vapour.ws/r/2860/ <- review please? === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr [22:27] menn0: http://reviews.vapour.ws/r/2860/ [22:28] cherylj: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1267393 [22:28] Bug #1267393: [MIR] juju-core, juju-mongodb, gccgo, golang

=== akhavr1 is now known as akhavr === akhavr1 is now known as akhavr [22:44] hey dimitern, do you know where mfoord is with bug 1494476? [22:44] Bug #1494476: MAAS provider with MAAS 1.9 - /etc/network/interfaces "auto eth0" gets removed and bridge is not setup

[22:44]

[22:46] cherylj, he has a fix proposed for 1.25, I'm working on a simpler fix for 1.24 [22:47] dimitern: awesome, thanks === akhavr1 is now known as akhavr === akhavr1 is now known as akhavr