[00:20] <mup> Bug #1518793 opened: cinder (liberty) fails to retrieve volume limit in Horizon <juju-core:New> <https://launchpad.net/bugs/1518793>
[00:26] <davecheney> does anyone have the link to the build tashboard
[00:26] <davecheney> i'm looking for the failing race builder
[00:36] <davecheney> menn0_: thumper https://github.com/juju/testing/pull/84
[01:09] <thumper> WTH?
[01:10] <thumper> fresh build of juju 1.22.7
[01:10] <thumper> $ juju bootstrap
[01:10] <thumper> Bootstrap failed, cleaning up the environment.
[01:10] <thumper> ERROR there was an issue examining the environment: dial tcp 127.0.0.1:37019: getsockopt: connection refused
[01:10] <thumper> with local provider
[01:11] <thumper> oh ffs
[01:12] <thumper> fuck fuck fuckity fuck
[01:12] <thumper> something changed no doubt with go 1.5
[01:22] <axw> davecheney: why skip tests that fail the race detector? they're failing due to things other than races? too slow?
[01:22] <axw> thumper: yes, that's fixed on master
[01:23] <axw> thumper: different error type
[01:23] <thumper> yeah
[01:23] <thumper> patched my local
[01:26] <thumper> axw: because we want go get the race test voting
[01:26] <thumper> then expand
[01:27] <thumper> otherwise people keep committing races
[01:27] <axw> fair enough
[01:29] <davecheney> axw: the tests timeout
[01:29] <davecheney> some horrid timing issue
[01:29] <davecheney> so, skip them for now
[01:29] <davecheney> get the race test voting
[01:29] <davecheney> and iterate from there
[01:29] <axw> davecheney: nps. getting it voting sounds good
[02:02] <mup> Bug #1518806 opened: apiserver: tests to not pass with -race under Go 1.2 <juju-core:Triaged by dave-cheney> <https://launchpad.net/bugs/1518806>
[02:02] <mup> Bug #1518807 opened: apiserver/client: tests to not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518807>
[02:02] <mup> Bug #1518809 opened: apiserver/uniter: tests to not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518809>
[02:14] <mup> Bug #1518810 opened: cmd/juju/commands: tests do not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518810>
[02:17] <mup> Bug #1518810 changed: cmd/juju/commands: tests do not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518810>
[02:25] <axw> wallyworld: thanks for shipit. I may end up changing the watcher as discussed as the worker evolves to support watching the remote side. we'll see.
[02:26] <wallyworld> axw: yep, np. it's always hard to get this 100% up front. i'm all for iterating on a feature branch and correcting issues as we get futher into the implementtion
[02:26] <wallyworld> at least we're considering all the options
[02:32] <mup> Bug #1518810 opened: cmd/juju/commands: tests do not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518810>
[03:26] <mup> Bug #1518820 opened: environs/bootstrap: tests to not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518820>
[03:27] <thumper> hmm...
[03:28] <thumper> I thought that the lxd provider had been merged into master
[03:29] <mup> Bug #1518820 changed: environs/bootstrap: tests to not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518820>
[03:30] <davecheney> thumper: it has
[03:30] <davecheney> i've raised some bugs because now the tests don't pass unless you have lxd installed
[03:30] <thumper> yeah... but I can't bootstrap and NFI why
[03:30] <davecheney> and not pass in an impolite way
[03:32] <mup> Bug #1518820 opened: environs/bootstrap: tests to not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1518820>
[04:00] <cherylj> thumper: I think there were some build flag restrictions with lxd where it wouldn't work unless you had go 1.3 or later.
[04:01] <thumper> I have go 1.5
[04:01] <cherylj> ah, n/m then :)
[04:09] <anastasiamac> wallyworld: axw: I *think* list cli is ready for review (http://reviews.vapour.ws/r/3171/)
[04:09] <anastasiamac> plz b genetle - i have a hole week ahead of me :P
[04:09] <axw> anastasiamac: okey dokey, looking
[04:09] <anastasiamac> gentle even
[04:09] <wallyworld> a "hole" week. what type of hole?
[04:10] <anastasiamac> a big and balck one :D
[04:10] <anastasiamac> black*
[04:11] <anastasiamac> for crying out \o/
[04:11] <cherylj> O_o
[04:12] <cherylj> neato.  I got my provisioning updater to use the new MAAS 1.9 curtin status:  http://paste.ubuntu.com/13469033/
[04:12] <cherylj> thumper: ^^
[04:13] <axw> cherylj: sweet!
[04:13] <cherylj> I feel better about demoing this now that we can use the new MAAS stuff
[04:13]  * thumper looks
[04:13] <axw> cherylj: looking forward to being able to tell what's going on ;)
[04:13] <cherylj> thanks axw :)
[04:13] <thumper> nice
[04:13] <cherylj> although, the stuff from MAAS isn't as verbose or informative as I was hoping
[04:14] <axw> yeah that particular message isn't great
[04:15] <axw> anastasiamac: still reviewing, but please rename "type ListEndpointsServicesResult" to "type ListEndpointsServiceResults"
[04:15] <axw> anastasiamac: it's a collection of results where each result is a ListEndpointsServiceResult
[04:16] <anastasiamac> axw: there are several result collections
[04:16] <axw> anastasiamac: this one is in model/crossmodel
[04:16] <axw> not sure if there are others that need changing yet
[04:18] <anastasiamac> axw: yes.... ListEndpointsServiceResult is "service" and "ListEndpointsServicesResult" is "services" result. The 2nd being really a result from a "service directory" but we did not want to use "service directory" :D
[04:19] <axw> anastasiamac: not following. I'm looking at the definition of ListEndpointsServicesResult, and its contents are an error, and a slice of ListEndpointsServiceResult
[04:20] <axw> so how is that not ListEndpointsServiceResults?
[04:21] <anastasiamac> axw: it must b too hot in QLD, but isn't ur head spinning form all "Item"(s) and "result"(s)... I wish we had better less awful names (and naming conventions)
[04:22] <anastasiamac> axw: i'll address after school pickup :D
[04:22] <axw> anastasiamac: I agree it's not great, but we do have a convention and we do need to stick to it or things will be even worse
[04:22] <axw> anastasiamac: thank you
[04:30] <wallyworld> axw: i'll look at api pr, in the meantime, coupld you please look at this small one for charmrepo https://github.com/juju/charmrepo/pull/54
[04:32] <axw> wallyworld: LGTM
[04:32] <wallyworld> ty
[04:39] <mup> Bug #1518793 changed: cinder (liberty) fails to retrieve volume limit in Horizon <juju-core:Invalid> <cinder (Juju Charms Collection):New> <https://launchpad.net/bugs/1518793>
[04:39] <wallyworld> axw: so we have a naming issue. apifacade.WatchRemoteService(service string) should really call apiserver "WatchRemoteServices". but that method name is already used
[04:39] <axw> wallyworld: in existing facades it's always singular, even if it takes bulk. it's named after the singular argument.
[04:40] <axw> s/always/predominantly/
[04:40] <wallyworld> axw: yeah, i was about to say except in storageprovisioner WatchMachine()
[04:40] <wallyworld> mybe elsewhere
[04:40] <wallyworld> wish we were consistent
[04:40] <wallyworld> ok, i'll ignore it
[04:46] <wallyworld> axw: lgtm
[04:46] <axw> wallyworld: thanks
[09:21] <dimitern> jam, hey, sorry :/ I had to do an emergency reinstall of the new laptop this morning, after some package yesterday caused mayhem
[09:21] <jam> dimitern: we had *just* brought up the new laptop
[09:21] <dimitern> jam, nice! congrats :)
[09:23]  * dimitern discovered even with 15.10 it's quite a challenge to get 4K laptop monitor + HD external monitor to work short of forcing the 4K screen to 1920x1080
[09:36] <dooferlad> dimitern: wow, really? I thought it was annoying just having the 4k screen.
[09:37] <dooferlad> dimitern: no scaling per screen I take it
[09:38] <dimitern> dooferlad, it's quite good actually, the issue is text is too small, but when scaled by 200% and it looks fine on the 4K screen, the text on the HD screen is also scaled twice :/ I wish unity supported separate scaling factors per display
[09:38] <dimitern> dooferlad, nailed it :)
[09:39] <dooferlad> yea, same problem with a 1200px high screen and a 1440px one. It is great fun moving a window from the "big" one to a small one because you lose the bottom.
[09:40] <dimitern> so while it's perfect with 2 screens of the same size (well, and using nvidia drivers, as "Displays" is too dumb to allow the 4K screen to scale to 1920x1080 - it only shows its native res)
[09:41] <dimitern> a full make check takes ~5m now, not 20
[09:41] <dooferlad> :-)
[09:41] <dooferlad> that is about the same speed as my desktop! Nice!
[09:41] <dimitern> yeah - quad core i7 + k2100m gpu
[09:42] <dimitern> the latter I only tried with steam :)
[09:42] <dooferlad> :-)
[09:43] <dimitern> I'll be living the dream - running tests *while* using a HO at full quality :D
[09:59] <voidspace> dimitern: https://github.com/juju/juju/pull/3788
[09:59] <dimitern> voidspace, will have a look
[09:59] <voidspace> dimitern: if we want to rebase a feature branch, instead of merge, then we can't just do it as a rebase then merge
[09:59] <voidspace> dimitern: because that ends up being the same as a merge
[09:59] <voidspace> dimitern: but if we want CI tests run then we *have* to do it as a merge
[10:01] <jam> fwereade: standup?
[10:28] <voidspace>  dooferlad dimitern: I *think* the rebase is now done on the feature branch
[10:29] <dimitern> voidspace, I'll update and do a make check locally
[10:30] <dimitern> voidspace, has it landed?
[10:31] <voidspace> dimitern: I pushed...
[10:31] <dimitern> voidspace, I can't see any changes
[10:31] <voidspace> dimitern: hmmm...
[10:32] <voidspace> I pushed to upstream/maas-spaces
[10:32] <voidspace> I wonder where that went
[10:32] <dimitern> voidspace, it looks like you pushed voidspace/juju branch maas-spaces-rebase-1
[10:32] <voidspace> dimitern: I already had that
[10:32] <dimitern> voidspace, ah, ok
[10:32] <voidspace> dimitern: that was my initial rebase on Friday
[10:33] <dimitern> voidspace, we as mere devs no longer have direct commit rights for the upstream repo btw
[10:33] <voidspace> I did a fresh fetch --all then checked out upstream/maas-spaces
[10:33] <voidspace> then did a rebase
[10:33] <voidspace> then pushed
[10:33] <voidspace> dimitern: well I did wonder that
[10:33] <voidspace> dimitern: I half expected my push to fail
[10:33] <voidspace> dimitern: if that is indeed the case then we *can't* do a direct rebase, except using the jujubot credentials or via CI doing a merge
[10:33] <voidspace> however the push *appeared* to work
[10:34] <voidspace> but the changes aren't there
[10:34] <dimitern> yeah
[10:34] <dimitern> let's wait for frobware to come back - he has perms
[10:34] <voidspace> cool, he can do it :-)
[10:42]  * frobware back with new shiny keyboard... :)
[10:42] <dimitern> frobware, congrats ;)
[10:43] <frobware> dimitern, dooferlad, voidspace, jam: anything to note from the standup?
[10:43] <dimitern> frobware, we need your expertise (and perms) to do the rebase of maas-spaces :)
[10:43]  * frobware is struck by how nice a new keyboard feels...
[10:43] <dooferlad> frobware: not unless you count dimiter in HD
[10:43] <dimitern> oh yeah - new laptop, new cam, etc.
[10:43] <frobware> dimitern, all working?
[10:45] <dimitern> frobware, now it is - I had issues mostly around getting the 4K screen to work with my external HD monitor
[10:46] <dimitern> frobware, and I somehow managed to mess up the packages yesterday, so this morning it wasn't booting properly and had to reinstall from the usb
[10:46] <frobware> dimitern, eww
[10:47] <frobware> dimitern, voidspace: rebase to master? I see some chat - what's the redux?
[10:47] <voidspace> frobware: I pushed, it vanished
[10:48] <frobware> voidspace, you pushed to hard... :)
[10:48] <voidspace> frobware: I shouldn't be able to push anyway as mere devs don't have push rights to core repo
[10:48] <voidspace> frobware: probably
[10:48] <voidspace> frobware: upshot is, you have to do it as you have perms and we don't
[10:48] <voidspace> frobware: so we're leaving it to you
[10:48] <frobware> voidspace, and in terms of the rebase we're happy to take whatever is on tip this morning?
[10:49]  * frobware will rebase, test, then push
[10:50] <voidspace> frobware: well, I thought putting through CI (and therefore doing a merge not a rebase) was a good idea
[10:51] <voidspace> frobware: however dimitern and dooferlad point out that we need to accept master *anyway*
[10:51] <voidspace> so a rebase is fine
[10:51] <voidspace> with the slight caveat that master currently has tests that fail for me :-(
[10:51] <voidspace> but those are marked as critical and being worked on
[10:52] <frobware> voidspace, shall we choose a different commit for the rebase then?
[10:52] <voidspace> frobware: we could just wait
[10:54] <frobware> voidspace, let's do that; do we urgently need something from master today?
[10:54] <voidspace> frobware: I don't think so, we just don't want to drift too far out of sync.
[11:07] <voidspace> we have a map ordering dependency in a test
[11:07] <voidspace> sometimes it passes, sometimes it fails
[11:07] <voidspace> TestListAllOkay in payload/persistence/env_test.go
[11:14] <voidspace> or a timing issue I guess
[11:17] <frobware> voidspace, that's in maas-spaces, master, somewhere else?
[11:19] <voidspace> frobware: well, I'm looking at my branch
[11:19] <voidspace> frobware: I bet it's on master too - will check
[11:19] <voidspace> frobware: yep, I see it on master too
[11:20] <voidspace> frobware: hard to tell if the ordering is significant
[11:21] <voidspace> frobware: committed by ericsnow in October
[11:21] <frobware> voidspace, I just had successful unit test run on master; was rebasing maas-spaces
[11:23] <voidspace> frobware: it maybe a timing issue, or a wily issue, or something else
[11:23] <voidspace> frobware: but that test fails intermittently for me on master
[11:23] <voidspace> frobware: are you on wily?
[11:24] <frobware> voidspace, nope - trusty
[11:24] <voidspace> right
[11:24] <dimitern> voidspace, I see the same error on wily with go 1.5.1
[11:24] <voidspace> dimitern: I'm using go 1.3.3
[11:24] <voidspace> dimitern: so wily is the common factor
[11:25] <dimitern> voidspace, yeah, seems so - why 1.3.3 btw?
[11:26] <voidspace> dimitern: I built go from source a long while ago
[11:26] <voidspace> dimitern: and have seen no compelling reason to change the version I'm using
[11:26] <voidspace> dimitern: I easily can
[11:27] <dimitern> voidspace, I see
[11:27] <dimitern> voidspace, well, 1.5.1 in wily is slightly faster fwiw
[11:29] <voidspace> cool
[11:29] <voidspace> will switch at some point
[11:38] <fwereade> mattyw, do you recall offhand why api/metricsmanager is using the user-facing ClientFacade stuff?
[11:51] <mattyw> fwereade, I'm about to go afk for 30 mins, happy to talk when I get back
[11:51] <fwereade> mattyw, no rush
[11:52] <mattyw> fwereade, looking at it quickly I suspect it's just bad code - it just needs base.FacadeCaller I think, I'll take a look when I get back an fix it
[11:53] <fwereade> mattyw, no need, I've speculatively hit it already, just wannted to check I wasn't missing something
[12:15] <frobware> voidspace, dooferlad, dimitern: http://reviews.vapour.ws/r/3206/
[12:16] <voidspace> frobware: but if you merge it as a pull request it will appear as a merge
[12:16] <dimitern> frobware, looking
[12:16] <frobware> dimitern, so it needs pushing to upstream/maas-spaces then?
[12:17] <dimitern> frobware, LGTM
[12:17] <dimitern> frobware, yeah
[12:17] <dimitern> frobware, unless CI can pick it up I guess?
[12:27] <voidspace> dimitern: frobware: if CI picks it up it will be a merge not a rebase
[12:27] <voidspace> if should be pushed to upstream/maas-spaces
[12:39] <rick_h_> wallyworld: still around by chance?
[12:39] <wallyworld> a bit
[12:39] <rick_h_> wallyworld: the series in metadata for core, is that in a feature branch or trunk for 1.26?
[12:39] <wallyworld> was featyre branch, merged in last week
[12:39] <wallyworld> bt ony local so far
[12:39] <wallyworld> still wip
[12:39] <wallyworld> need to add forced overrides
[12:40] <wallyworld> also charm store charms
[12:40] <wallyworld> and subordinates and upgrades
[12:40] <rick_h_> wallyworld: ok cool, do we have a list of items needed to wrap it up on the local side? urulama is close to the store end and I want to make sure we've got a path that ties it into a nice bow for delibery
[12:41] <urulama> rick_h_: had a chat this morning, we have a cunning plan :)
[12:41] <wallyworld> there's the spec which defines the overall. there's no done this, need to do that list
[12:41] <wallyworld> and yes, we did talk about it :-)
[12:41] <rick_h_> urulama: :) ok
[12:43] <urulama> rick_h_: i've written the outline of events in the email, but having an action plan would be great, yes. we'll work on it with wallyworld and probably include cmars as well
[12:44] <rick_h_> urulama: ok ty
[12:44] <wallyworld> action plan for series in metadata?
[12:44] <rick_h_> urulama: wallyworld just want to make sure we've got all the parts in sync and no blockers on getting this 1.26 along with the publish stuff.
[12:45] <urulama> wallyworld: yes, series.
[12:45] <rick_h_> wallyworld: a bit bigger, we've got a proof point of making the juju-gui charm one charm, mutliple series, published with the new development channel work, pushed from our CI infrastructure
[12:45] <wallyworld> ok
[12:46] <wallyworld> rick_h_: this was a huge undertaking for the 1.26 timeframe, so the work will be ongoing till the deadlines
[12:47] <rick_h_> wallyworld: understand, just looking ot make sure there's no dead/blocked time so we can make it. Thanks for the heads up that the current work is in master currently.
[12:47] <wallyworld> sure, np
[12:48] <wallyworld> rick_h_: i plan on advertising this to feature buddies for beta1 when the local use cases should be pretty much done (with --force options, etc)
[12:49] <rick_h_> wallyworld: <3 ty
[12:49] <wallyworld> adding support for charm store charms will not be too much extra from a core perspective after that
[12:50] <rick_h_> wallyworld: right, I was just nervous it was still in feature branch and curious how much it would take to get it merged into master as sometimes that seems to take a bit.
[12:50] <rick_h_> wallyworld: my concerns are all put to bed :) you go enjoy your evening.
[12:50] <wallyworld> rick_h_: it did take a bit, but i've done it already :-)
[12:51] <wallyworld> rick_h_: if you definition of enjoy is working on a series in metadata PR, I will have a ball
[12:51] <urulama> :D
[12:51] <urulama> that's a small PR, wallyworld :)
[12:51] <urulama> checking if that's all that needs to change, now, that's another thing :P
[12:52] <wallyworld> i wish it were simple, this current PR has a lot of touch points
[14:17] <marcoceppi> help please bootstrapping agent-version? http://paste.ubuntu.com/13476900/
[14:25] <voidspace> dooferlad: your branch of gomaasapi on launchpad doesn't currently build
[14:25] <voidspace> dooferlad: do you have a version you can push that does build?
[14:25] <dooferlad> voidspace: In the middle of a change, but give me a few minutes
[14:25] <voidspace> dooferlad: cool - thanks! Let me know when.
[14:25] <dooferlad> voidspace: do you have a build error you can pastebin?
[14:26] <voidspace> dooferlad: obviously doesn't need to be feature complete but I'd like to start using the bits that do work
[14:26] <voidspace> dooferlad: line 101 of testservice.go Space undefined
[14:26] <voidspace> dooferlad: the spaces member of the TestServer is map[uint]Space
[14:27] <dooferlad> voidspace: bother, OK.
[14:27] <voidspace> dooferlad: maybe you forgot to add a file?
[14:27] <dooferlad> voidspace: I purposefully didn't, but clearly I need to.
[14:27] <voidspace> heh
[14:42] <dooferlad> voidspace: give that a go
[14:43] <dooferlad> voidspace: example code: http://pastebin.ubuntu.com/13477034/
[14:43] <voidspace> dooferlad:  "github.com/dooferlad/here"
[14:43] <dooferlad> voidspace: no tests for the newest code, but I hope it compiles.
[14:43] <voidspace> dooferlad: in jsonobject.do
[14:43] <voidspace> *.go
[14:44] <dooferlad> voidspace: Eugh, just delete all here references and you will be fine.
[14:44] <voidspace> dooferlad: ok
[14:45] <voidspace> here is used quite a lot in testservice.go
[14:45] <voidspace> dooferlad: is this because you're developing on github and then pushing to launchpad?
[14:45] <voidspace> or some other hack
[14:46] <voidspace> or is it an error logging package
[14:46] <dooferlad> voidspace: it is my debug data logger library. You can go get github.com/dooferlad/here to make it go away
[14:46] <voidspace> dooferlad: cool, I'll do that
[14:46] <dooferlad> voidspace: it is really quite useful for debugging.
[14:47] <voidspace> dooferlad: yay, builds!
[14:47] <voidspace> dooferlad: and I'll look at your debug logger later :-)
[14:47] <dooferlad> voidspace: yay for building!
[14:47] <dooferlad> voidspace: I will brew tea in celebration!
[14:47] <voidspace> dooferlad: :-)
[14:47] <voidspace> me too I think
[14:58] <mattyw> wwitzel3, ping?
[15:16] <dimitern> voidspace, dooferlad, so apparently p&c fixed the hr site and I'm no longer your manager there :)
[15:17] <dimitern> but cadmin is yet to be fixed, so expense claims still come to me
[15:20] <dooferlad> dimitern: congratulations on having less admin to do!
[15:21] <dimitern> dooferlad, cheers :)
[15:38] <sinzui> dimitern: voidspace Do either of you have a minute to review http://reviews.vapour.ws/r/3208/
[15:38] <dimitern> sinzui, LGTM
[15:39] <sinzui> thank you dimitern
[15:56] <dooferlad> voidspace: branch updated
[15:57] <dooferlad> voidspace: minor change in usage. See TestSubnetsInNodes.
[15:59] <mattyw> katco, ping?
[16:00] <natefinch> mattyw: she's out this week
[16:01] <mattyw> natefinch, yeah I only just saw, I pinged before checking the calendar
[16:40] <mup> Bug #1519027 opened: lxd cannot bootstrap with streams <bootstrap> <ci> <lxd-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1519027>
[16:55] <mup> Bug #1519027 changed: lxd cannot bootstrap with streams <bootstrap> <ci> <lxd-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1519027>
[16:58] <mup> Bug #1519027 opened: lxd cannot bootstrap with streams <bootstrap> <ci> <lxd-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1519027>
[17:01] <dooferlad> voidspace, dimitern, frobware: hangout
[17:01] <alexisb> natefinch, you are the only moonstone rep this week correct?
[17:04] <natefinch> alexisb: eric is around more or less this week, but he just moved into a new house over the weekend, so may be in and out.
[17:04] <natefinch> alexisb: otherwise, yes
[17:13] <voidspace> dooferlad: dammit, always catches me by surprise
[17:13] <voidspace> I should check at the start of the day
[18:16] <voidspace> dooferlad: so subnet IDs come in from the test server as integers - which the gomaasapi helpfully turns into float64
[18:16] <voidspace> dooferlad: as far as I can tell this does match what maas itself spits out
[18:16] <voidspace> dooferlad: but it's a mild pain for the code
[18:17] <voidspace> dooferlad: currently it doesn't look like the space name is making it across from the test server though (I'm getting nil back from the json even though the gomaasapi.CreateSubnet has the Space field populated)
[18:48] <voidspace> ericsnow: one of your payload tests fails intermittently on wily
[18:48] <voidspace> ericsnow: maybe a go 1.3+ issue (do you use go 1.2?)
[18:48] <voidspace> ericsnow: and new house?
[18:49] <ericsnow> voidspace: :)
[18:49] <voidspace> :)
[18:49] <ericsnow> voidspace: does it look like #1516541?
[18:49] <mup> Bug #1516541: payload/api/private: tests do not pass <juju-core:Triaged> <https://launchpad.net/bugs/1516541>
[18:49] <voidspace> ericsnow: no
[18:50] <ericsnow> voidspace: k, I'll take a look
[18:50] <voidspace> ericsnow: payload/persistence
[18:50] <ericsnow> voidspace: filed a bug?
[18:50] <voidspace> ericsnow: of course not
[18:50] <ericsnow> voidspace: :)
[18:50] <voidspace> ericsnow: doing it now
[18:51] <ericsnow> voidspace: thanks
[18:52] <voidspace> ericsnow: https://bugs.launchpad.net/juju-core/+bug/1519061
[18:52] <mup> Bug #1519061: payload/persistence intermittent failure <juju-core:New> <https://launchpad.net/bugs/1519061>
[18:52] <ericsnow> voidspace: thanks
[18:53] <voidspace> ericsnow: dimiter sees it too, I use go 1.3 and he uses go 1.5
[18:53] <mup> Bug #1519061 opened: payload/persistence intermittent failure <juju-core:New> <https://launchpad.net/bugs/1519061>
[18:53] <voidspace> ericsnow: we're both on wily
[18:53] <ericsnow> voidspace: k
[18:58] <mup> Bug #1519061 changed: payload/persistence intermittent failure <juju-core:New> <https://launchpad.net/bugs/1519061>
[19:01] <mup> Bug #1519061 opened: payload/persistence intermittent failure <juju-core:New> <https://launchpad.net/bugs/1519061>
[19:04] <mup> Bug #1519061 changed: payload/persistence intermittent failure <juju-core:New> <https://launchpad.net/bugs/1519061>
[19:07] <mup> Bug #1519061 opened: payload/persistence intermittent failure <juju-core:Triaged> <https://launchpad.net/bugs/1519061>
[19:08] <cherylj> frobware: ping?
[19:13] <cherylj> frobware: if you're still around, could you update bug 1516891 with your status?
[19:13] <mup> Bug #1516891: juju 1.25 misconfigures juju-br0 when using MAAS 1.9 bonded interface <juju-core:Triaged by frobware> <MAAS:Invalid> <https://launchpad.net/bugs/1516891>
[19:30] <fwereade> waigani, ping
[19:30] <waigani> fwereade: pong
[19:31] <fwereade> waigani, do you know any of the details of how we auth the per-env api connections for the per-env workers?
[19:32] <fwereade> waigani, can controller-machine-0 always log into its own hosted environments? or do they have separate creds or something?
[19:33] <fwereade> waigani, ("I have no idea" is a perfectly reasonable answer, no need to look stuff up if it's not immediately to mind, I'm just looking for a quick answer if it's there)
[19:33] <waigani> fwereade: right, I was digging :)
[19:34] <fwereade> waigani, np, I can dig myself :)
[19:34] <waigani> okay, yeah of the top of my head all I can say is it's a good question. thumper will be on soon. I'll check with him too.
[19:35] <waigani> fwereade: btw I'm polishing off the system kill. Here's the output: http://paste.ubuntu.com/13468747/
[19:35] <fwereade> waigani, that would be nice, thanks
[19:36] <waigani> and with -v : http://paste.ubuntu.com/13468473/
[19:36] <fwereade> nice :D
[19:36] <fwereade> lovely
[19:36] <waigani> I'm going to add a header and footer message and not count dead environments
[19:36] <fwereade> waigani, yeah, sounds good
[19:36] <waigani> but yeah, it was cool to watch everything go down
[19:37] <fwereade> waigani, very nice indeed
[19:38] <waigani> fwereade: talking with thumper, we thought we'd do the same for environment destroy
[19:39] <waigani> i.e. show the same kind of tapering off status, just with machines and services
[19:39] <fwereade> waigani, <3
[19:40] <fwereade> waigani, soon I'll want it for units per dying service, and units in scope per dying relation :)
[19:41] <waigani> lol
[19:42] <natefinch> fwereade: if you have some time in the next couple days, a review on this would be good... it's the other half of the min version stuff, in the charm repo, with your suggested changes from the other review: https://github.com/juju/charm/pull/176
[19:46] <waigani> fwereade: not sure if this answers your question, but the undertaker worker apiserver endpoint has two auth checks 1. are you a machine agent 2. are you an environment manager
[19:47] <waigani> fwereade: and that worker would be dialing in from machine 0
[19:49] <natefinch> is it just me, or is the help on storage add internally inconsistent?  "a comma separated sequence of: POOL, COUNT, and SIZE
[19:50] <natefinch> juju storage add u/0 data=ebs,1024,3
[19:50] <natefinch> ... pretty sure that's not supposed to be 1024 instances of 3 meg storage
[19:53] <natefinch> maybe it's supposed to be 1024M, and the order doesn't actually matter since the formats are all unique?  ug...
[20:08] <waigani> fwereade: quick answer is, no separate creds as worker agents only come from inside an environ i.e. already authed
[20:11] <mup> Bug #1519081 opened: help for juju add storage is confusing <storage> <juju-core:New> <https://launchpad.net/bugs/1519081>
[20:23] <mup> Bug #1519081 changed: help for juju add storage is confusing <storage> <juju-core:New> <https://launchpad.net/bugs/1519081>
[20:26] <mup> Bug #1519081 opened: help for juju add storage is confusing <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1519081>
[20:31] <fwereade> natefinch, thanks
[20:50] <mup> Bug #1519095 opened: state: tests to not pass with -race under Go 1.2 <juju-core:New> <https://launchpad.net/bugs/1519095>
[21:02] <cherylj> natefinch: did katco talk to you about bug 1517344?
[21:03] <mup> Bug #1517344: state: initially assigned units don't get storage attachments <bug-squad> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1517344>
[21:14] <mup> Bug #1519097 opened: juju/utils/fslock: data race caused by createAliveFile running twice <juju-core:Triaged> <https://launchpad.net/bugs/1519097>
[21:20] <mup> Bug #1514462 changed: Assertion failure in TestAPI2ResultError <ci> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514462>
[21:23] <mup> Bug #1514462 opened: Assertion failure in TestAPI2ResultError <ci> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514462>
[21:26] <mup> Bug #1514462 changed: Assertion failure in TestAPI2ResultError <ci> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514462>
[21:29] <mup> Bug #1514462 opened: Assertion failure in TestAPI2ResultError <ci> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514462>
[21:32] <davechen1y>         for misses := 0; misses < 0; misses++ {
[21:32] <davechen1y> let's count to 2^63
[21:41] <mup> Bug #1514462 changed: Assertion failure in TestAPI2ResultError <ci> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514462>
[21:47] <fwereade> thumper, thank you for the excellent comments in apiserver/admin.go, they were exactly what I needed to know
[21:47] <thumper> :)
[21:56] <davechen1y>                         logger.Debugf("Failed to replace lock, giving up: (%s)", err)
[21:56] <davechen1y> fatal error logged at debug
[21:59] <fwereade> menn0, apiserver/apiserver.go:321 -- we don't statePool.Close until after the tomb.Done
[22:00] <fwereade> menn0, is there a reason? I'd usually expect a tomb.Kill(statePool.Close()) *before* the done
[22:00] <menn0> fwereade: probably a think-o
[22:00]  * menn0 checks code
[22:02] <menn0> fwereade: I remember soon after the StatePool work went in there were panics due to the StatePool being closed too soon
[22:03] <menn0> fwereade:  tomb.Kill(statePool.Close()) before the done seems right to me
[22:03] <fwereade> menn0, ok, interesting, I will take care around there :)
[22:04] <fwereade> menn0, I would hope that the wg.Wait would be enough to get the apiserver's mitts off it
[22:04] <menn0> fwereade: yeah, that should be enough
[22:04] <menn0> fwereade: it's possible I initially had the defers the wrong way around or something
[22:04] <fwereade> menn0, ah yeah :)
[22:04] <fwereade> menn0, thanks
[22:05] <menn0> fwereade: I think originally all the cleanups were separate defer lines
[22:05] <menn0> not trusting my memory too much though
[22:05] <fwereade> menn0, ha, yeah, there's something rather off about that sort of construct
[22:11] <mup> Bug #1510952 changed: Upgrades broken in 1.22 tip <blocker> <ci> <regression> <upgrade-juju> <juju-core:Won't Fix> <juju-core 1.22:Won't Fix> <https://launchpad.net/bugs/1510952>
[23:30] <alexisb> thumper, wallyworld I am going to be a bit late for our next call
[23:30] <wallyworld> ok