[00:06] <bigjools> qhartman: yes, preseed adjustment is the way to go, for now at least.
[00:07] <bigjools> allenap: I think there is a caching proxy in the way somewhere which doesn't have the new layout
[02:32] <bigjools> jtv: http://paste.ubuntu.com/7311567/
[02:33] <jtv> So you're getting it too?  I'm not.
[02:33] <jtv> Though let me try trunk.
[02:33] <jtv> Whoops, yes, lots of errors!
[02:34] <jtv> Eenteresting.
[02:35] <bigjools> ah
[02:35] <bigjools> apparently
[02:35] <bigjools> functools.wraps expects the callable being wrapped to have a __module__ attribute
[02:36] <jtv> Hey.
[02:36] <jtv> I'm getting this in my branch.
[02:36] <jtv> Of which I ran the tests endlessly yesterday without these failures.
[02:36] <bigjools> I am getting this in trunk
[02:37] <jtv> So... package update?
[02:37] <bigjools> I expect a django update broke things
[02:37] <jtv> Yes, I'm getting it in trunk too.  Thing is, I wasn't getting this yesterday, and it's not a code change.
[02:37] <bigjools> of which there was just one
[02:37]  * bigjools looks at the django change
[02:38] <bigjools> jtv: yep I reckon this is a regression in the security update
[02:38]  * bigjools files bug
[02:39] <jtv> Might I recommend a priority on the high side?
[02:41] <bigjools> jtv: https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1311433
[02:41] <bigjools> can you confirm it :)
[02:42] <jtv> I registered my being affected by it.
[02:42] <jtv> Hope that's what you mean.
[02:42] <bigjools> change the status
[02:42] <bigjools> well it does that automatically I think
[02:44] <jtv> I didn't think the Confirmed status did much, except maybe make triagers think the bug doesn't need attention.
[02:44] <jtv> Oh, it's Confirmed now.
[02:48] <bigjools> jtv: this is very serious, maas no longer runs at all in trusty
[02:56] <bigjools> jtv: ok we can fix this locally
[02:56] <bigjools> jtv: https://code.djangoproject.com/ticket/22486
[02:57] <bigjools> I'll file a maas bug
[02:58] <jtv> I wonder where we're doing the partial thing.
[02:59] <jtv> src/maasserver/views/combo.py?
[03:00] <jtv> get_combo_view is the only thing (outside of tests) that looks to me like it might be doing this.
[03:02] <bigjools> jtv: can you do me a favour and see if this patch fixes things? https://github.com/prestontimmons/django/commit/b63ae5c60619a257ad57cf6043e71f681283e47b
[03:02] <jtv> Looking..
[03:02] <jtv> I was just trying a patch of my own.
[03:03] <bigjools> it's a patch to django though
[03:03] <bigjools> security team will apply it if we confirm it works
[03:03] <jtv> Ah.  Meanwhile I seem to have a working patch to maas.
[03:04] <bigjools> jtv: ah!
[03:04] <jtv> bigjools: my test run is not done yet, but this simple maas fix seems to work around the problem at least for us: http://paste.ubuntu.com/7311704/
[03:04] <bigjools> jtv: land it so it unblocks the lander at least
[03:04] <jtv> I'll start a VM to try the django patch.
[03:05] <jtv> Aye-aye sir.
[03:05] <jtv> Got a maas bug number?
[03:05] <bigjools> jtv: same number, I added a maas task
[03:05] <jtv> OK
[03:20] <mdeslaur> jtv: any news?
[03:21] <jtv> mdeslaur: about what?
[03:21] <jtv> the bug?
[03:21] <jtv> I'm landing a workaround in maas.
[03:21] <mdeslaur> jtv: yeah, the upstream patch
[03:21] <mdeslaur> I'm building security regression fixes with the commit from the upstream bug
[03:21] <jtv> I'm still setting up for the attempt.
[03:22] <jtv> By the way, you wouldn't happen to know a way to get a plain diff from that github page?
[03:22] <mdeslaur> jtv: add ".patch" to the end of the url
[03:23] <jtv> Ah, of course!  Why didn't I figure that out myself!

