=== kadams54 is now known as kadams54-away
axwanastasiamac: sent you an email with a few links01:27
anastasiamacaxw: thnx :-001:29
anastasiamacaxw: in terms of appeal - both content and presentation - I think that katco's spec is the winner :-)01:46
anastasiamacaxw: do u know what she used?01:47
axwanastasiamac: yeah. nope, sorry01:47
axwit's certainly more structured than others, which is good for a spec01:47
anastasiamacaxw: and I can see that she has used cucmber for user stories (functional testing)01:47
anastasiamacaxw: structure but also gr8 visuals01:48
menn0waigani: doing this automatic env UUID filtering has exposed some things that were missed with the env UUID migrations03:00
waiganimenn0: that's good03:00
menn0waigani: i've just spent a bit of time tracking down why my branch won't land and it's because EnvUUID wasn't being set on minUnitsDoc03:00
menn0waigani: of course my upcoming branch would fix that automatically but I want to get the query side of things landed first03:01
waiganimenn0: do you want me to set EnvUUID on minUnitsDoc?03:02
menn0waigani: it's ok,. i've just fixed the problem in my branch03:02
menn0waigani: it would be good to know if the minUnits collection was migrated to use env UUIDs in 1.21 though or if that came after03:03
menn0waigani: we might need to add an upgrade step in 1.22 that populates env UUID if it's missing03:03
waiganimenn0: it was migrated in 1.2103:04
waiganimenn0: adding another catchall upgrade step for missing UUIDs sounds like a good idea03:05
menn0waigani: definitely03:05
menn0waigani: I wonder if the existing upgrade step can just be re-run for 1.22?03:05
waiganimenn0: I'd have to take a close look when we come to actually doing it03:07
waiganimenn0: btw the test for your hack to upgrade state 1.20->1.21 fails with my branch, as state tests now have two states/envs by default. My solution is to destroy the second env and close the second state for that test.03:07
menn0waigani: which hack is that?03:08
waigani// StateServerInfo contains a hack that assumes a single environment. This03:09
waigani// hack is executed when environmentDoc is missing the env-uuid field, as03:09
waigani// in the case below. As such, we destroy the other environment and close03:09
waigani// OtherState to emulate the expected single environment state.03:09
waiganimenn0: test = TestStateServerInfoWithPreMigrationDoc03:09
menn0waigani: right. i think what you've done is probably ok.03:10
waiganimenn0: it makes that test more ugly, but I think it is better to keep that test the exception and the  default to be for two envs to be set up for state tests03:12
waiganias this is the new world that the code needs to work in03:13
* menn0 nods03:13
axwdavecheney: I'm going to move state/storage.go to a new package, state/storage, and state/tools.go -> state/storage/tools03:48
axwdavecheney: state/toolstorage -> state/storage/tools too03:49
axw(just letting you know because you've been moving bits around in that area)03:49
menn0waigani: the branch that automatically adds env UUID when querying is in04:10
menn0waigani: http://reviews.vapour.ws/r/594/diff/ removes many of the docID calls that are now unnecessary04:10
menn0waigani: can you PTAL?04:11
waiganimenn0: just gave it a shipit04:12
menn0waigani: cheers04:13
davecheneyaxw: -1 to two new packages04:14
davecheney+0 to state/storage04:14
davecheneyas long as state/storage doesn't import state, i'm fine with this04:14
davecheneytools is a shitty pacakge name04:15
davecheneystate/storage/storagetools  if you must04:15
axwdavecheney: state/storage is fine with me. it will not depend on state04:16
axwI'll leave the existing toolstorage one alone then. never was happy with the name, but storagetools sounds like tools for dealing with storage rather than a place to store tools04:17
menn0davecheney or axw: would you mind quickly looking over http://reviews.vapour.ws/r/594/ ?04:19
davecheneymenn0: LGTM04:23
davecheneythank god for tat04:23
menn0davecheney: and there's a lot more of that kind of thing coming up04:24
menn0damn... my last branch (already merged) broke upgrades04:44
menn0waigani: hmmmm looks like there's no unit test for the pre-migration settings loading hack04:52
=== kadams54_ is now known as kadams54-away
menn0upgrade problem fixed without reverting. fix merging now.05:14
mattywmenn0, ping?05:54
=== urulama_ is now known as urulama
dimiternjam1, 1:1?07:32
jam1dimitern: yeah, brt07:32
fwereadejam1, it's a public holiday and I'm going out for breakfast but I should be back for our chat07:38
jam1fwereade: enjoy07:38
fwereadeanastasiamac, likewise, I should be free for ours later07:38
menn0mattyw: hi. i've got to head out for a bit but i'll be back later on08:29
mattywmenn0, no problem, I'm in gmt+8 at the moment so we can just discuss it tomorrow08:30
anastasiamacfwereade: i'd rather talk tomorrow then :-) enjoy ur holiday!09:01
voidspacejam1: dimitern: standup?10:02
dimiternvoidspace, omw10:02
jam1voidspace: just a few, be there soon10:02
=== ashipika1 is now known as ashipika
=== kadams54 is now known as kadams54-away
voidspacedimitern: when you get a chance http://reviews.vapour.ws/r/596/12:44
dimiternvoidspace, sure, in a moment12:44
voidspacedimitern: I'm taking a break anyway, so no massive hurry12:45
dimiternvoidspace, reviewed13:23
voidspacedimitern: thanks14:16
dimiternvoidspace, please ping me if something is not clear14:17
voidspacedimitern: I think the major concerns you have are entirely unwarranted :-)14:18
voidspacedimitern: I will try to explain why14:19
voidspacedimitern: after I get coffee14:19
dimiternvoidspace, :) ok, I'm listening14:19
voidspacedimitern: I don't think there is any race condition at all14:19
voidspacehmmmm... actually, *maybe* there is14:19
voidspacedimitern: however you're incorrect about state filtering of addresses14:20
dimiternvoidspace, exactly - between the time you read the initial list of addresses and you try to add a new one14:20
voidspacedimitern: right14:20
voidspacedimitern: so we need to check the return value of AddIPAddress and retry on failure14:20
dimiternvoidspace, that one I rephrased several times - I understand what allocated map is for (name could be better yes)14:20
voidspacedimitern: but TestPickNewAddressIgnoresUnavailableAndAllocated doesn't make sense14:20
dimiternvoidspace, well with that test now it will pass when it shouldn't14:21
voidspacedimitern: no, more specifically14:21
voidspacedimitern: see my reply to your comment on line 254 subnets.go14:22
voidspacedimitern: and the for loop doesn't need a max tries - the algorithm guarantees it won't go on forever14:22
voidspacedoorbell (and coffee)14:23
dimiternvoidspace, yes - the map can be used to track all addresses, regardless of their state14:23
dimiternvoidspace, so the allocated map will work fine, just the retrying needs to be in place and the two-step allocation14:24
dimiternvoidspace, i.e. find an available address - create it as "unknown" if it still does not exist; if it does (regardless of state) - retry14:25
dimiternvoidspace, sorry, now I realize PickNewAddress shouldn't mark the address as allocated14:26
voidspacedimitern: no, it creates it Unknown for the provider to allocate (or fail)14:26
dimiternvoidspace, it should only add is as a placeholder ("Unknown") until tried to allocate it and either got OK (then set it to allocated) or error (set it to unavailable)14:27
dimiternvoidspace, yeah14:27
voidspaceAddIPAddress does this for us anyway14:27
sinzuidimitern, voidspace perrito666 . Win builds broke. I think a win dep is missing: http://juju-ci.vapour.ws:8080/job/win-client-build-installer/1362/console14:28
dimiternvoidspace, ok, but it will be helpful to have a comment about it - before AddIPAddress, ideally in the PickNewAddress doc comment as well (... creates an address with AddressStateUnknown..)14:28
dimiternsinzui, looking14:29
dimiternsinzui, it appears the regression occurred quite some time ago - commit https://github.com/juju/juju/commit/99c2bcd0de788321a73d1c32ed5c114dbe9adb89 - Sept, 3014:33
dimiternsinzui, were the windows builds not tested in a while?14:33
sinzuiWe test EVERY run14:33
sinzuiand that is why we knew the regression from last week was fixed14:34
dimiternsinzui, ok, I'll dig deeper then14:34
sinzuidimitern, http://juju-ci.vapour.ws:8080/view/Juju%20Revisions/job/win-client-build-installer/1359/console is the last pass from Friday14:34
sinzuiI am looking for the candidate revs14:34
sinzuidimitern, This is what we know about the windows failure https://bugs.launchpad.net/juju-core/+bug/140034414:48
mupBug #1400344: Windows dependencies broken <ci> <regression> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1400344>14:48
dimiternsinzui, I can't see how a missing dependency can cause this build failure and how it did pass before14:54
sinzuidimitern, okay. For each release tarball, we due a redundant setup for cross compilation on windows for386 and amd64. That is what you may have seen in the log. I think that kind of ensures no one tampered with our go setup between runs. The script then build 386 to make the win client, then builds amd64 to make the win agent14:56
dimiternsinzui, that sounds sensible to me14:57
wwitzel3fwereade: ping14:58
fwereadewwitzel3, pong14:58
wwitzel3fwereade: oops, just saw the calendar, you're on holiday I won't bother you :)14:59
dimiternsinzui, i'm still looking for the root cause though14:59
bogdanteleagastat_t doesn't exist on windows14:59
bogdanteleagaif you're still on that14:59
fwereadewwitzel3, if it's quick it's fine15:00
fwereadewwitzel3, because then I can hit you up for a review of http://reviews.vapour.ws/r/598/ which is directly relevant to your interests15:00
fwereadewwitzel3, ;p15:01
wwitzel3fwereade: I wanted to chat about min version, probably not likely to be quick15:01
wwitzel3fwereade: I will take a look15:01
fwereadewwitzel3, ok, natefinch is hopefully circulating it among users for great clarity and sanity15:01
dimiternsinzui, this is the commit that introduced the regression I think - https://github.com/juju/juju/commit/99c2bcd0de788321a73d1c32ed5c114dbe9adb89 (3 days ago)15:05
dimiternkatco, ping15:05
natefinchericsnow: sorry to hear you didn't get the job at Canonical15:05
ericsnownatefinch: lol me too!15:05
katcodimitern: howdy15:06
sinzuidimitern, That is very interesting because there is *another* regression that relates to metadata. I just reported https://bugs.launchpad.net/juju-core/+bug/140035015:06
mupBug #1400350: metadata_test consistently fails in ppc64el unit tests <ci> <ppc64el> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1400350>15:06
katcoericsnow: natefinch lol i JUST got the same email15:06
natefinchkatco: really?  That's hilarious15:06
ericsnowkatco: sorry to hear it!15:06
wwitzel3fwereade: ok, thanks, there must be a doc I haven't seen yet, the doc I have for min version is basically blank :)15:06
katconatefinch: yep. apparently i've outstayed my welcome! (sniff)15:06
ericsnowkatco: mine was from Good Luck Jonathan ;)15:07
dimiternkatco, can you tell me more info about this commit - https://github.com/juju/juju/commit/99c2bcd0de788321a73d1c32ed5c114dbe9adb8915:07
ericsnowkatco: j/k15:07
natefinchericsnow, wwitzel3, perrito666 : BRT15:07
katcoericsnow: haha15:07
dimiternkatco, it appears it introduced a regression for windows builds15:07
katcodimitern: it looks like ericsnow authored this?15:07
katcodimitern: sorry, am i missing something?15:08
dimiternkatco, hmm..  sorry I meant https://github.com/juju/juju/commit/0c7de1a60355b3dfa3b5db23b9b5551680eae76e15:08
ericsnowkatco, dimitern: curse you syscall!15:08
dimiternkatco, it seems like a backport of some sorty15:09
katcodimitern: ahhh ok15:09
dimiternericsnow, yay, windows :)15:09
dimiternkatco, but that seems a merge into some feature branch, not master, 1.21 or 1.2015:10
katcodimitern: yeah trying to make sense of this. definitely a merge, but into what?15:11
natefinchericsnow, katco: https://www.youtube.com/watch?v=F4eCd6xUSik15:11
dimiternsinzui, that ppc failure it due to the same thing btw15:12
dimiternericsnow, was that change necessary just to access the creation time of the backup?15:13
sinzuidimitern, I agree, and jog just noted that the recent failures in run-unit-tests-precise-i386 are about that test15:13
katcodimitern: ok, looks like that was me trying to land my leadership/lease branch. it wouldn't do an automatic merge so i merged locally.15:13
dimiternkatco, on master though, or?15:14
katcodimitern: sinzui: do we have a test run from commit https://github.com/juju/juju/commit/216aa121c173b625f6417f3ac3ca8f960c862a38?15:14
katcodimitern: yes on master15:14
dimiternkatco, right, thanks for confirming15:14
katcodimitern: is this a regression on master, or 1.21, or?15:15
katconothing in my branch should have caused a regression unless i merged incorrectly15:15
sinzuikatco, I don't think that was the merged rev15:15
katcosinzui: sorry, can you rephrase that?15:16
dimiternkatco, it appears it affects only master15:16
katcodimitern: oh, well at least that's good news15:17
sinzuikatco, that rev isn't listed because git merged it as a different commit hash.15:17
wwitzel3fwereade: I went through that code 3 times and I am disappointed to say I couldn't find anything wrong :p15:17
dimiternkatco, what you merged actually came from an earlier commit by ericsnow - https://github.com/juju/juju/commit/99c2bcd0de788321a73d1c32ed5c114dbe9adb8915:17
ericsnowdimitern: yep, that's the one15:18
katcodimitern: right... so... is it my code, or what i merged?15:18
* katco is a little slow pre-coffee o.015:18
dimiternericsnow, and there's a related test - https://github.com/juju/juju/commit/d5044f634bbe569271f589de2f15ba7f3e1fece8 which will fail on non-linux environments15:18
sinzuikatco, I am looking at the range, but looking at http://reports.vapour.ws/releases, we can see when 1.22-alpha1 starts to fail15:19
dimiternkatco, it appears to me you've merged a bunch of changes, some of them earlier on master, but the merge overwrote some of the hashes or something - that's why it doesn't show the source immediately15:19
katcodimitern: so i have performed the merge incorrectly?15:21
sinzuikatco, http://reports.vapour.ws/releases/2152 is the first build with that revision15:21
katcosinzui: so http://reports.vapour.ws/releases/2150 is the more likely candidate?15:22
dimiternkatco, I don't think so - you've merged what was on master already - landed with ericsnow's https://github.com/juju/juju/pull/123815:22
sinzuikatco, There are many regressions in master right now15:22
katcodimitern: ah ok.15:22
voidspacedimitern: I have something that automatically adds new imports when I need them - I almost never do them manually15:23
sinzuikatco there we have opened three so far, and we may open more when we know why manual env tests fail15:23
voidspacedimitern: which is my excuse for how they *always* end up in the wrong place...15:23
voidspacedimitern: I need to start checking them in the diff...15:23
voidspacedimitern: sorry15:23
katcovoidspace: i have the same problem15:23
voidspacekatco: I have a foolproof way of checking them15:24
voidspacekatco: get dimitern to review...15:24
dimiternvoidspace, I know, I use goimports as well - it does screw up sometimes when removing imports it can remove blank lines between groups15:24
katcovoidspace: we should really write a linter so these kinds of things don't clog up reviews15:24
voidspacesounds good15:24
voidspacecheck for doc comments and a few other stylistic issues15:25
dimiternkatco, voidspace, I was actually considering proposing a patch for goimports to fix this, but the process is a bit long15:25
katcothat is one of my cardinals rules of reviews, let's not discuss style guidlines we've already agreed upon15:25
katcodimitern: it would be much appreciated15:25
katcodimitern: yeah looking at the diff b/t my fork and master, i don't think this would have caused a regression on other platforms: https://github.com/katco-/juju/commit/a632fb4237a2da1cebfcb136874bed665644d40815:26
katcosame thing from juju/juju perspective: https://github.com/juju/juju/commit/a632fb4237a2da1cebfcb136874bed665644d40815:27
dimiternkatco, it does look fine, although I just had a quick look around - checking for syscall and map comparisons15:30
dimiternericsnow, alright so you'll be fixing those two related to Stat_t ?15:33
katcodimitern: lmk if i can help at all. otherwise moving onto planned work!15:34
dimiternkatco, sure, but if ericsnow is already on it I think it's fine15:36
ericsnowdimitern: I'm going to fix bug #1400350 and I expect that will fix 1400344 too :)15:37
mupBug #1400350: metadata_test consistently fails in ppc64el unit tests <ci> <ppc64el> <regression> <test-failure> <juju-core:Triaged by ericsnowcurrently> <https://launchpad.net/bugs/1400350>15:37
katcoericsnow: your job is on the line apparently! ;)15:38
dimiternericsnow, :) yeah, it appears so15:38
ericsnowkatco: lol, yours too!15:38
katcoericsnow: haha15:38
ericsnownatefinch: for the windows-only file I put "// +build windows" at the top, right?15:58
ericsnownatefinch:  and "// +build !windows" for the non-windows file?15:58
natefinchericsnow: or _windows.go for the windows one (but yes, you need // +build !windows for the non-windows one15:58
ericsnownatefinch: the filename doesn't impact the compilation related to windows, does it?15:59
ericsnownatefinch: I have metadata.go, metadata_windows.go, and metadata_unix.go16:00
ericsnownatefinch: the special-case files just defined the OS-specific functionality as a function that metadata.go calls16:00
natefinchericsnow: yes it does.  _<os/arch>.go will be treated the same as // +build <os/arch>16:00
ericsnownatefinch: (on windows the func is empty)16:00
ericsnownatefinch: sweet16:00
natefinchericsnow: I prefer the filename version because it's much more obvious... it's fairly easy to miss the build tag at the top of a file16:01
ericsnownatefinch: agreed16:01
natefinch(but you can't do fancy stuff like !windows with the filename version)16:01
ericsnownatefinch: got it16:01
ericsnownatefinch: if you got a sec, take a look: http://reviews.vapour.ws/r/599/16:04
katcoto be entertained: traceroute
ericsnowkatco: nice!16:11
natefinchtraceroute isn't installed by default?  Geez, even windows has that preinstalled.16:24
natefinchAlso.... awesome.  Though they should slow down the ping times between them to give a more dramatic effect :)16:25
katconatefinch: lol not sure if it's an actual network they need to work16:25
natefinchkatco: "damn, the web server is pegged again, go reboot 'against.the.evil.Galactic.Empire'"16:26
katconatefinch: rofl16:26
voidspacedimitern: about to finish this16:26
voidspacedimitern: do you have something else I can move onto?16:26
voidspacedimitern: I'm asking now so I catch you before you EOD16:27
dimiternvoidspace, just a sec16:27
voidspacedimitern: sure16:27
voidspacedimitern: I still need to write a test for the race16:27
voidspacedimitern: although it's fixed16:27
voidspaceas are the other issues16:27
dimiternvoidspace, nice!16:27
dimiternvoidspace, there is one thing that comes to mind16:29
dimiternvoidspace, I believe we have what's necessary to implement Subnets() on ec216:29
voidspacedimitern: do we not have it?16:30
voidspacedimitern: I thought we did16:30
voidspacedimitern: Subnets(instanceId)16:30
dimiternvoidspace, I still see it as returning notimplementedf16:31
voidspacedimitern: indeed, me too16:31
voidspaceI thought we had it16:31
dimiternvoidspace, we have it for maas16:31
dimiternvoidspace, it should be quick and easy - returning all subnets (there will only be default vpc subnets for now, but that's fine)16:32
voidspacedimitern: ok, do you know the ec2 call off the top of your head?16:32
voidspaceif not I can look into it and shout if I get stuck16:32
dimiternvoidspace, one quirk though - AllocatableIPLow and AllocatableIPHigh need to be set so we respect AWS limits16:32
dimiternvoidspace, the api call is DescribeSubnets, but in goamz it's called Subnets16:32
voidspacedimitern: so we need to extend network.BasicInfo to include that info I think16:33
voidspacedimitern: then possibly adjust the maas implementation to fill this in too16:33
dimiternvoidspace, the aws docs says the first 4 and the last ip in a subnet cidr are reserved I think16:33
voidspaceI'll check on that16:33
dimiternvoidspace, but please double check16:33
dimiternvoidspace, well we'll need to add the high/low range to network.BasicInfo anyway16:35
voidspacedimitern: ok16:35
dimiternvoidspace, maybe even rename that to SubnetInfo ?16:35
voidspacedimitern: I'll see how it's used elsewhere16:36
voidspacedimitern: that sounds better for us16:36
voidspacebetter in general16:36
dimiternvoidspace, yeah, I think it sounds better in the face of recent changes :)16:36
ericsnowsinzui: two of the backups blockers should be fixed now (1400344 and 1400350)16:54
ericsnowsinzui: (same fix)16:54
sinzuithank you ericsnow16:55
ericsnownatefinch: i've updated http://reviews.vapour.ws/r/557/17:09
ericsnownatefinch: FYI, you're the only one who hasn't recused themself from a LGTM :)17:09
ericsnownatefinch: if you don't feel up to it I'll see if axw will tackle it17:10
lazyPoweris there a way to specify the hookenv you want to execute a juju run command in? juju run -h doesn't say17:40
lazyPowerreason being, i'd like to see what was sent otw without entering debug hooks if i can get away with it - hackedbellini is experencing an issue wrt some data being sent by postgres and it seems really cumbersome to have to deploy a second unit, attach debug hooks, and step through an entire deployment to get at that data.17:41
marcoceppiwwitzel3: ^17:42
wwitzel3lazyPower: no, not currently.17:47
wwitzel3lazyPower: in master we have the ability to do that with juju-run17:47
lazyPowerwwitzel3: ack, i figured that was the case for now.17:48
wwitzel3natefinch: I'm going to grab lunch, want to talk gce when I get back?17:53
lazyPowerwwitzel3: wait - i just saw a drop in #juju from stub about juju run -r relation:id - is this the current trunk capability?18:02
ericsnownatefinch: could you take a quick look at http://reviews.vapour.ws/r/600/ (for CI blocker)18:19
natefinchericsnow: looking18:22
ericsnownatefinch: ta18:22
* natefinch gives ericsnow a ship it with a moral quandry.18:28
ericsnownatefinch: k18:28
katcohave to run to the dr. bbiab18:30
natefinchDr Bbiab must have a hard time with people misspelling his name.18:31
natefinchsorry his/her  ... don't want to presume18:31
voidspaceg'night all18:40
wwitzel3lazyPower: yes, -r is in trunk for juju-run, but not juju run18:51
natefinchwwitzel3: re: gce, yes, in a couple minutes18:56
wwitzel3natefinch: sounds good, just ping me when you're ready18:56
=== fuzzy_ is now known as Fuzai
natefinchwwitzel3: I'm in moonstone19:36
wwitzel3natefinch: omw19:37
ericsnownatefinch, wwitzel3 mind if I join in?19:48
ericsnownatefinch, wwitzel3: I'm going to assume not :)19:50
=== kadams54 is now known as kadams54-away
alexisbnatefinch, on the hangout when you are ready20:34
wwitzel3alexisb: we are wrapping up some google provide hand off stuff, he'll be right there :)20:35
alexisbwwitzel3, heh no rush20:35
alexisbI have plenty to keep me occupied in the meantime20:35
menn0does anyone know how to get the landing bot to look at a branch again when a previous merge attempt was manually cancelled?20:37
menn0thumper: ^20:37
thumpermenn0: try the merge magic string again?20:38
menn0thumper: I did that20:38
* thumper shrugs20:38
menn0thumper: I think previously wallyworld had to do something20:38
menn0thumper: it's something to do with the bot not seeing it's own fail message in the conversation20:39
menn0I wonder if I just copy a failure from elsewhere...20:39
thumperah... sorry don't know what to do there20:39
menn0thumper: I'm trying a few things. it's academic anyway since CI is blocked.20:41
menn0thumper: that totally worked though :) I just copied a "Build failed..." message from elsewhere and then the bot was happy to consider the branch again.20:42
menn0thumper: of course it didn't get anywhere due to CI being blocked20:42
natefinchalexisb: hi, sorry, coming20:44
ericsnowcould I get a second opinion on http://reviews.vapour.ws/r/557/#comment5998?20:45
menn0is anyone looking at bug 1400348?20:50
mupBug #1400348: Azure deployment broken <azure-provider> <bootstrap> <ci> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1400348>20:50
=== kadams54-away is now known as kadams54
thumpermenn0: I have noticed a few intermittent failures in jujud around logging in during upgrade21:01
thumpermenn0: have you seen these?21:01
menn0thumper: yep. there's a ticket for that which I plan on getting to soon.21:02
thumpermramm: chat time?21:02
mrammsure thing, I'm in the hangout21:03
thumpermramm: so am I21:04
thumperdumb googld21:05
thumpermenn0: care to look at that azure bug?21:43
menn0thumper: I was thinking about it. i've already sent axw some questions for when he starts21:44
menn0thumper: do we have a company account to access azure that I can use?21:44
katcoany lxc experts? could use some help debugging an issue in canonical/#juju21:44
menn0thumper: or should I set up my own?21:44
thumpermenn0: could ask sinzui21:44
menn0thumper: actually... I think I know where some creds might be22:04
sinzuimenn0, I can help22:05
menn0sinzui: great22:06
menn0thumper: I have what I need from sinzui so I'll start on that bug now22:14
thumpermenn0: thank you22:28
katcoaxw: ping you on yet?22:40
anastasiamackatco: it's about 7am where andrew is...22:44
anastasiamache usually jumps in in around 3hrs... just before our standup...22:44
anastasiamackatco: well in about 2hrs now... :-)22:45
katcoanastasiamac: yeah just thought i'd check. do you recall if ian was working on an issue with certs and simple streams?22:45
katcoanastasiamac: it's ringing a bell but i can't place it22:45
anastasiamackatco: both ring a bell22:45
anastasiamackatco: i thought that he landed the cert stuff...22:45
katcoanastasiamac: i'm wondering if i'm thinking of this: https://bugs.launchpad.net/juju-core/+bug/139790922:45
mupBug #1397909: State server certificate has empty SAN list <juju-core:In Progress by wallyworld> <https://launchpad.net/bugs/1397909>22:46
anastasiamackatco: sounds rite...22:46
anastasiamackatco: Merge pull request #1241 from wallyworld/update-server-certificate22:51
anastasiamackatco: about 3 days ago...22:52
katcoanastasiamac: thanks, but if that's what i'm thinking of then it's not appropriate22:52
anastasiamackatco: k :-)22:52
menn0thumper: I can easily duplicate that problem but I'm having a hard time understanding why it's azure specific23:07
menn0thumper: trying on ec2 now as a sanity check23:07
menn0thumper: then will try to narrow down the commit but I'm pretty sure it's wallyworld's credupdater worker23:07
anastasiamackatco: well done for solving that issue on #juju23:16
anastasiamackatco: thnx for the email too23:16
anastasiamackatco: emacs...23:17
=== urulama_ is now known as urulama
katcoanastasiamac: mwhudson helped a lot23:17
anastasiamackatco: team work is amazing :)23:18
katcoanastasiamac: np about the email. yes, i agree mentioning the word emacs brings calm and joy to an irc chatroom ;)23:18
katcounlike the editor which shall not be named!23:18
mattywmorning all23:34
katcogood morning mattyw23:35
mattywkatco, what time is it for you?23:35
katcomattyw: 17:3523:35
anastasiamackatco:  m sure it thinks of itself as IDE not an editor23:37
katcoanastasiamac: what, emacs?23:37
anastasiamackatco: IDEA23:37
anastasiamackatco: but m not racist and m happy to try emacs23:38
katcowhat would be the correct term for one who discriminates against editors?23:38
mattywkatco, foolish?23:40
katcomattyw: lol, yes i'd say so.23:40
mattywanastasiamac, what do you use at the moment?23:40
mattywanastasiamac, also - hi!23:40
anastasiamacmattyw: hi :-)23:40
anastasiamackatco: considering E in IDE is an environment = environmentalist?23:41
anastasiamacmattyw: IntelliJ23:41
katcoenvironmentalist, i like that23:41
anastasiamackatco: :)23:41
anastasiamackatco: but neither u nor I r that23:41
anastasiamackatco: i just live conflict resolution GUI in IntelliJ23:42
katcoanastasiamac: absolutely not. i support everyone's right to use a totally-worse-than-emacs editor :)23:42
anastasiamackatco: m glad u clarified :-)23:42
menn0thumper: so the CI blocker was definitely introduced by the 009aef5 merge23:47
=== kadams54 is now known as kadams54-away
menn0thumper: it's a pretty big change which introduces a new jujud worker23:49
menn0thumper:  git log  009aef5~..009aef523:49
menn0thumper: do I try to rip the whole thing out or try to fix the issue?23:50
menn0thumper: I've ripped it out (only one conflict) and am running tests23:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!