 seeing lxcbr0 in there *at all* is wrong and should be fixed
<wallyworld_> dimitern: which bit?
<dimitern> wallyworld_, in fact I'm thinking of doing that today, as this is likely the 15th bug report related to that piece of code in the maas provider
<fwereade> ok, uniter tests passing again, popping out to shops, bbs
<wallyworld_> dimitern: that would be awesome
<wallyworld_> i don't know enough about networking
<dimitern> wallyworld_, there is some code in there that aims to "restore" /etc/network/interfaces the way they *should* look like in a stock trusty install, but that's really not the point - we shouldn't be using the bridge at all, but first we should respect the network-bridge setting
<dimitern> at least
<wallyworld_> sounds reasonable
<TheMue> morning
<dimitern> wallyworld_, cool, thanks
<dimitern> TheMue, morning
<wallyworld_> dimitern: no, thank you, i have no idea really
<dimitern> wallyworld_, well, I have to admit the simple solution of just using "network-bridge" in there as a temporary fix (so at least it's configurable) simply didn't occur to me earlier, and we can't just remove the bridge creation until we've implemented the static ip reservation api maas 1.7 gives us; so tl;dr - thanks for pointing that out :)
<wallyworld_> np, it was an educated guess :-)
<mattyw> morning all
<voidspace> morning all
<TheMue> mattyw, voidspace: heya
<mattyw> TheMue, morning morning
<fwereade> voidspace, would you be free to take a look at a couple of gsamfira's PRs? https://github.com/juju/juju/pull/782 https://github.com/juju/juju/pull/833
<fwereade> voidspace, gsamfira: I should be able to get to them later, but I realised I broke something in the uniter and I'm focused on unbreaking it
<gsamfira> fwereade: heh, no worries
<fwereade> and if anyone *else* is free -- jam, dimitern maybe? -- http://reviews.vapour.ws/r/288/diff/# is the code, on which I'd really a appreciate a logic/style pre-review, but I haven't yet fixed all the tests (sigh)
<jam> fwereade: looking
<jam> fwereade: is "State().Members" a ma