[00:00] <cherylj> davecheney: thanks!
[00:27] <waigani> thumper: do you also not want the username quoted in the error returned by the apiserver?
[00:28] <thumper> I think quoted is fine from the api server as it is developer facing
[00:29] <waigani> thumper: yep, wrote too quickly - I see we use %q in the rest of the errors in that package
[04:36] <thumper> wine time
[04:41] <waigani> wallyworld: thanks for the review. I've responded to your comments, but can't seem to update my diff.
[04:41] <wallyworld> waigani: i saw the replies, so marked at +1
[04:42] <waigani> wallyworld: okay thanks
[04:42] <wallyworld> np
[06:43] <wallyworld> dimitern: heya
[06:43] <dimitern> wallyworld, morning
[06:43] <wallyworld> god weekend? i hope you gots sleep :-)
[06:43] <wallyworld> good
[06:44] <dimitern> wallyworld, :) ~18h in total
[06:44] <wallyworld> wow
[06:45] <wallyworld> i 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/33
[06:46] <wallyworld> i'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 test
[06:47] <dimitern> wallyworld, yeah - I was just looking at your two PRs in amz.v3 after v3-unstable was promoted to v3
[06:48] <wallyworld> i've pull her juju-core branch to test juju live katco-:goamz-v3-support
[06:49] <dimitern> wallyworld, I thought I *did* compare v2 to v3 to see if something was missing but apparently I missed something
[06:55] <wallyworld> dimitern: stupid irc dropped out, not sure if i missed any reply
[06:56] <dimitern> wallyworld, I was looking at https://github.com/go-amz/amz/compare/v1...v2 and https://github.com/go-amz/amz/compare/v2...v3
[06:56] <wallyworld> yeah, the v2..v3 diff what what i based the pr on
[06:57] <dimitern> wallyworld, but I can't see the changes in the PR to be missing from v3?
[06:58] <wallyworld> hmm, maybe i had an out of date local copy
[06:58] <wallyworld> let me check
[06:58] <dimitern> wallyworld, that's might be - esp. if you're using symlinks in your gopath
[06:59] <wallyworld> hmm, i just git pulled in my v3 master and no updates
[06:59] <wallyworld> i'll look around a bit
[07:01] <wallyworld> dimitern: so as an example, in https://github.com/go-amz/amz/tree/v3/ec2 there's no blockdevicemappings_test.go
[07:01] <wallyworld> that file should be there and is in v2
[07:02] <dimitern> wallyworld, thats true, but why it doesn't show up on the v2..v3 diff?
[07:02] <dimitern> weird
[07:03] <wallyworld> yeah, and there's a bunch of network stuff missing too
[07:03] <dimitern> wallyworld, ok, I'll do the diff locally to be sure
[07:03] <wallyworld> ok
[07:03] <dimitern> wallyworld, apparently github compare lies
[07:04] <wallyworld> there must be a logical reason you'd think
[07:07]  * dimitern keeps digging 
[07:18] <dimitern> wallyworld, for some reason even though v3 was branched off v2 some commits in v2 are missing
[07:18] <wallyworld> dimitern: 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 limits
[07:18] <wallyworld> hmm
[07:19] <dimitern> wallyworld, can connect to the ec2 web ui with the shared creds or you just have the api keys?
[07:19] <wallyworld> i never use the web ui, just ElasticFox
[07:20] <wallyworld> i have the api keys also for juju
[07:20] <dimitern> wallyworld, you can clean up the stale vpc from there
[07:21] <dimitern> wallyworld, 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] <wallyworld> ok, i'll see if i have it
[07:23] <dimitern> wallyworld, in the PR #33 there are still some things missing from v2 btw
[07:23] <wallyworld> ah, ok
[07:24] <dimitern> wallyworld, but not much, so if you go ahead and merge that, I'll propose a follow-up to add the missing
[07:27] <wallyworld> dimitern: 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 fox
[07:28] <wallyworld> dimitern: ok, that's merged
[07:28] <dimitern> wallyworld, ok, I'll ask jam if he has them
[07:28] <dimitern> wallyworld, thanks!
[07:28] <wallyworld> dimitern: once your stuff lands, i'll update a fork of kath's branch i have and land that in core
[07:29] <dimitern> wallyworld, ok, will let you know
[07:29] <wallyworld> ok, i might duck off to have dinner
[08:27] <Muntaner> good morning devs o/
[08:27] <Muntaner> I'm writing my first charm and having some problems, can anybody help me?
[08:33] <dimitern> Muntaner, morning! try asking in #juju
[08:33] <dimitern> for all your charming needs :)
[08:33] <Muntaner> dimitern, ty ;)
[08:33] <TheMue> morning
[08:37] <dooferlad> dimitern, TheMue: morning
[08:38] <dimitern> TheMue, dooferlad, morning folks!
[08:38] <TheMue> dooferlad: dimitern: o/
[08:38] <dooferlad> dimitern: heard anything from voidspace?
[08:39] <dimitern> dooferlad, he become a dad over the weekend
[08:39] <dimitern> :)
[08:40] <dooferlad> dimitern: awesome!
[08:40] <TheMue> aaah, fantastic news
[08:40] <dimitern> so I guess he won't be here today
[08:40] <dimitern> yeah indeed :)
[08:40] <dooferlad> indeed
[08:40] <dimitern> I've seen pics on FB
[08:41] <TheMue> oh, dedn't know he's on FB, so far only G+. while have a look
[08:43] <TheMue> found and added him ;)
[08:54] <jam> dimitern: sorry I misesd you earlier, just missed the schedule. what's up with ec2?
[08:55] <jam> wallyworld: maybe you know?
[08:55] <dimitern> jam, minor mishap with some missing commits from amz.v2 into amz.v3, but wallyworld sorted that out
[08:55] <jam> dimitern: k, I thought there was something you needed w VPC
[08:55] <dimitern> jam, I'm now manually comparing amz.v2 to the updated amz.v3 to make sure all is good, then I'll do a live test
[08:56] <jam> dimitern: I do see a spare network interface in us-east-1
[09:00] <dimitern> TheMue, sorry, I'll be 10m late for our 1:1
[09:01] <TheMue> dimitern: ok
[09:06] <dimitern> wallyworld, jam, I'm happy to report after that PR #33 landed amz.v3 has everything is needs wrt storage and networking
[09:06] <dimitern> I'll still need to do a live test later though
[09:12] <dimitern> TheMue, I'm in the hangout
[09:12] <TheMue> dimitern: coming
[09:38] <dimitern> axw, katco, jam, wallyworld, is anyone using the shared aws account for testing now?
[09:38] <dimitern> I'm thinking of cleaning up the stale VPCs, subnets, security groups, etc.
[09:39] <dimitern> unless anyone responds in the next half hour, I'll go ahead and do it
[09:48] <perrito666> dimitern: for me go for it
[09:49] <dimitern> perrito666, +1
[10:11] <jam> dimitern: I'm using eu-west-1 for a live service
[10:11] <jam> (my IRC proxy)
[10:11] <jam> but nothing in US-east-1
[10:11] <dimitern> jam, ok
[10:41] <wallyworld> dimitern: sorry, had to go down to soccer at short notice
[10:42] <dimitern> wallyworld, np. s'all good :)
[10:42] <wallyworld> dimitern: once you're happy with goaws, I'll land a branch to update core
[10:43] <dimitern> wallyworld, I still need to do a live test, so I'll let you know; but looking at the code it should work
[10:43] <wallyworld> ok, sounds good
[10:43] <wallyworld> i did a storage live test and it was good too
[10:44] <dimitern> wallyworld, cool!
[10:59] <perrito666> morning
[11:04] <dimitern> FYI all leftovers in the shared aws account where cleaned up for all regions (jam's instance is unaffected ofc)
[11:05] <dimitern> we should have a script to do that
[11:08] <TheMue> perrito666: o/
[11:35] <dooferlad> dimitern: hangout?
[11:40] <dimitern> dooferlad, omw, sorry
[11:40] <dooferlad> dimitern: no worries!
[11:42] <dimitern> dooferlad, i'm in the hangout btw
[13:11] <mup> Bug #1427204 was filed: systemd service tests map ordering failures <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1427204>
[13:15] <mup> Bug #1427210 was filed: 'relative path in ExecStart not valid' vivid local deploy failure <ci> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1427210>
[13:16] <mgz> I have filed that one as a blocker, not the map ordering test failures though
[13:16] <mgz> will poke eric when he's on about 'em
[13:30] <dimitern> dooferlad, ping
[13:31] <dooferlad> dimitern: hi
[13:31] <dimitern> dooferlad, I knew it there will be a ci bug reported for that map ordering thing ^^
[13:31] <dimitern> dooferlad, how's that going ?
[13:32] <dooferlad> dimitern: it is happening...
[13:33] <dimitern> dooferlad, did you file a bug? that 1427204 one above should be a duplicate of yours
[13:33] <dooferlad> dimitern: I did.
[13:33] <dooferlad> https://bugs.launchpad.net/juju/+bug/1427149
[13:33] <mup> Bug #1427149: Tests require predictable map ordering <pyjuju:New for dooferlad> <https://launchpad.net/bugs/1427149>
[13:34] <dooferlad> bother, wrong project
[13:34] <mup> Bug #1427149 was filed: Tests require predictable map ordering <juju-core:New for dooferlad> <https://launchpad.net/bugs/1427149>
[13:35] <dimitern> dooferlad, it's the right one I think
[13:35] <dooferlad> dimitern: it is now.
[13:35] <mup> Bug #1427204 changed: systemd service tests map ordering failures <ci> <regression> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1427204>
[13:35] <dimitern> dooferlad, ah, ok
[13:36] <dimitern> mgz, dooferlad is already on the map ordering one, so I'll mark the 1427204 as dupe
[13:36] <dooferlad> dimitern: already have
[13:36] <dimitern> dooferlad, yeah, I was just about to say that :)
[13:38] <mgz> ah, pyjuju, is why I didn't see it
[13:56] <dimitern> TheMue, you have a review btw
[13:56] <TheMue> dimitern: great, thank you
[14:00] <mgz> dooferlad: 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 else
[14:01] <dooferlad> mgz: yes
[14:03] <dimitern> axw, are you there by any chance?
[14:04] <dimitern> wallyworld__, ping
[14:04] <wallyworld__> yo
[14:04] <dimitern> wallyworld__, so the goamz live tests pass (so far) except for this - http://paste.ubuntu.com/10501880/
[14:05] <dimitern> wallyworld__, which looks like the check needs .* before and after
[14:05] <wallyworld__> hmmm, ok, i thought it passed before, maybe not
[14:07] <dimitern> wallyworld__, but the networking stuff seems unbroken
[14:07] <wallyworld__> so do you have any pending changes to commit to goamz?
[14:07] <dimitern> wallyworld__, not right now (I have some I'll do later, but not code related)
[14:08] <wallyworld__> ok, i'll fix that test
[14:09] <dimitern> wallyworld__, cheers
[14:10] <wallyworld__> dimitern: i just ran that test with --amazon and it passed for me
[14:11] <wallyworld__> maybe it fails when run with other tests
[14:11] <dimitern> wallyworld__, "--" instead of "-" ?
[14:11] <wallyworld__> it complained tht it wanted ec creds
[14:11] <wallyworld__> let me try again
[14:12] <dimitern> wallyworld__, it should take a few minutes - if it passes in a few seconds only the local live tests were run
[14:12] <wallyworld__> even for one test
[14:12] <wallyworld__> maybe gocheck.f messes with the flag
[14:13] <dimitern> depends on the test
[14:13] <dimitern> it shouldn't
[14:13] <wallyworld__> i ran go test -gocheck.f TestBlockDeviceMappings  -amazon
[14:13] <wallyworld__> maybe -amazon needs to be first
[14:14] <wallyworld__> still passes
[14:14] <dimitern> I run go test -check.v -check.f TestBlockDeviceMappings -amazon and it passed
[14:15] <wallyworld__> ok, trying ./...
[14:15] <dimitern> so it could be flaky
[14:24] <wallyworld__> dimitern: i got 5 vpc related failures but no block ones
[14:25] <wallyworld__> so yeah, looks flakey
[14:29] <dimitern> wallyworld__, I'll have a look
[14:31] <wallyworld__> dimitern: i think though the latest goamz rev is good to use with juju core
[14:31] <dimitern> wallyworld__, I agree
[14:35] <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 4
[14:35] <mup> Bug #1421315: subordinate service not appearing in watch output <oil> <juju-core:Triaged> <juju-deployer:Triaged by hazmat> <https://launchpad.net/bugs/1421315>
[14:37] <dimitern> rick_h_, good to know - it makes it easier to track, thanks
[14:38] <rick_h_> sinzui: can we get ^ marked as a beta regression then and a blocker for release?
[14:40] <sinzui> rick_h_, you mean 1.22-beta4 is broken and we need a 1.22-beta5
[14:40] <hazmat> sinzui: yes
[14:40] <sinzui> thank you
[14:40] <rick_h_> sinzui: yes please
[14:40] <rick_h_> sinzui: and we can help QA and verify that beta5 fixes the issue before release
[14:41] <rick_h_> sinzui: vs the current medium status on the bug
[14:41] <hazmat> sinzui: any public info i can watch to track the status of deployer in core qa?
[14:42] <sinzui> hazmat, no, sorry, but after my meeting, I will be able to report where we are with deployer revision testing
[14:42] <hazmat> sinzui: thanks
[14:49] <wallyworld__> dimitern: i need sleep, if you are happy with the goamz update to core, can you $$merge$$ it for me?
[14:51] <dimitern> wallyworld__, will do, np
[14:51] <wallyworld__> ty
[15:04] <dimitern> ericsnow, hey
[15:04] <dimitern> ericsnow, can you take care of this bug please? https://bugs.launchpad.net/juju-core/+bug/1427210
[15:04] <mup> Bug #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:05] <ericsnow> dimitern: yep
[15:05] <ericsnow> dimitern: first on my list :)
[15:05] <dimitern> ericsnow, cheers :)
[15:05] <ericsnow> perrito666: standup?
[15:05] <dimitern> ericsnow, the other one - with the map ordering dooferlad is already fixing and I asked him to check in with you when done
[15:07] <rick_h_> jrwren: can you help dimitern https://bugs.launchpad.net/bugs/1421315 with the steps you used to reproduce please?
[15:07] <mup> Bug #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 sweeter
[15:18] <jrwren> rick_h_: I have the websocket frames in a screenshot. I'll share doc.
[15:18] <rick_h_> jrwren: ty
[15:28] <dimitern> jrwren, rick_h_, thanks for sharing the document, but this still doesn't show the issue
[15:29] <rick_h_> jrwren: I'm not seeing the beta4 screenshot
[15:30] <rick_h_> dimitern: basically the images highlight how the allwatcher sent the info about the nrpe charm in the watcher output
[15:30] <rick_h_> dimitern: and in beta4 that is no longer sent
[15:31] <dimitern> rick_h_, sorry, but I'd rather have logs I can search in than a screenshot of half a log
[15:32] <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 events
[15:32] <dimitern> rick_h_, ok, it will be great if those dumps are available somewhere as well
[15:33] <dimitern> jrwren, ^^
[15:33] <perrito666> ericsnow: I assumed standup was postponed
[15:34] <ericsnow> perrito666: k
[15:35] <ericsnow> perrito666: ah, I missed Nate's email :)
[15:36] <jrwren> rick_h_: I didn't add beta4 screenshot as it is identical to the others.
[15:37] <jrwren> dimitern: Yes, doesn't show the issue. Still trying to repro.
[15:37] <dimitern> jrwren, ah, sorry I though you already did
[15:38] <jrwren> dimitern: No, I'm guessing this regression is only in master. I've not built master yet, so I cannot confirm.
[15:39] <jrwren> dimitern: It is not in any released version that I've tested, and I've tested all current released versions AFAIK
[15:39] <dimitern> jrwren, not even in 1.22-beta4? that was proposed for release
[15:39] <jrwren> dimitern: this morning i confirmed it is not in 1.22-beta4
[15:40] <dimitern> jrwren, ok
[15:41] <dimitern> rick_h_, ^^
[15:41] <jrwren> dimitern: ugh. Typo in my lp comment. I added another comment.
[15:41] <dimitern> jrwren, no worries, thanks for clarifying
[15:42] <rick_h_> jrwren: oh, important typo lol
[15:43] <rick_h_> jrwren: dimitern ok, so we need to check with the original bug author and confirm what juju he's using
[15:44] <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:45] <TheMue> dimitern: have you done the live testing? I now have an interesting race condition in state/action_test.go:374
[15:45] <hazmat> rick_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 output
[15:46] <rick_h_> hazmat: ok, ty.
[15:47] <mup> Bug #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:48] <TheMue> dimitern: if I run the state tests directly in my VM they pass, but when doing it via ssh this test above fails
[15:48] <dimitern> TheMue, I'm doing it now
[15:52] <dimitern> TheMue, what do you mean via ssh?
[15:53] <TheMue> dimitern: 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@192.168.2.210 '~/bin/jdt test state'"
[15:54] <TheMue> dimitern: here jdt is the script I told you about
[15:54] <TheMue> dimitern: inside the VM I'm simply doing a "jdt test state", so that's not the reason
[15:55] <TheMue> dimitern: 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 directly
[15:55] <dimitern> TheMue, could be something ssh-related - try using -v
[15:56] <TheMue> dimitern: will do
[15:59] <TheMue> dimitern: same result. so would be interesting how testing state passed for you
[15:59] <TheMue> dimitern: the latest changes here only have been the comments like in the review
[16:00] <alexisb> rick_h_, I am confused by the comments in lp 1421315
[16:01] <alexisb> it 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 true
[16:01] <alexisb> dimitern, 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 beta4
[16:01] <alexisb> in the lsat 15 minutes :)
[16:01] <rick_h_> alexisb: yep
[16:01] <alexisb> it is going to be a fun monday
[16:01] <rick_h_> alexisb: so now we're working it out and reevaluating atm
[16:01] <alexisb> hazmat, as always thanks for your help
[16:02] <dimitern> alexisb, not more than I am I guess :)
[16:02] <alexisb> rick_h_, ack, just keep the bug updated and we will stay on it
[16:02] <alexisb> but 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 update
[16:02] <alexisb> thnx
[16:03] <hazmat> rick_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 guys
[16:05] <dimitern> TheMue, good news
[16:05] <dimitern> TheMue, so far I couldn't manage to reproduce the issue with your fix
[16:05] <TheMue> dimitern: aaaaaah
[16:05] <TheMue> dimitern: \o/
[16:09] <dimitern> TheMue, yep, so far so good, now I'm retrying the same steps without your fix
[16:09] <TheMue> dimitern: interested in the results
[16:13] <dooferlad> dimitern / TheMue: I need some inspiration with how to fix a test. Can either of you jump in a hangout for a while?
[16:13] <perrito666> mm, these automated travel services would be so much better if you could specify an arrival date instead of departure
[16:13] <dimitern> dooferlad, sure, just give me 2m
[16:13] <TheMue> dooferlad: sure
[16:14] <dooferlad> dimitern, TheMue: Thanks guys.
[16:14] <dooferlad> dimitern, TheMue: The usual one that we use for the standup?
[16:15] <TheMue> dooferlad: would say so
[16:16] <dimitern> TheMue, confirmed!
[16:16] <dimitern> TheMue, I managed to reproduce the issue on 1.22 without your fix
[16:16] <TheMue> dimitern: fantastic
[16:37] <dimitern> TheMue, you have LGTM
[16:37] <TheMue> dimitern: great, thx, port it to 1.23 then
[16:37] <dimitern> TheMue, +1
[17:00] <perrito666> so natefinch back?
[17:01] <natefinch> perrito666: yep
[17:02] <perrito666> so ericsnow natefinch wwitzel3  do we staandup or that already happened?
[17:02] <natefinch> perrito666: we can do that now if they're available
[17:02] <ericsnow> natefinch: sure
[17:03]  * perrito666 took the 2 hs thing literally
[17:03] <natefinch> perrito666: haha
[17:03] <natefinch> perrito666: I'm rarely that exact :)
[17:21] <mup> Bug #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:22] <dooferlad> dimitern: https://github.com/juju/juju/compare/master...dooferlad:master-map-ordering-tests?expand=1
[17:25] <dimitern> dooferlad, this looks good to me - go ahead and propose it and ask ericsnow to have a look please
[17:26] <dooferlad> dimitern: 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 github
[17:27] <dimitern> dooferlad, sure, that's ok
[17:27] <dooferlad> dimitern: I am seeing some failures in environs/manual, but I don't know if they are related.
[17:27] <dimitern> dooferlad, paste?
[17:28] <dooferlad> dimitern: http://pastebin.ubuntu.com/10503991/
[17:29] <dimitern> dooferlad, no I don't believe these are related
[17:31] <dooferlad> dimitern, ericsnow: http://reviews.vapour.ws/r/1048/ (should) fix bug #1427149
[17:31] <mup> Bug #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 looking
[17:32] <dooferlad> dimitern: I will keep an eye on my email, but assume no fast response until tomorrow. Have a good evening!
[17:32] <dimitern> dooferlad, cheers, same to you!
[17:57] <lazyPower> !QUESTION: Why does the local.jenv file have multiple entries for the state server "localhost" and "10.0.3.1" (by default) - why not just use the 10.0.3.1 address? is this something to work around the snowflakeness of the local provider?
[17:57] <mup> lazyPower: In-com-pre-hen-si-ble-ness.
[17:57] <lazyPower> mup: botsnack
[17:57] <mup> lazyPower: Roses are red, violets are blue, and I don't understand what you just said.
[18:08] <TheMue> Would like a review of http://reviews.vapour.ws/r/1050/. It's the port of fix #1425435 from 1.22 to master.
[18:08] <mup> Bug #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] <ericsnow> dooferlad: done
[18:09] <dimitern> lazyPower, 1) it is; 2) because localhost is special in case of ipv4 vs ipv6
[18:09] <lazyPower> aahhh ok ty for the explanation
[18:09] <dimitern> :)
[18:09] <ericsnow> dimitern: I have a patch up for lp-1427210: http://reviews.vapour.ws/r/1047/
[18:09] <dimitern> ericsnow, looking
[18:10] <ericsnow> dimitern: thanks
[18:12] <cory_fu> dimitern: 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:13] <dimitern> cory_fu, I suppose it can
[18:14] <cory_fu> dimitern: 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 entry
[18:15] <dimitern> ericsnow, reviewed
[18:15] <ericsnow> dimitern: thanks
[18:16] <dimitern> cory_fu, that's because the local provider insists on reporting localhost as one of its endpoints
[18:16] <TheMue> dimitern: the ported fix is available for review too
[18:16] <dimitern> cory_fu, I can't quite recall why, but there was some other good reason - ask thumper
[18:16] <dimitern> TheMue, cheers, will have a look
[18:17] <TheMue> dimitern: great, thanks
[18:18] <mup> Bug #1427302 changed: failed to retrieve the template to clone: lxc container 1.21.3 <oil> <juju-core:New> <https://launchpad.net/bugs/1427302>
[18:21] <mup> Bug #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:29] <mup> Bug #1427302 changed: failed to retrieve the template to clone: lxc container 1.21.3 <oil> <juju-core:New> <https://launchpad.net/bugs/1427302>
[18:36] <TheMue> dimitern: seen your review, thx already
[18:36] <dimitern> TheMue, np :)
[18:49] <mup> Bug #1427342 was filed: juju package should have strict version dep with juju-core <juju-core:New> <https://launchpad.net/bugs/1427342>
[19:03] <sinzui> natefinch, dimitern, someone landed a change to 1.22 without first landing 1.22-beta5 version. CI knows the version is released
[19:04] <sinzui> natefinch, dimitern I am trying to merge the 1.22-beta5 branch to satisfy CI
[19:05] <natefinch> sinzui: are you saying no code should have been landed before the 1.22-beta5 tag was created?
[19:06] <sinzui> natefinch, CI will not test a version of juju that tries to mutate the agents that are released.
[19:07] <sinzui> natefinch, The branch that incremented juju to beta5 hadn't merged, so CI blocked testing of the last merge to 1.22
[19:08] <natefinch> sinzui: 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] <sinzui> natefinch, dimitern : I am bringing this up because it isn't clear from the failure email sent to the list why publish-revision failed
[19:08] <sinzui> I am fixing it. nothing for your team o do
[19:09] <natefinch> sinzui: ok
[19:09] <sinzui> we will retest in about 15 minutes
[19:16] <natefinch> TheMue: you around?
[19:29] <TheMue> natefinch: yep
[19:34] <natefinch> TheMue: how's the train from Munich to Nuremberg?  I'm considering just flying into Munich, since most of my flights go through there anyway
[19:35] <TheMue> natefinch: 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] <TheMue> natefinch: I'll take it too, but from north. ;)
[19:36] <natefinch> TheMue: nice.  Do you know if you have to book ahead of time, or can you basically walk up and buy a ticket?
[19:38] <TheMue> natefinch: 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 time
[19:38] <natefinch> TheMue: cool.
[19:40] <TheMue> natefinch: time is between 2 and 2:30, depending on the exact trains
[19:41] <TheMue> natefinch: sadly Munich Central Station is 40 mins away from the airport
[19:42] <natefinch> TheMue: oh, hmm
[19:42] <natefinch> TheMue: that's unfortunate
[19:42] <natefinch> TheMue: that might make my decision for me, then
[19:43] <TheMue> natefinch: yep
[19:43] <sinzui> hazmat, we expect CI to test deployer along with quickstart starting Thursday
[19:44] <TheMue> natefinch: is their a flight from Amsterdam to Nuremberg? or Heathrow? then this may be better.
[19:44] <hazmat> sinzui: cool, thanks for the update
[19:46] <natefinch> TheMue: 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 longer
[19:47] <natefinch> dang, I was happy with the 8 hour direct flight to Munich :)
[19:47] <TheMue> natefinch: yes, I know, puzzling together the optimal connection isn't very easy.
[20:02] <alexisb> natefinch, ping
[20:09] <thumper> urulama: are you still around?
[20:13] <urulama> thumper: hey. just about to have dinner. will ping you when i'm done :)
[20:14] <thumper> ok
[20:25] <davecheney> thumper:
[20:25] <davecheney> i forgot to ask
[20:25] <davecheney> at the standup
[20:25] <davecheney> what is next with power ?
[20:29] <thumper> davecheney: I need to talk with alexisb about that in my call this morning
[20:30] <davecheney> ok
[20:30] <davecheney> i have the fix as a replacement .deb we can deploy on ppc64 ci machines to get them going
[20:35] <urulama> thumper: back
[20:35] <thumper> urulama: that was quick
[20:35] <thumper> urulama: I'm free for the next 20 minutes
[20:50] <ericsnow> mgz: how do I kick off a run of "local-deploy-vivid-amd64"?
[20:55] <mgz> ericsnow: you mean for a specific branch? or just rerun the last job?
[20:56] <ericsnow> mgz: trying to verify 1427210 is fixed (so job 144)
[20:59] <mgz> ericsnow: it seems to be reliably (twince in the same way) failing with a new error
[20:59] <ericsnow> mgz: k
[21:00] <mgz> conf.Output value "/var/log/juju-jenkins-localdeploy-vivid-amd64/machine-0.log" (Options are syslog) is not valid
[21:00] <ericsnow> mgz: how do I look at the logs?
[21:01] <mgz> ericsnow: 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-city
[21:01] <ericsnow> mgz: k
[21:02]  * urulama makes a note to self ... don't talk to thumper :P
[21:02] <thumper> urulama: oh, c'mon
[21:02] <thumper> it wasn't that bad
[21:03] <urulama> you were laughing a lot, yes :D
[21:03] <perrito666> urulama: really? you need a note? I got it in my induction manual
[21:03] <urulama> perrito666: :D
[21:04] <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 call
[21:08] <urulama> thumper: fyi, you have +1++ on JES CLI
[21:09] <thumper> awesome
[21:09] <rick_h_> lol
[21:32] <alexisb> thumper, ping
[21:32] <thumper> hey
[21:32] <thumper> coming
[22:29] <ericsnow> could someone take a look at a small patch: http://reviews.vapour.ws/r/1051/
[22:29] <ericsnow> it should unblock CI
[22:31] <menn0> ericsnow: looking
[22:32] <alexisb> wallyworld__, ping
[22:34] <menn0> ericsnow: i'm probably just missing context but why is a command simple when it contains one of the those characters?
[22:35] <ericsnow> menn0: yeah, the condition is reversed (so all those are *not* simple) :)
[22:35] <ericsnow> menn0: I'll fix that
[22:35] <menn0> ericsnow: right, that makes more sense then!
[22:37] <menn0> ericsnow: while you're in there, consider using strings.ContainsAny()
[22:37] <menn0> ericsnow: that would simplify the function somewhat (and make it more efficient)
[22:37] <ericsnow> menn0: sounds good
[22:40] <menn0> ericsnow: initial review done
[22:45] <ericsnow> menn0: thanks
[22:45] <ericsnow> menn0: I've updated the patch
[22:46] <mup> Bug #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:48] <sinzui> ericsnow, do you want to claim this bug as in progress or fix committed https://bugs.launchpad.net/juju-core/+bug/1409639
[22:48] <mup> Bug #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] <ericsnow> sinzui: good point
[22:49] <menn0> ericsnow: 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] <ericsnow> sinzui: I'll updated it
[22:49] <ericsnow> menn0: ah, you're right
[22:54] <menn0> ericsnow: sorry, a couple more little things
[22:55] <ericsnow> menn0: no worries
[22:57] <ericsnow> menn0: fixed
[22:59] <menn0> ericsnow: ship it
[22:59] <ericsnow> menn0: thanks
[23:44] <ericsnow> abentley: are you looking at local-deploy-vivid-amd64?