cheryljdavecheney: thanks!00:00
waiganithumper: do you also not want the username quoted in the error returned by the apiserver?00:27
thumperI think quoted is fine from the api server as it is developer facing00:28
waiganithumper: yep, wrote too quickly - I see we use %q in the rest of the errors in that package00:29
thumperwine time04:36
waiganiwallyworld: thanks for the review. I've responded to your comments, but can't seem to update my diff.04:41
wallyworldwaigani: i saw the replies, so marked at +104:41
waiganiwallyworld: okay thanks04:42
wallyworlddimitern: heya06:43
dimiternwallyworld, morning06:43
wallyworldgod weekend? i hope you gots sleep :-)06:43
dimiternwallyworld, :) ~18h in total06:44
wallyworldi have a question - kat finished some goamz signing work, and it's now merged. but it looks like stuff is missing in the v3 branch, i've done a pr  https://github.com/go-amz/amz/pull/3306:45
wallyworldi'm testing the storage stuff live, but was wondering if you could test the network stuff as i don't have enough to go on with what to test06:46
dimiternwallyworld, yeah - I was just looking at your two PRs in amz.v3 after v3-unstable was promoted to v306:47
wallyworldi've pull her juju-core branch to test juju live katco-:goamz-v3-support06:48
dimiternwallyworld, I thought I *did* compare v2 to v3 to see if something was missing but apparently I missed something06:49
wallyworlddimitern: stupid irc dropped out, not sure if i missed any reply06:55
dimiternwallyworld, I was looking at https://github.com/go-amz/amz/compare/v1...v2 and https://github.com/go-amz/amz/compare/v2...v306:56
wallyworldyeah, the v2..v3 diff what what i based the pr on06:56
dimiternwallyworld, but I can't see the changes in the PR to be missing from v3?06:57
wallyworldhmm, maybe i had an out of date local copy06:58
wallyworldlet me check06:58
dimiternwallyworld, that's might be - esp. if you're using symlinks in your gopath06:58
wallyworldhmm, i just git pulled in my v3 master and no updates06:59
wallyworldi'll look around a bit06:59
wallyworlddimitern: so as an example, in https://github.com/go-amz/amz/tree/v3/ec2 there's no blockdevicemappings_test.go07:01
wallyworldthat file should be there and is in v207:01
dimiternwallyworld, thats true, but why it doesn't show up on the v2..v3 diff?07:02
wallyworldyeah, and there's a bunch of network stuff missing too07:03
dimiternwallyworld, ok, I'll do the diff locally to be sure07:03
dimiternwallyworld, apparently github compare lies07:03
wallyworldthere must be a logical reason you'd think07:04
* dimitern keeps digging 07:07
dimiternwallyworld, for some reason even though v3 was branched off v2 some commits in v2 are missing07:18
wallyworlddimitern: fwiw, with the go-amz branch in pr 33, the new juju storage stuff works live, and the unit tests pass. the networking stuff fails live for me because of vpc limits07:18
dimiternwallyworld, can connect to the ec2 web ui with the shared creds or you just have the api keys?07:19
wallyworldi never use the web ui, just ElasticFox07:19
wallyworldi have the api keys also for juju07:20
dimiternwallyworld, you can clean up the stale vpc from there07:20
dimiternwallyworld, if you have the account to login to the web ui can you send them to me by mail along with the api keys?07:21
wallyworldok, i'll see if i have it07:21
dimiternwallyworld, in the PR #33 there are still some things missing from v2 btw07:23
wallyworldah, ok07:23
dimiternwallyworld, but not much, so if you go ahead and merge that, I'll propose a follow-up to add the missing07:24
wallyworlddimitern: ok. i have access to a web ui, using my canonical.com email as the user name, but it appears to be a different account to that controlled using the api keys i have and which i use with elastic fox07:27
wallyworlddimitern: ok, that's merged07:28
dimiternwallyworld, ok, I'll ask jam if he has them07:28
dimiternwallyworld, thanks!07:28
wallyworlddimitern: once your stuff lands, i'll update a fork of kath's branch i have and land that in core07:28
dimiternwallyworld, ok, will let you know07:29
wallyworldok, i might duck off to have dinner07:29
Muntanergood morning devs o/08:27
MuntanerI'm writing my first charm and having some problems, can anybody help me?08:27
dimiternMuntaner, morning! try asking in #juju08:33
dimiternfor all your charming needs :)08:33
Muntanerdimitern, ty ;)08:33
dooferladdimitern, TheMue: morning08:37
dimiternTheMue, dooferlad, morning folks!08:38
TheMuedooferlad: dimitern: o/08:38
dooferladdimitern: heard anything from voidspace?08:38
dimiterndooferlad, he become a dad over the weekend08:39
dooferladdimitern: awesome!08:40
TheMueaaah, fantastic news08:40
dimiternso I guess he won't be here today08:40
dimiternyeah indeed :)08:40
dimiternI've seen pics on FB08:40
TheMueoh, dedn't know he's on FB, so far only G+. while have a look08:41
TheMuefound and added him ;)08:43
jamdimitern: sorry I misesd you earlier, just missed the schedule. what's up with ec2?08:54
jamwallyworld: maybe you know?08:55
dimiternjam, minor mishap with some missing commits from amz.v2 into amz.v3, but wallyworld sorted that out08:55
jamdimitern: k, I thought there was something you needed w VPC08:55
dimiternjam, I'm now manually comparing amz.v2 to the updated amz.v3 to make sure all is good, then I'll do a live test08:55
jamdimitern: I do see a spare network interface in us-east-108:56
dimiternTheMue, sorry, I'll be 10m late for our 1:109:00
TheMuedimitern: ok09:01
dimiternwallyworld, jam, I'm happy to report after that PR #33 landed amz.v3 has everything is needs wrt storage and networking09:06
dimiternI'll still need to do a live test later though09:06
dimiternTheMue, I'm in the hangout09:12
TheMuedimitern: coming09:12
dimiternaxw, katco, jam, wallyworld, is anyone using the shared aws account for testing now?09:38
dimiternI'm thinking of cleaning up the stale VPCs, subnets, security groups, etc.09:38
dimiternunless anyone responds in the next half hour, I'll go ahead and do it09:39
perrito666dimitern: for me go for it09:48
dimiternperrito666, +109:49
jamdimitern: I'm using eu-west-1 for a live service10:11
jam(my IRC proxy)10:11
jambut nothing in US-east-110:11
dimiternjam, ok10:11
wallyworlddimitern: sorry, had to go down to soccer at short notice10:41
dimiternwallyworld, np. s'all good :)10:42
wallyworlddimitern: once you're happy with goaws, I'll land a branch to update core10:42
dimiternwallyworld, I still need to do a live test, so I'll let you know; but looking at the code it should work10:43
wallyworldok, sounds good10:43
wallyworldi did a storage live test and it was good too10:43
dimiternwallyworld, cool!10:44
dimiternFYI all leftovers in the shared aws account where cleaned up for all regions (jam's instance is unaffected ofc)11:04
dimiternwe should have a script to do that11:05
=== Murali_ is now known as Murali
TheMueperrito666: o/11:08
=== Murali_ is now known as Murali
dooferladdimitern: hangout?11:35
dimiterndooferlad, omw, sorry11:40
dooferladdimitern: no worries!11:40
dimiterndooferlad, i'm in the hangout btw11:42
mupBug #1427204 was filed: systemd service tests map ordering failures <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1427204>13:11
mupBug #1427210 was filed: 'relative path in ExecStart not valid' vivid local deploy failure <ci> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1427210>13:15
mgzI have filed that one as a blocker, not the map ordering test failures though13:16
mgzwill poke eric when he's on about 'em13:16
dimiterndooferlad, ping13:30
dooferladdimitern: hi13:31
dimiterndooferlad, I knew it there will be a ci bug reported for that map ordering thing ^^13:31
dimiterndooferlad, how's that going ?13:31
dooferladdimitern: it is happening...13:32
dimiterndooferlad, did you file a bug? that 1427204 one above should be a duplicate of yours13:33
dooferladdimitern: I did.13:33
mupBug #1427149: Tests require predictable map ordering <pyjuju:New for dooferlad> <https://launchpad.net/bugs/1427149>13:33
dooferladbother, wrong project13:34
mupBug #1427149 was filed: Tests require predictable map ordering <juju-core:New for dooferlad> <https://launchpad.net/bugs/1427149>13:34
dimiterndooferlad, it's the right one I think13:35
dooferladdimitern: it is now.13:35
mupBug #1427204 changed: systemd service tests map ordering failures <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1427204>13:35
dimiterndooferlad, ah, ok13:35
dimiternmgz, dooferlad is already on the map ordering one, so I'll mark the 1427204 as dupe13:36
dooferladdimitern: already have13:36
dimiterndooferlad, yeah, I was just about to say that :)13:36
mgzah, pyjuju, is why I didn't see it13:38
dimiternTheMue, you have a review btw13:56
TheMuedimitern: great, thank you13:56
=== Murali_ is now known as Murali
mgzdooferlad: forgot to check with you, you also get the four failures in service/systemd right? the StubCall one is a bit hard to parse but I assume is also map-related rather than something else14:00
dooferladmgz: yes14:01
dimiternaxw, are you there by any chance?14:03
dimiternwallyworld__, ping14:04
dimiternwallyworld__, so the goamz live tests pass (so far) except for this - http://paste.ubuntu.com/10501880/14:04
dimiternwallyworld__, which looks like the check needs .* before and after14:05
wallyworld__hmmm, ok, i thought it passed before, maybe not14:05
dimiternwallyworld__, but the networking stuff seems unbroken14:07
wallyworld__so do you have any pending changes to commit to goamz?14:07
dimiternwallyworld__, not right now (I have some I'll do later, but not code related)14:07
wallyworld__ok, i'll fix that test14:08
dimiternwallyworld__, cheers14:09
wallyworld__dimitern: i just ran that test with --amazon and it passed for me14:10
wallyworld__maybe it fails when run with other tests14:11
dimiternwallyworld__, "--" instead of "-" ?14:11
wallyworld__it complained tht it wanted ec creds14:11
wallyworld__let me try again14:11
dimiternwallyworld__, it should take a few minutes - if it passes in a few seconds only the local live tests were run14:12
wallyworld__even for one test14:12
wallyworld__maybe gocheck.f messes with the flag14:12
dimiterndepends on the test14:13
dimiternit shouldn't14:13
wallyworld__i ran go test -gocheck.f TestBlockDeviceMappings  -amazon14:13
wallyworld__maybe -amazon needs to be first14:13
wallyworld__still passes14:14
dimiternI run go test -check.v -check.f TestBlockDeviceMappings -amazon and it passed14:14
wallyworld__ok, trying ./...14:15
dimiternso it could be flaky14:15
wallyworld__dimitern: i got 5 vpc related failures but no block ones14:24
wallyworld__so yeah, looks flakey14:25
dimiternwallyworld__, I'll have a look14:29
wallyworld__dimitern: i think though the latest goamz rev is good to use with juju core14:31
dimiternwallyworld__, I agree14:31
wallyworld__dimitern: this should do it - it's what i've tested live juju deployments with http://reviews.vapour.ws/r/1046/14:35
rick_h_dimitern: just heads up https://bugs.launchpad.net/juju-deployer/+bug/1421315 confirms it's between beta 3 and 414:35
mupBug #1421315: subordinate service not appearing in watch output <oil> <juju-core:Triaged> <juju-deployer:Triaged by hazmat> <https://launchpad.net/bugs/1421315>14:35
dimiternrick_h_, good to know - it makes it easier to track, thanks14:37
rick_h_sinzui: can we get ^ marked as a beta regression then and a blocker for release?14:38
sinzuirick_h_, you mean 1.22-beta4 is broken and we need a 1.22-beta514:40
hazmatsinzui: yes14:40
sinzuithank you14:40
rick_h_sinzui: yes please14:40
rick_h_sinzui: and we can help QA and verify that beta5 fixes the issue before release14:40
rick_h_sinzui: vs the current medium status on the bug14:41
hazmatsinzui: any public info i can watch to track the status of deployer in core qa?14:41
sinzuihazmat, no, sorry, but after my meeting, I will be able to report where we are with deployer revision testing14:42
hazmatsinzui: thanks14:42
wallyworld__dimitern: i need sleep, if you are happy with the goamz update to core, can you $$merge$$ it for me?14:49
dimiternwallyworld__, will do, np14:51
dimiternericsnow, hey15:04
dimiternericsnow, can you take care of this bug please? https://bugs.launchpad.net/juju-core/+bug/142721015:04
mupBug #1427210: 'relative path in ExecStart not valid' vivid local deploy failure <ci> <local-provider> <lxc> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1427210>15:04
ericsnowdimitern: yep15:05
ericsnowdimitern: first on my list :)15:05
dimiternericsnow, cheers :)15:05
ericsnowperrito666: standup?15:05
dimiternericsnow, the other one - with the map ordering dooferlad is already fixing and I asked him to check in with you when done15:05
rick_h_jrwren: can you help dimitern https://bugs.launchpad.net/bugs/1421315 with the steps you used to reproduce please?15:07
mupBug #1421315: subordinate service not appearing in watch output <api> <juju-gui> <oil> <regression> <juju-core:Triaged> <juju-core 1.22:Triaged> <juju-deployer:Triaged by hazmat> <https://launchpad.net/bugs/1421315>15:07
rick_h_jrwren: if you have the websocket frames in a pastebin/etc even sweeter15:07
jrwrenrick_h_: I have the websocket frames in a screenshot. I'll share doc.15:18
rick_h_jrwren: ty15:18
dimiternjrwren, rick_h_, thanks for sharing the document, but this still doesn't show the issue15:28
rick_h_jrwren: I'm not seeing the beta4 screenshot15:29
rick_h_dimitern: basically the images highlight how the allwatcher sent the info about the nrpe charm in the watcher output15:30
rick_h_dimitern: and in beta4 that is no longer sent15:30
dimiternrick_h_, sorry, but I'd rather have logs I can search in than a screenshot of half a log15:31
rick_h_dimitern: right, understand. It was the easiest way I could mention jrwren to QA it as I know how to watch the allwatcher from the websocket the gui manages so this is from a browser session of watcher events15:32
dimiternrick_h_, ok, it will be great if those dumps are available somewhere as well15:32
dimiternjrwren, ^^15:33
perrito666ericsnow: I assumed standup was postponed15:33
ericsnowperrito666: k15:34
ericsnowperrito666: ah, I missed Nate's email :)15:35
jrwrenrick_h_: I didn't add beta4 screenshot as it is identical to the others.15:36
jrwrendimitern: Yes, doesn't show the issue. Still trying to repro.15:37
dimiternjrwren, ah, sorry I though you already did15:37
jrwrendimitern: No, I'm guessing this regression is only in master. I've not built master yet, so I cannot confirm.15:38
jrwrendimitern: It is not in any released version that I've tested, and I've tested all current released versions AFAIK15:39
dimiternjrwren, not even in 1.22-beta4? that was proposed for release15:39
jrwrendimitern: this morning i confirmed it is not in 1.22-beta415:39
dimiternjrwren, ok15:40
dimiternrick_h_, ^^15:41
jrwrendimitern: ugh. Typo in my lp comment. I added another comment.15:41
dimiternjrwren, no worries, thanks for clarifying15:41
rick_h_jrwren: oh, important typo lol15:42
rick_h_jrwren: dimitern ok, so we need to check with the original bug author and confirm what juju he's using15:43
rick_h_jrwren: dimitern because I'm doubting he's building trunk?15:44
rick_h_hazmat: did you replicate the subordinate bug and if so on which version of juju? ^15:44
TheMuedimitern: have you done the live testing? I now have an interesting race condition in state/action_test.go:37415:45
hazmatrick_h_: i didn't, i just read the log output of deployer, its deployed a subordinate, service waited 5s, and does a watch, and the sub isn't in the output15:45
rick_h_hazmat: ok, ty.15:46
mupBug #1427257 was filed: Juju backup doesn't contain .juju files <juju-core:New> <https://launchpad.net/bugs/1427257>15:47
rick_h_so might be more a race/timing issue where we didn't replicate that with the gui because we weren't checking the time there.15:47
TheMuedimitern: if I run the state tests directly in my VM they pass, but when doing it via ssh this test above fails15:48
dimiternTheMue, I'm doing it now15:48
dimiternTheMue, what do you mean via ssh?15:52
TheMuedimitern: I've got a VM running my test system in. when I go in directly it passes. but from inside the editor on the host system I can do a "ssh themue@ '~/bin/jdt test state'"15:53
TheMuedimitern: here jdt is the script I told you about15:54
TheMuedimitern: inside the VM I'm simply doing a "jdt test state", so that's not the reason15:54
TheMuedimitern: I think the output via SSH back to the editor slows the tests a bit down and that's why the behavior here is different from doing it directly15:55
dimiternTheMue, could be something ssh-related - try using -v15:55
TheMuedimitern: will do15:56
TheMuedimitern: same result. so would be interesting how testing state passed for you15:59
TheMuedimitern: the latest changes here only have been the comments like in the review15:59
alexisbrick_h_, I am confused by the comments in lp 142131516:00
alexisbit is marked as critical but is not broken in 1.22-beta4?16:01
rick_h_alexisb: heh you and me both. Sorry, our guy said he confirmed it but then found out it was not true16:01
alexisbdimitern, rick_h_ am I reading something wrong?16:01
rick_h_alexisb: so in between we had it run up the flag pole as a breakage in beta416:01
alexisbin the lsat 15 minutes :)16:01
rick_h_alexisb: yep16:01
alexisbit is going to be a fun monday16:01
rick_h_alexisb: so now we're working it out and reevaluating atm16:01
alexisbhazmat, as always thanks for your help16:01
dimiternalexisb, not more than I am I guess :)16:02
alexisbrick_h_, ack, just keep the bug updated and we will stay on it16:02
alexisbbut at this point I am not sure what our next step is given the information :)16:02
rick_h_alexisb: will do, standup atm and will bring it up and update16:02
hazmatrick_h_: yeah.. if it its not reconfirmed, then not sure.. i'm basically booked for the next 36 hrs re trying to reproduce myself, might want to reach out to the oil guys16:03
dimiternTheMue, good news16:05
dimiternTheMue, so far I couldn't manage to reproduce the issue with your fix16:05
TheMuedimitern: aaaaaah16:05
TheMuedimitern: \o/16:05
dimiternTheMue, yep, so far so good, now I'm retrying the same steps without your fix16:09
TheMuedimitern: interested in the results16:09
dooferladdimitern / TheMue: I need some inspiration with how to fix a test. Can either of you jump in a hangout for a while?16:13
perrito666mm, these automated travel services would be so much better if you could specify an arrival date instead of departure16:13
dimiterndooferlad, sure, just give me 2m16:13
TheMuedooferlad: sure16:13
dooferladdimitern, TheMue: Thanks guys.16:14
dooferladdimitern, TheMue: The usual one that we use for the standup?16:14
TheMuedooferlad: would say so16:15
dimiternTheMue, confirmed!16:16
dimiternTheMue, I managed to reproduce the issue on 1.22 without your fix16:16
TheMuedimitern: fantastic16:16
dimiternTheMue, you have LGTM16:37
TheMuedimitern: great, thx, port it to 1.23 then16:37
dimiternTheMue, +116:37
perrito666so natefinch back?17:00
natefinchperrito666: yep17:01
perrito666so ericsnow natefinch wwitzel3  do we staandup or that already happened?17:02
natefinchperrito666: we can do that now if they're available17:02
ericsnownatefinch: sure17:02
* perrito666 took the 2 hs thing literally17:03
natefinchperrito666: haha17:03
natefinchperrito666: I'm rarely that exact :)17:03
mupBug #1427302 was filed: failed to retrieve the template to clone: lxc container 1.21.3 <oil> <juju-core:New> <https://launchpad.net/bugs/1427302>17:21
dooferladdimitern: https://github.com/juju/juju/compare/master...dooferlad:master-map-ordering-tests?expand=117:22
dimiterndooferlad, this looks good to me - go ahead and propose it and ask ericsnow to have a look please17:25
dooferladdimitern: I need to stop for the day in a moment, so I will propose, but if it needs to land today someone else may have to $$prod$$ on github17:26
dimiterndooferlad, sure, that's ok17:27
dooferladdimitern: I am seeing some failures in environs/manual, but I don't know if they are related.17:27
dimiterndooferlad, paste?17:27
dooferladdimitern: http://pastebin.ubuntu.com/10503991/17:28
dimiterndooferlad, no I don't believe these are related17:29
dooferladdimitern, ericsnow: http://reviews.vapour.ws/r/1048/ (should) fix bug #142714917:31
mupBug #1427149: Tests require predictable map ordering <ci> <regression> <test-failure> <juju-core:In Progress by dooferlad> <https://launchpad.net/bugs/1427149>17:31
* ericsnow is looking17:31
dooferladdimitern: I will keep an eye on my email, but assume no fast response until tomorrow. Have a good evening!17:32
dimiterndooferlad, cheers, same to you!17:32
lazyPower!QUESTION: Why does the local.jenv file have multiple entries for the state server "localhost" and "" (by default) - why not just use the address? is this something to work around the snowflakeness of the local provider?17:57
muplazyPower: In-com-pre-hen-si-ble-ness.17:57
lazyPowermup: botsnack17:57
muplazyPower: Roses are red, violets are blue, and I don't understand what you just said.17:57
TheMueWould like a review of http://reviews.vapour.ws/r/1050/. It's the port of fix #1425435 from 1.22 to master.18:08
mupBug #1425435: juju-deployer/jujuclient incompatibility with 1.21.3 <api> <cts> <network> <oil> <openstack> <orange-box> <regression> <uosci> <juju-core:Triaged> <juju-core 1.22:Triaged by themue> <juju-core 1.23:Triaged> <https://launchpad.net/bugs/1425435>18:08
ericsnowdooferlad: done18:08
dimiternlazyPower, 1) it is; 2) because localhost is special in case of ipv4 vs ipv618:09
lazyPoweraahhh ok ty for the explanation18:09
ericsnowdimitern: I have a patch up for lp-1427210: http://reviews.vapour.ws/r/1047/18:09
dimiternericsnow, looking18:09
ericsnowdimitern: thanks18:10
cory_fudimitern: Fair enough about localhost working across IPv4 and IPv6, but couldn't that be handled when the .jenv file is created?  Or is there some other specialness that I'm unaware of?18:12
dimiterncory_fu, I suppose it can18:13
cory_fudimitern: The use-case I'm investigating is attempting to connect to an already bootstrapped local provider from within a container, for review and CI.  I was able to get juju status to work (briefly) by removing the localhost entry, but the .jenv file gets re-written periodically which re-adds the localhost entry18:14
dimiternericsnow, reviewed18:15
ericsnowdimitern: thanks18:15
dimiterncory_fu, that's because the local provider insists on reporting localhost as one of its endpoints18:16
TheMuedimitern: the ported fix is available for review too18:16
dimiterncory_fu, I can't quite recall why, but there was some other good reason - ask thumper18:16
dimiternTheMue, cheers, will have a look18:16
TheMuedimitern: great, thanks18:17
mupBug #1427302 changed: failed to retrieve the template to clone: lxc container 1.21.3 <oil> <juju-core:New> <https://launchpad.net/bugs/1427302>18:18
mupBug #1427302 was filed: failed to retrieve the template to clone: lxc container 1.21.3 <oil> <juju-core:New> <https://launchpad.net/bugs/1427302>18:21
mupBug #1427302 changed: failed to retrieve the template to clone: lxc container 1.21.3 <oil> <juju-core:New> <https://launchpad.net/bugs/1427302>18:29
TheMuedimitern: seen your review, thx already18:36
dimiternTheMue, np :)18:36
mupBug #1427342 was filed: juju package should have strict version dep with juju-core <juju-core:New> <https://launchpad.net/bugs/1427342>18:49
sinzuinatefinch, dimitern, someone landed a change to 1.22 without first landing 1.22-beta5 version. CI knows the version is released19:03
sinzuinatefinch, dimitern I am trying to merge the 1.22-beta5 branch to satisfy CI19:04
natefinchsinzui: are you saying no code should have been landed before the 1.22-beta5 tag was created?19:05
sinzuinatefinch, CI will not test a version of juju that tries to mutate the agents that are released.19:06
sinzuinatefinch, The branch that incremented juju to beta5 hadn't merged, so CI blocked testing of the last merge to 1.2219:07
natefinchsinzui: oh, I see what you mean - we have to change the actual files to create a new release number, as well as creating the tag in git... and we hadn't made the change to the files yet.19:08
sinzuinatefinch, dimitern : I am bringing this up because it isn't clear from the failure email sent to the list why publish-revision failed19:08
sinzuiI am fixing it. nothing for your team o do19:08
natefinchsinzui: ok19:09
sinzuiwe will retest in about 15 minutes19:09
natefinchTheMue: you around?19:16
TheMuenatefinch: yep19:29
natefinchTheMue: how's the train from Munich to Nuremberg?  I'm considering just flying into Munich, since most of my flights go through there anyway19:34
TheMuenatefinch: should be very good, it's near and Nuremberg-Munich are on the ICE route. the ICE is the fastest train in Germany.19:35
TheMuenatefinch: I'll take it too, but from north. ;)19:35
natefinchTheMue: nice.  Do you know if you have to book ahead of time, or can you basically walk up and buy a ticket?19:36
TheMuenatefinch: normally you can buy directly at the railway station. only if you want to make sure getting a good seat you'll have to book ahead of time19:38
natefinchTheMue: cool.19:38
TheMuenatefinch: time is between 2 and 2:30, depending on the exact trains19:40
TheMuenatefinch: sadly Munich Central Station is 40 mins away from the airport19:41
=== kadams54 is now known as kadams54-away
natefinchTheMue: oh, hmm19:42
natefinchTheMue: that's unfortunate19:42
natefinchTheMue: that might make my decision for me, then19:42
TheMuenatefinch: yep19:43
sinzuihazmat, we expect CI to test deployer along with quickstart starting Thursday19:43
TheMuenatefinch: is their a flight from Amsterdam to Nuremberg? or Heathrow? then this may be better.19:44
hazmatsinzui: cool, thanks for the update19:44
natefinchTheMue: looks like most flights want to take me to munich or frankfurt, and then a tiny airplane to nuremberg...   amsterdam or zurich are other possible stops... but they end up being a little longer19:46
natefinchdang, I was happy with the 8 hour direct flight to Munich :)19:47
TheMuenatefinch: yes, I know, puzzling together the optimal connection isn't very easy.19:47
=== anthonyf is now known as Guest30629
=== kadams54-away is now known as kadams54
=== Guest30629 is now known as anthonyjf
alexisbnatefinch, ping20:02
thumperurulama: are you still around?20:09
urulamathumper: hey. just about to have dinner. will ping you when i'm done :)20:13
=== urulama is now known as urulama|afk
davecheneyi forgot to ask20:25
davecheneyat the standup20:25
davecheneywhat is next with power ?20:25
=== kadams54 is now known as kadams54-away
thumperdavecheney: I need to talk with alexisb about that in my call this morning20:29
davecheneyi have the fix as a replacement .deb we can deploy on ppc64 ci machines to get them going20:30
=== urulama|afk is now known as urulama
urulamathumper: back20:35
thumperurulama: that was quick20:35
thumperurulama: I'm free for the next 20 minutes20:35
ericsnowmgz: how do I kick off a run of "local-deploy-vivid-amd64"?20:50
mgzericsnow: you mean for a specific branch? or just rerun the last job?20:55
ericsnowmgz: trying to verify 1427210 is fixed (so job 144)20:56
mgzericsnow: it seems to be reliably (twince in the same way) failing with a new error20:59
ericsnowmgz: k20:59
=== kadams54-away is now known as kadams54
mgzconf.Output value "/var/log/juju-jenkins-localdeploy-vivid-amd64/machine-0.log" (Options are syslog) is not valid21:00
ericsnowmgz: how do I look at the logs?21:00
mgzericsnow: it's not yet up on juju-reports so I'm just looking at the job in jenkins, which requires admin/password which can be found is cloud-city21:01
ericsnowmgz: k21:01
* urulama makes a note to self ... don't talk to thumper :P21:02
thumperurulama: oh, c'mon21:02
thumperit wasn't that bad21:02
urulamayou were laughing a lot, yes :D21:03
perrito666urulama: really? you need a note? I got it in my induction manual21:03
urulamaperrito666: :D21:03
rick_h_urulama: don't take that from thumper!21:04
rick_h_urulama: just bring up UX issues until he calls off the phone call21:04
urulamathumper: fyi, you have +1++ on JES CLI21:08
alexisbthumper, ping21:32
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
ericsnowcould someone take a look at a small patch: http://reviews.vapour.ws/r/1051/22:29
ericsnowit should unblock CI22:29
menn0ericsnow: looking22:31
alexisbwallyworld__, ping22:32
menn0ericsnow: i'm probably just missing context but why is a command simple when it contains one of the those characters?22:34
ericsnowmenn0: yeah, the condition is reversed (so all those are *not* simple) :)22:35
ericsnowmenn0: I'll fix that22:35
menn0ericsnow: right, that makes more sense then!22:35
menn0ericsnow: while you're in there, consider using strings.ContainsAny()22:37
menn0ericsnow: that would simplify the function somewhat (and make it more efficient)22:37
ericsnowmenn0: sounds good22:37
menn0ericsnow: initial review done22:40
ericsnowmenn0: thanks22:45
ericsnowmenn0: I've updated the patch22:45
mupBug #1403084 changed: Tests that need to be fixed on windows <ci> <tech-debt> <testing> <windows> <juju-core:Fix Released> <https://launchpad.net/bugs/1403084>22:46
sinzuiericsnow, do you want to claim this bug as in progress or fix committed https://bugs.launchpad.net/juju-core/+bug/140963922:48
mupBug #1409639: juju needs to support systemd for >= vivid <systemd-boot> <juju-core:Triaged> <juju-core (Ubuntu):Triaged> <juju-core (Ubuntu Vivid):Triaged> <https://launchpad.net/bugs/1409639>22:48
ericsnowsinzui: good point22:48
menn0ericsnow: re the comment about the error check TODO. where I commented there's no UpdateConfig call. Looks like a copy and paste problem? That TODO appears twice in the PR.22:49
ericsnowsinzui: I'll updated it22:49
ericsnowmenn0: ah, you're right22:49
menn0ericsnow: sorry, a couple more little things22:54
ericsnowmenn0: no worries22:55
=== kadams54 is now known as kadams54-away
ericsnowmenn0: fixed22:57
menn0ericsnow: ship it22:59
ericsnowmenn0: thanks22:59
ericsnowabentley: are you looking at local-deploy-vivid-amd64?23:44

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