/srv/irclogs.ubuntu.com/2015/10/08/#juju-dev.txt

=== 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
mupBug #1503990 opened: apiserver/http: attachment functions not tested <juju-core:New> <https://launchpad.net/bugs/1503990>07:34
mupBug #1503992 opened: apiserver: Digest SHA header is incorrectly formed <juju-core:New> <https://launchpad.net/bugs/1503992>07:49
mupBug #1503992 changed: apiserver: Digest SHA header is incorrectly formed <juju-core:New> <https://launchpad.net/bugs/1503992>07:58
mupBug #1503992 opened: apiserver: Digest SHA header is incorrectly formed <juju-core:New> <https://launchpad.net/bugs/1503992>08:04
=== 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
dooferladTheMue / voidspace: If you have a moment: http://reviews.vapour.ws/r/2854/16:52
* dooferlad is done for the day16:53
=== akhavr1 is now known as akhavr
rogpeppethumper: hiya17:00
=== 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
perrito666Is the core team going to happen ?17:57
natefinchperrito666: ericsnow and I were there18:05
natefinchnow just me18:05
=== akhavr1 is now known as akhavr
perrito666I tried, no one was when I asked18:14
=== akhavr1 is now known as akhavr
mgzthe core team is always happening18:30
=== akhavr1 is now known as akhavr
frobwarevoidspace, ping18:33
frobwarevoidspace, any progress with the 1.9 MAAS bug?18:34
mupBug #1504272 opened: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>18:54
mupBug #1504272 changed: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>18:57
=== akhavr1 is now known as akhavr
mupBug #1504272 opened: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>19:09
mupBug #1504272 changed: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>19:12
voidspacefrobware: I have a fix committed (in a branch)19:13
voidspacefrobware: needs a test19:13
voidspacefrobware: manually confirmed to work fine with maas 1.919:13
frobwarevoidspace, point me at the branch - I have a local 1.9 install and could try it.19:14
frobwarevoidspace, (thx!!!)19:14
voidspacefrobware: however, I would still like to confirm the bug - maas 1.9 seems to work fine for me and I have yet to reproduce19:14
voidspacefrobware: https://github.com/voidspace/juju/tree/1494476-maas-networking19:15
mupBug #1504272 opened: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>19:15
voidspacefrobware: works fine, including deploying containers, with MAAS Version 1.9.0 (alpha1+bzr4064+4128+417~ppa0~ubuntu14.10.1)19:16
=== akhavr1 is now known as akhavr
voidspacefrobware: 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
voidspacefrobware: dimitern: and that it's relatively easy to do - even for deployed environments that have machines with an existing juju-br019:18
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:19
dimiternvoidspace, dropping juju-br0 without replacing it with something else that will ensure container addressability is not an option unfortunately19:23
=== akhavr1 is now known as akhavr
=== \b is now known as benonsoftware
=== akhavr1 is now known as akhavr
=== akhavr1 is now known as akhavr
mgzcmars: bug 1504272 btw, not sure if you want anything worded differently20:11
mupBug #1504272: Errors from rpc do not appear in logs <api> <observability> <juju-core:Triaged> <https://launchpad.net/bugs/1504272>20:11
voidspacefrobware: tell dimitern that the containers setup their own bridges that we can use20:12
voidspacefrobware: he's dropped off irc20:12
voidspacefrobware: anyway, a conversation for when you all return20:12
frobwarevoidspace, back now20:13
cmarsmgz, thanks20:13
frobwarevoidspace, when the container starts it sets up its own bridge?20:13
voidspacefrobware: no, installing kvm and lxc puts a bridge in place - containers will do that aspect of the networking themselves if we let them20:14
voidspaceif you have lxc installed you'll have a bridge it created20:14
voidspaceanyway, dooferlad can make his case for this when you return20:15
frobwarevoidspace, can you recreate the problem?20:15
voidspacefrobware: not yet20:15
voidspacejust putting the daughter to bed - may get a chance in a bit20:15
voidspaceat 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
voidspaceso it *should* work :-)20:16
frobwaredimitern, https://github.com/voidspace/juju/tree/1494476-maas-networking20:22
mgzabentley: we're in the hangout20:34
=== 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
mgzhttp://reviews.vapour.ws/r/2860/ <- review please?22:10
=== akhavr1 is now known as akhavr
=== akhavr1 is now known as akhavr
=== akhavr1 is now known as akhavr
mgzmenn0: http://reviews.vapour.ws/r/2860/22:27
sinzuicherylj: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/126739322:28
mupBug #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:28
=== akhavr1 is now known as akhavr
=== akhavr1 is now known as akhavr
cheryljhey dimitern, do you know where mfoord is with bug 1494476?22:44
mupBug #1494476: MAAS provider with MAAS 1.9 - /etc/network/interfaces "auto eth0" gets removed and bridge is not setup <addressability> <lxc> <maas-provider>22:44
mup<network> <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:44
dimiterncherylj, he has a fix proposed for 1.25, I'm working on a simpler fix for 1.2422:46
cheryljdimitern: awesome, thanks22:47
=== akhavr1 is now known as akhavr
=== akhavr1 is now known as akhavr

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!