[03:23] <jtv> Thanks.  :)
[03:23] <mdeslaur> yeah, super-intuitive
[03:23] <mdeslaur> I just uploaded a fixed package for trusty here: https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages
[03:23] <mdeslaur> and will upload for the other releases in a few minutes
[03:24] <jtv> Are you saying I could just use that package instead of applying the diff?
[03:24] <mdeslaur> jtv: yes
[03:24] <jtv> Great, thanks!
[03:24] <mdeslaur> and I would like to know if it fixes maas before I push them out ASAP
[03:25] <jtv> Yes, of course...  I'm setting up to establish that.
[03:28] <mdeslaur> jtv: cool, thanks
[04:02] <jtv> mdeslaur: for maas, the proposed update fixes the failures!
[04:02] <mdeslaur> jtv: awesome, thanks for testing!
[04:02] <mdeslaur> I'll release them right away
[04:02] <jtv> (Although of course independently from that, I already landed a workaround in maas)
[04:02] <jtv> Thanks.  This has bitten us pretty hard, so glad to see it being resolved for everyone.
[04:02] <bigjools> thanks mdeslaur
[04:03] <bigjools> and thanks for testing jtv
[04:03] <jtv> Still seeing _some_ test failures with the new package, but let me see what they are first.
[04:03] <jtv> May be unrelated.
[04:03] <mdeslaur> bigjools, jtv: thanks!
[04:03] <jtv> xargs: env: terminated by signal 9
[04:03] <jtv> That's something we've seen before... probably unrelated.
[04:03] <mdeslaur> I'll make sure we add maas to our django testing going forward
[04:03] <jtv> I'm investigating.
[04:03] <bigjools> mdeslaur: \o/
[04:11] <jtv> Found the cause of those other test errors: VM ran out of memory.  Not an issue.
[04:13] <mdeslaur> jtv: thanks
[06:57] <rvba> gmb: did you get to the bottom of the "AttributeError: 'functools.partial' object has no attribute '__module__'" failure?
[06:58] <rvba> (Hi gmb, btw :))
[06:58] <rvba> jtv: ^
[06:59] <rvba> I'm asking because I'm seeing that locally now… and I saw that the python-django package has been updated…
[07:03] <bigjools> rvba: I did
[07:03] <bigjools> django fail
[07:03] <rvba> Yeah, I just saw the fixes.
[07:03] <bigjools> update again
[07:03] <rvba> What a mess.
[07:04] <bigjools> yes :)
[07:13] <gmb> Bbiam
[09:24] <jtv> Who's up for what I hope will be a simple review?  https://code.launchpad.net/~jtv/maas/env-context-manager/+merge/216840
[09:25] <rvba> jtv: I'll take it
[09:25] <jtv> Merci beaucoup.
[09:25] <rvba> Pas de problème.
[10:38] <alfs> I'm having some strange mirroring problems.
[10:38] <alfs> http://archive.ubuntu.com/ubuntu/ is fine
[10:38] <alfs> http://ftp.se.debian.org/ubuntu/  does not work
[10:39] <alfs> The installer claims the archive is broken, and syslogs says 403 forbidden when accessing http://ftp.se.debian.org/ubuntu/
[10:39] <alfs> http://ftp.se.debian.org/ubuntu/dists/trusty/Release
[10:39] <alfs> but it works fine outside the installer.
[10:40] <alfs> Trying to access it from the interrupted installation shell, but the kvm/keymapping does not allow me typing slashes... trying to find some workaround
[11:08] <jtv> Could it be a problem with a proxy somewhere inbetween?
[11:15] <alfs> dont think there are any. However, when I dump traffic on the gw/router, I see e.g. icmp packets to the mirror when I ping, but no web requests.
[11:25] <alfs> Seems it's not a mirror problem. Same error with e.g. ftp.uk.debian.org/ubuntu and others.
[11:25] <alfs> *digging for proxies*
[13:26] <melmoth> hola ! now that trusty is out, i guess i can just apt-get install maas and juju-core and all the tools without having to add any ppa or are ppa still relevant ?
[14:57] <lazyPower> melmoth: i'm not using any ppa's and my MAAS cluster works a treat. (i'm using kvm virtualization, ymmv if on bare metal)
[14:59] <magicrobotmonkey> anyone have any tips for debugging the pxelinux.0 that comes with MAAS? Cobblers works fine, but with MAAS it barfs on some iSCSI stuff
[14:59] <magicrobotmonkey> i think it may be using the wrong interface
[14:59] <melmoth> lazyPower, nodes will be kvm vm too , it s just for playing :-)
[14:59] <melmoth> actually, even the maas box is a kvm vm.
[15:00] <lazyPower> ah, i went the other way around with that and kept the region controller on bare metal so i could reach the aas nodes from outside my network.
[15:00] <lazyPower> bridging into the VM was a bit of a heady process
[15:03] <magicrobotmonkey> im install maas-cluster-controller on a brand new trusty install and the apache restart is bailing due to missing crochet module
[15:04] <rvba> magicrobotmonkey: looks like a packaging bug.  Please report a bug with all the details and we will get back to you ASAP.
[15:04] <magicrobotmonkey> ok ty
[15:24] <qhartman> so, I'm setting up a multi-homed MAAS cluster, and the routes and DNS on the nodes that come up are all sorts of wrong.
[15:24] <qhartman> I'm wanting to treat the MAAS-side as a management network, and as such isn't bridged / routed onto the main network.
[15:24] <qhartman> but the MAAS config tool doesn't want to let me make the DHCP changes that I think need to be made to make this work.
[15:25] <qhartman> since the external interfaces (which are internet connected) are managed by a different DHCP
[15:25] <qhartman> so, what's the right way to do this sort of setup?
[15:25] <qhartman> I'm sure I could hand-jam it, but that seems counter to the point of MAAS.
[15:26] <qhartman> or should I have my MAAS controller setup to bridge between the networks and have the nodes see the outside world that way?
[16:03] <lazyPower> qhartman: i setup a bridge device on the region controller - but my maas nodes are kvm machines and not bare metal.
[16:03] <lazyPower> its kind of dependent on your network topology
[16:05] <qhartman> right
[16:05] <qhartman> yeah, I've setup my controller to do forwarding now as well. We'll see if this actually fixes the Juju problem.
[16:05] <qhartman> I'm nuking the other machine I was working on and starting with a fresh node
[16:07] <magicrobotmonkey> is there a strategy for importing pxe files from a host that can't reach the internet?
[16:07] <magicrobotmonkey> the region controller can
[16:52] <lazyPower> magicrobotmonkey: you should only need to import the pxe files on your region controller. I'm fairly certain that hands off the files to the zone controllers.
[16:53] <lazyPower> i could be wrong though - needs citation
[16:53] <magicrobotmonkey> hmm it doesnt seem like the docs say that
[16:53] <magicrobotmonkey> but it turns out i have some network issues to resolve first anyways
[17:49] <magicrobotmonkey> how do you login to a maas-cluster-controller from the cli?
[21:16] <allenap> jhobbs: Hi there. Have you had a look at the “HWE streams” thing?
[21:22] <jhobbs> allenap: a little bit, I wrote a doc on some of it https://docs.google.com/a/canonical.com/document/d/1CJlIu2wapKJgDl-MXmvK_RseqBHeWJQ6S-gJzn0bh34/edit#heading=h.eeybgo5224oo
[21:24] <allenap> jhobbs: Nifty, I’ll read that before the meeting.