al, disables apt update/upgrade
<voidspace> dimitern: ah, so definitely sounds like a MAAS bug
<dimitern> voidspace: there's 1 machine that matches those spaces, and here's the error we get: http://paste.ubuntu.com/23415499/
<dimitern> voidspace: yeah, IIRC mpontillo did mention something about that and they seem to be fixing it
<voidspace> dimitern: cool, so I don't think we should hold up this PR with it - I haven't seen a MAAS bug for it
<voidspace> dimitern: worth filing even if it turns out to be a duplicate
<dimitern> voidspace: I'll look into filing one later today; just testing with 2.0 now - 2.1 tested OK
<voidspace> dimitern: I have a very short PR fixing not_networks for 1.9 I'd like you to test too if possible
<voidspace> dimitern: will ping in a couple of minutes
<dimitern> voidspace: sure - can do - is it about the way we serialize multiple negatives?
<voidspace> dimitern: yep
<voidspace> dimitern: changing from comma separated to multiple parameters
<dimitern> voidspace: ok
<dimitern> mgz: ping
<dimitern> mgz: do you know which mongo version are we using for the windows CI slave running this job: http://reports.vapour.ws/releases/4546/job/run-unit-tests-win2012-amd64/attempt/3002#highlight
<dimitern> mgz: if it's 2.6.x, the test might be failing due to this mongo bug - https://jira.mongodb.org/browse/SERVER-14840
<dimitern> voidspace: tested on 2.0 successfully and LGTM-ed
<voidspace> dimitern: you rock
<dimitern> voidspace: it took me a lot longer to setup the spaces / subnets on maas than to run bootstrap OK :)
<voidspace> dimitern: I can imagine
<voidspace> dimitern: my maas 2 is not playing ball and won't enlist new nodes
<voidspace> burned a few hours on it :-/
<voidspace> dimitern: might have to reinstall from scratch
<voidspace> got inveigled in another conversation
<voidspace> about to create the PR for maas 1.9
<voidspace> and I'll do PRs to bump the gomaasapi dependency in juju
<voidspace> both for 2.0 and develop branches
<dimitern> voidspace: I'm now using frobware's kvm-maas-add|remove