[00:55] <natefinch> ericsnow: thanks for the hard work.
[08:59] <voidspace> dooferlad: grabbing coffee
[08:59] <voidspace> 5 mins
[08:59] <dooferlad> voidspace: ok
[09:03] <voidspace> dooferlad: right, omw
[09:04] <dooferlad> voidspace: are you in https://plus.google.com/hangouts/_/canonical.com/sapphire?authuser=0 ?
[09:05] <voidspace> dooferlad: I'm using the link for today
[09:05] <dooferlad> (that authuser=0 may not be 0 for you depending on how many google accounts you are signed into and in what order)
[09:05] <voidspace> dooferlad: yes
[09:16] <dooferlad> voidspace: looks like the standup ended then!
[09:16] <voidspace> dooferlad: you've frozen
[09:16] <voidspace> dooferlad: not sure if it's me or you :-)
[09:16] <voidspace> dooferlad: but yes, reinstalling from scratch sounds good
[09:17] <voidspace> dooferlad: I think so
[09:17] <voidspace> dooferlad: have a good day :-)
[09:17] <dooferlad> voidspace: and you
[09:17] <rogpeppe> if anyone wants to take a look at this fairly simple review, that would be great. https://github.com/juju/names/pull/55/files
[09:19] <rogpeppe> also, some test additions to juju (feature branch) http://reviews.vapour.ws/r/2852/
[10:30] <voidspace> dooferlad: trusty installed, new maas 1.9 installed, now configuring maas (well, fetching boot images currently)
[10:33] <voidspace> rogpeppe: looks like you already got your reviews
[10:33] <rogpeppe> voidspace: yup, thanks for taking a look
[10:34] <voidspace> rogpeppe: heh, np
[10:34] <voidspace> rogpeppe: how's tricks?
[10:34] <rogpeppe> voidspace: pretty good thanks
[10:34] <rogpeppe> voidspace: been working quite a bit on juju-core recently for a change. just like old times :)
[10:34] <voidspace> rogpeppe: same here, glad it's the weekend
[10:34] <voidspace> rogpeppe: life is easier when the team leads are on a sprint
[10:35] <voidspace> rogpeppe: it's been a good week, actually got some work done!
[10:35] <rogpeppe> voidspace: yeah, we've got lots done too :)
[10:36] <rogpeppe> voidspace: as for the weekend, i have some beef vindaloo marinating for saturday and my mouth is watering already
[10:36] <voidspace> rogpeppe: ooh, nice
[10:36] <voidspace> now you're making me hungry
[10:36] <rogpeppe> voidspace: haven't done this particular recipe before but the marinade looks awesome
[10:37] <voidspace> a nice vindaloo is a thing of wonder
[10:38] <voidspace> I should learn to cook
[10:38] <rogpeppe> voidspace: this is the recipe: http://www.munamahdzarfadaaq.com/2013/07/beef-vindaloo.html
[10:38] <voidspace> it's on my list
[10:38] <voidspace> (learning to cook that is - I rely to much on my wonderful but long suffering wife)
[10:38] <rogpeppe> voidspace: curries are pretty straightforward actually
[10:38] <voidspace> rogpeppe: they'd be good to start with as my wife won't cook hot curry :-)
[10:38] <voidspace> although we have a great curry house nearby
[10:38] <rogpeppe> voidspace: not too much subtle chemistry involved, unlike quite a bit of european
[10:39] <voidspace> hehe
[10:39] <voidspace> right
[10:39] <voidspace> I don't do subtle at the best of times...
[10:39] <voidspace> rogpeppe: I've bookmarked the recipe, I'm very tempted
[10:39] <voidspace> thanks
[10:39] <voidspace> rogpeppe: and enjoy :-)
[10:39] <rogpeppe> voidspace: i will
[10:39] <rogpeppe> voidspace: have a good weekend!
[10:40] <voidspace> rogpeppe: we have a big church (from all across the country) celebration this weekend in Sheffield
[10:40] <voidspace> rogpeppe: they're always great fun, lots of life and good to see everyone
[10:40] <voidspace> rogpeppe: so it should be a good one
[10:40] <rogpeppe> voidspace: cool
[10:40] <voidspace> rogpeppe: and tonight I'm off to see the martian with a friend
[10:41] <rogpeppe> voidspace: i need to see that
[10:41] <voidspace> rogpeppe: I've heard mostly good things about it...
[10:53] <voidspace> dooferlad: and after remembering to configure the network properly in maas, node enlisting worked and commissioning in process
[10:53] <voidspace> I may need to do the "setting the power type" dance before I can attempt to bootstrap and see if I can reproduce the bug
[10:57] <voidspace> ah no, can bootstrap without setting power type if I manually start the vms
[10:57] <voidspace> maas used to refuse to let me do that
[11:01] <rogpeppe> voidspace: here's another small review for you if you care to look - we changed our minds on the earlier one: https://github.com/juju/names/pull/56
[11:02] <voidspace> rogpeppe: looking
[11:02] <rogpeppe> voidspace: tal
[11:02] <voidspace> dooferlad: hmmm... looks like I still can't repro the bug with 1.9 alpha 2 from dailybuilds-qa-ok
[11:02] <voidspace> dooferlad: bootstrap is supposed to fail and it works fine!
[11:03] <voidspace> rogpeppe: looks like a nice improvement
[11:03] <rogpeppe> voidspace: thanks
[11:04] <voidspace> LGTM
[11:30] <voidspace> dammit
[11:30] <voidspace> I have maas 1.7 I think
[11:35] <rogpeppe> voidspace: and... here's the juju-core changes resulting from that names package change: http://reviews.vapour.ws/r/2866
[11:35] <voidspace> rogpeppe: up to my knees in broken and confusing maas
[11:35] <voidspace> rogpeppe: will probably be able to get to it in a bit though
[11:35] <rogpeppe> voidspace: np
[11:36] <rogpeppe> voidspace: that would be nice, thanks
[12:23] <voidspace> rogpeppe: why the change to the github.com/juju/utils entry?
[12:23] <voidspace> rogpeppe: the revision hasn't changed but the timestamp has
[12:23] <rogpeppe> voidspace: i know, that's really really weird
[12:24] <voidspace> :-)
[12:24] <rogpeppe> voidspace: i've seen that happen a few times
[12:24] <rogpeppe> voidspace: and i don't know how it can, 'cos AFAIK the time stamp is an immutable property of the commit log entry
[12:24] <rogpeppe> voidspace: it's time-zone related somehow
[12:24] <rogpeppe> voidspace: anyway, the commit hash is the only thing that really matters
[12:24] <voidspace> rogpeppe: ok
[12:25] <voidspace> rogpeppe: got a friend coming for lunch in ten minutes or so - but will carrying on reading until then
[12:25] <voidspace> and pick it up again afterwards
[12:25] <rogpeppe> voidspace: thanks
[12:25] <voidspace> although straightforward changes so far...
[12:28] <voidspace> rogpeppe: it's *all* comment changes, swapping Username for Id and removing of @local
[12:28] <voidspace> rogpeppe: LGTM
[12:28] <rogpeppe> voidspace: yeah, thanks
[12:29] <voidspace> hmmm... except the backwards compatibility issue (potential) noted by mattyw
[12:29] <voidspace> I have yet another screwed maas install *sigh*
[12:30] <voidspace> a vanilla maas 1.9 alpha 2 from dailybuilds doesn't seem to work
[12:30] <voidspace> and that's the only way to get a recent enough maas to reproduce this bug
[12:30] <voidspace> so I give up and will just write my test anyway and leave manual testing for maas to be fixed
[15:09] <mup> Bug #1504578 opened: upgrade fails because the api server cannot get port <blocker> <ci> <regression> <upgrade-juju> <juju-core:Incomplete> <juju-core chicago-cubs:Triaged> <https://launchpad.net/bugs/1504578>
[15:11] <cherylj> cmars: ping?
[15:24] <cherylj> rogpeppe: Could you take a look at bug 1504578?
[15:24] <mup> Bug #1504578: upgrade fails because the api server cannot get port <blocker> <ci> <regression> <upgrade-juju> <juju-core:Incomplete> <juju-core chicago-cubs:Triaged> <https://launchpad.net/bugs/1504578>
[15:24] <cherylj> rogpeppe: cmars volunteered you :)
[15:24] <rogpeppe> cherylj: how privileged am i? :)
[15:25] <rogpeppe> cherylj: i'll take a look
[15:28] <rogpeppe> cherylj: i don't know what the status of critical bugs on feature branches is
[15:28] <rogpeppe> cherylj: does it means we can't do any more work on the feature branch until it's resolved?
[15:28] <rogpeppe> cherylj: (i think probably not)
[16:42] <mup> Bug #1504602 opened: haproxy charm is stuck in an executing state preventing relation changes <juju-core:New> <https://launchpad.net/bugs/1504602>
[16:56] <rogpeppe> does anyone here know about juju version upgrade state migrations?
[16:56] <rogpeppe> we're trying to fix a critical bug here
[17:25] <mgz> rogpeppe: commented on bug 1504578
[17:25] <mup> Bug #1504578: upgrade fails because the api server cannot get port <blocker> <ci> <regression> <upgrade-juju> <juju-core:Incomplete> <juju-core chicago-cubs:Triaged> <https://launchpad.net/bugs/1504578>
[17:26] <mgz> rogpeppe: as I understand it, the second bug from your comment was introduced by that change,
[17:27] <mgz> so we could file another bug for the upgrade not doing what it apparently should
[18:30] <mgz> cherylj: bzrlib portable process life detection code:
[18:30] <mgz> http://bazaar.launchpad.net/~bzr-pqm/bzr/bzr.dev/view/head:/bzrlib/osutils.py#L2531
[18:30] <mgz> http://bazaar.launchpad.net/~bzr-pqm/bzr/bzr.dev/view/head:/bzrlib/win32utils.py#L604
[18:33] <mgz> bug 220464
[18:33] <mup> Bug #220464: Bazaar doesn't detect its own stale locks <lockdir> <locking> <Bazaar:Fix Released by mbp> <https://launchpad.net/bugs/220464>
[18:35] <cherylj> dooferlad: ^^^
[18:35] <cherylj> dooferlad: it's relevant to my review comments for your fslock changes
[18:37] <mup> Bug #1504637 opened: storage: error message for unknown storage is terrible <juju-core:Triaged> <https://launchpad.net/bugs/1504637>
[18:40] <mup> Bug #1504637 changed: storage: error message for unknown storage is terrible <juju-core:Triaged> <https://launchpad.net/bugs/1504637>
[18:43] <mup> Bug #1504637 opened: storage: error message for unknown storage is terrible <juju-core:Triaged> <https://launchpad.net/bugs/1504637>
[19:37] <mup> Bug #1504658 opened: storage: cannot upgrade charms with additional required storage <juju-core:Triaged by axwalk> <juju-core 1.25:Triaged by axwalk> <https://launchpad.net/bugs/1504658>
[19:40] <mup> Bug #1504658 changed: storage: cannot upgrade charms with additional required storage <juju-core:Triaged by axwalk> <juju-core 1.25:Triaged by axwalk> <https://launchpad.net/bugs/1504658>
[19:43] <mup> Bug #1504658 opened: storage: cannot upgrade charms with additional required storage <juju-core:Triaged by axwalk> <juju-core 1.25:Triaged by axwalk> <https://launchpad.net/bugs/1504658>
[20:31] <mup> Bug #1501563 changed: 1.26-alpha1 client gets connection shutdown deploy 1.22 server <blocker> <ci> <regression> <juju-core:Fix Released by cmars> <https://launchpad.net/bugs/1501563>
[21:27] <cmars> mgz, cherylj did we ever get a fix landed for the chicago-cubs issue? was there a bug opened on it?
[21:30] <mgz> cmars: I didn't see a response from rog, but I've been juggling
[21:30] <cmars> mgz, is there a bug open on it?
[21:31] <mgz> cmars: I see no commits
[21:31] <cmars> mgz, ok, thanks
[21:31] <mgz> cmars: bug 1504578
[21:31] <mup> Bug #1504578: upgrade fails because the api server cannot get port <blocker> <ci> <regression> <upgrade-juju> <juju-core:Incomplete> <juju-core chicago-cubs:Triaged> <https://launchpad.net/bugs/1504578>