[00:44] lucky(~/src/github.com/juju/juju) % gb test [00:44] FATAL command "test" failed: failed to resolve import path "github.com/juju/juju/api": cannot find package "golang.org/x/net/http2/hpack" in any of: [00:44] ^ who added a dependency on the new http2 stuff ? [00:48] axw: yes [00:48] I believe so [00:48] * thumper shrugs [00:49] davechen1y: the shrug was for the http2 stuff [00:50] davechen1y: "go list" shows no dependency on http2 [00:50] perhaps just a test dep? [00:51] could be a test dep [00:51] still digging [00:57] ok [00:57] ignore this [00:58] short version: it's a go 1.6 thing [00:58] ignore it [01:05] :) [01:08] Bug #1510333 opened: worker/uniter: converge on a single approach for updating goal state [01:14] Bug #1510333 changed: worker/uniter: converge on a single approach for updating goal state [01:17] Bug #1510333 opened: worker/uniter: converge on a single approach for updating goal state [01:29] http://reviews.vapour.ws/r/3000/ [01:29] anyone ? [01:31] davechen1y: this is from where? [01:31] was it juju/juju/ssh? [01:31] I was going to suggest we just have juju/ssh rather than juju/utils/ssh [01:31] but then I saw the other deps on the utils package [01:31] and thought "meh" [01:33] thumper: the only thing worse than a utils packge is a utils repo [01:33] thumper: and the only thing worse than a utils repo is having several [01:33] one evil at a time [01:33] :) [01:33] k [01:36] axw: if you are happy with https://github.com/juju/retry/pull/1 I'll merge it :) [01:36] thumper: sorry, I keep getting distracted [01:36] axw: I was hoping fwereade would have looked, but I'm prepared to land it now [01:36] thumper: lemme take another quick look [01:36] cheers [01:39] thumper: I have added github.com/juju/retry. We wont know it works until there is a branch to merge. Since there isn't a branch there now, I don't know which packages deps it imports. [01:39] sinzui: https://github.com/juju/retry/pull/1 [01:40] thank youn thumper . I will quickly add the deps I see [01:40] cheers [01:42] thumper: reviewed [01:43] axw: ta [01:51] sinzui: I'll try merging now [01:51] sinzui: is it ready? [01:51] thumper: yep, I am watching to procs now [01:52] sinzui: who handles which repos go to reviewboard? [01:54] thumper: I don't know the config. I am sure ericsnow knows. [01:55] \o/ landed [01:55] thumper: I see real go test was really run too [01:55] as opposed to what? [01:56] thumper: the merge job just sending a success without actually merging the branch and running the tests [01:56] :) [01:57] I must admit, I do find it pleasing to see more tests than code :) [01:57] :)) [02:53] logger.Debugf("keeping unrecognised existing ssh key %q: %v", key, err) [02:53] ERRORS LOGGED AT DEBUGGG! [02:54] "some error are more equal than others"? :P [02:55] "some errors are more like guidelines" [02:57] :P [03:01] thumper: FFS [03:01] davechen1y: hey [03:01] tried to apply your suggestions to use the errors package, all the fucking tests expect an exact string [03:01] tempted to tell you to stick your recommendation [03:01] davechen1y: that's fine for now [03:01] cannot even upgrade them to errors.Annotate [03:01] we can "fix" it later [03:01] heh, fix [03:16] Man, can't tell you how much I hate all our gc.ErrorMatches tests. What a nightmare. [03:17] i fixed it, with a hammer [03:25] axw: re ExecuteCommandOnMachine [03:25] what if it went to juju/utils/exec [03:25] davechen1y: SGTM [03:25] davechen1y: oh hum, but htat means utils/exec depends on ssh? [03:27] davechen1y: if it's a PITA, don't worry. I'd just like for hte ssh package to be a bit leaner [03:30] i think i can fix that [03:30] type Client interface { [03:30] type Client interface { [03:30] // Client is an interface for SSH clients to implement [03:30] type Client interface { [03:31] ^ honestly, it should just say "client is an interface" [03:31] for all the good that comment does :) [03:32] axw, hmm [03:32] this is quite tricky [03:32] execonmachien requires something that mathces Command(...) *ssh.Cmd [03:32] dunno if it can be teased apart easily [03:33] davechen1y: yeah, just drop it. maybe it can be refactored later, not worth blocking the move over [03:34] mkay [03:39] i'm going to loose my shit this week http://juju-ci.vapour.ws:8080/job/github-merge-juju-utils/47/console [03:39] ^ anyone want to guess why this broke ? [03:45] davechen1y: because it's using go 1.2 I'm guessing [03:46] davechen1y: (and we're trying to compile it with that when we should just be downloading it and then checking out the older rev) [03:54] axw: i think there might be some sort of conditional compilation going on there [03:54] we pin the revision we want in juju/juju [03:54] but trying to compile juju/utils, it floats freely [03:55] davechen1y: ah hm, cos we don't have a dependencies.tsv there ? :/ [03:55] i dunno if adding one automatically help [03:55] bit of an oversight [03:55] * axw shrugs [03:56] here's what I propose [03:56] 1. i go an have some lunch [03:56] 2. it magically fixes itselp [03:56] sgtm ? [03:56] :) [03:56] sounds good. I'll do the same [03:56] 1. switch to gb [03:56] 2. ??? [03:56] 3. profit [09:32] frobware, hey, I'll be a couple of minutes late for our 1:! [09:32] 1:1 [09:35] dimitern, ok [10:02] jam, fwereade, standup? === Makyo is now known as Guest72537 [10:36] fwereade: my latest rev on http://reviews.vapour.ws/r/2935/ is quite substantial, I'd appreciate a look at the last commit when you can [10:37] fwereade: there's an unrelated fix mised in there, but it's also up for review as http://reviews.vapour.ws/r/3002/ [10:37] s/mised/mixed/ [10:47] axw, thanks [11:13] axw, both reviewed [12:05] https://github.com/juju/juju/wiki/howto:-implement-effective-config-structs [12:05] ...if anyone feels like some light reading or arguing [12:56] fwereade: did you have time for a chat? [12:58] wallyworld, just about to have lunch -- what time is it for you? [12:58] 23:00, i don't mind waiting [12:59] just ping when you're free [13:07] Bug #1510533 opened: destroy-environment panics [13:10] Bug #1510533 changed: destroy-environment panics [13:13] Bug #1510533 opened: destroy-environment panics [14:02] ericsnow: wwitzel3: natefinch: please do the standup without me. cats shattered lots of glass on our kitchen floor and my dog ate some [14:02] katco: ate some cat or glass? [14:04] katco: ok [14:05] dimitern, ping === marlinc_ is now known as marlinc [14:43] sinzui: chat? [14:44] abentley: sure [15:26] Bug #1403689 changed: Server should handle tools of unknown or unsupported series === Guest72537 is now known as Makyo [16:32] Bug #1510619 opened: Wily: add machine fails using kvm and lxcbr0 === akhavr1 is now known as akhavr [17:40] mgz_: ping [17:40] voidspace: wotcha [17:40] mgz_: hey [17:41] mgz_: so we have plans to get rid of the need for ignore-addresses on master [17:41] ace [17:41] mgz_: but we're going to land the fix and test it with those needing it *before* we actually remove ignore-addresses [17:41] (I work on the proposed fix next) [17:41] mgz_: so we'll land the change to ignore-addresses on containers and master first [17:42] mgz_: because currently containers are broken when you use ignore-machine-addresses [17:42] mgz_: and next a question... [17:42] voidspace: sounds fair [17:42] mgz_: when I attempt to do an upgrade from 120/1.22 to 1.24 but using --upload-tools [17:42] mgz_: it fails with "unknown series wily" [17:43] mgz_: dimitern thought you might have encountered this, or similar, when testing upgrades with QA and know a workaround [17:45] voidspace: yeah, we've had a lot of that in testing, [17:45] mgz_: did you solve it? [17:45] not sure if I know a specific workaround when using --upload-tools for upgrade though [17:45] :-/ [17:46] I'll ask aaron [17:46] abentley: ping [17:46] bug 1403689 is part of it [17:46] bug 1403689 [17:46] Bug #1403689: Server should handle tools of unknown or unsupported series [17:46] mgz_: ah, I wondered if there was a bug for it [17:46] mgz_: thanks [17:47] unassigned for 1.24 currently [17:47] what CI does is actually use streams, which we then control [17:47] right [17:47] I thought as much, and we can't suggest that to IS I don't think [17:47] we want them to test the new binaries [17:47] but yeah, bug suggests --upload-tools to 1.25 would work? [17:48] 1.25 isn't released yet [17:48] upgrades with --upload-tools are pretty dodgy anyway [17:48] needed when you have new binaries for a user to test [17:49] voidspace: your experience mirror's abentley's frustration over the past 48 hours [17:50] sinzui: heh [17:50] ouch [17:50] voidspace: the stupid client makes assumptions about its host to decide what to upload to the series and since 1.20.x doesn't check distro-info-data correctly, it will die because of vivid or wily [17:51] right :-/ [17:51] sinzui: it makes testing upgrades / fixes for upgrade bugs impossible [17:51] hopefully the fix is correct, so we never have the issue again [17:53] voidspace: abentley might want to bu you beer [17:53] sinzui: hah [17:54] sinzui: no, I meant the fix that wallyworld has allegedly committed to 1.25 and master [17:54] not that I've done it [17:54] he hasn't committed it to 1.24 though, which is where we need it [17:54] voidspace: CI tests 1.20 upgrades to the candidate we test. abentley is updating the test to use upload-tools as needed. so your change is exactly what we are looking to test [17:54] right [17:54] so we need 1.20 and onwards fixed really [17:54] might be worth abentley pinging wallyworld about it [17:55] voidspace: yeah, we can do a 1.20 release if we need to. We just need to make several jobs non-voting before hand to check to deal with unsupported features [17:56] sinzui: although a 1.20 to 1.22 upgrade works I believe, 1.24 is the problematic version [17:56] sinzui: so just fixing 1.22 on would suffice [17:56] which is one less release at least [17:57] voidspace: we can test/release 1.22 at anytime. we have special PPA setup for its distrubution too [17:57] cool [17:58] I've added a comment to the bug [18:05] Bug #1510651 opened: Agents are "lost" after terminating a state server in an HA env [18:29] frobware: our proposed fix for getting rid of ignore-machine-addresses can't work [18:29] frobware: it's effectively what we're already doing [18:29] frobware: we might need to prefer a provider fallback address over an exact match machine address [18:29] frobware: I'll discuss it with dimiter tomorrow [18:30] frobware: meanwhile, the fix for containers has landed on 1.25 and is landing on master [18:30] frobware: and I've tested on both 1.25 and master [18:32] voidspace: pong [18:36] abentley: unping [18:36] abentley: it's about the wily issue and upgrades [18:36] abentley: see the above conversation if you want... :-) [18:36] abentley: I'll try and persuade wallyworld that we need the fix for 1.22 & 1.24 [18:39] voidspace: I'm not sure whether we need 1.22. 1.24 would be nice, given that we may need to do a 1.24.8 at some point. [18:40] abentley: well, if you want to test an upgrade *from* 1.22 (as I do as it happens and I thought you needed to) then we need it in 1.22 [18:41] voidspace: Mwuh? You mean he fixed the server instead of the client? [18:42] abentley: the error message is from the api server [18:42] not a client issue as far as I know [18:43] abentley: see bug 1403689 [18:43] Bug #1403689: Server should handle tools of unknown or unsupported series [18:43] abentley: it's the api server that rejects the upload [18:46] voidspace: The client should not try to upload tools that it knows will be rejected by the server. [18:47] katco: is your dog ok? [18:50] abentley: not sure how it was fixed [18:53] Bug #1510619 changed: Wily: add machine fails using kvm and lxcbr0 [18:59] Bug #1510619 opened: Wily: add machine fails using kvm and lxcbr0 [19:05] Bug #1510619 changed: Wily: add machine fails using kvm and lxcbr0 === natefinch is now known as natefinch-afk [19:44] Bug #1510675 opened: vSphere provider leaves behind virtual machines upon bootstrap failure [19:47] Bug #1510675 changed: vSphere provider leaves behind virtual machines upon bootstrap failure [19:50] Bug #1510675 opened: vSphere provider leaves behind virtual machines upon bootstrap failure [20:17] Bug #1510688 opened: sync-tools tries to upload agents that are not permitted by the state server [20:17] Bug #1510689 opened: juju upgrade --upload-tools tries to upload tools agents that are not permitted by the state server [20:20] Bug #1510688 changed: sync-tools tries to upload agents that are not permitted by the state server [20:20] Bug #1510689 changed: juju upgrade --upload-tools tries to upload tools agents that are not permitted by the state server [20:26] Bug #1510688 opened: sync-tools tries to upload agents that are not permitted by the state server [20:26] Bug #1510689 opened: juju upgrade --upload-tools tries to upload tools agents that are not permitted by the state server [21:59] cmars: running a bit late, can i ping you [21:59] wallyworld, sure, np [22:07] cmars, that was my fault, that wallyworld was late [22:08] alexisb, heh no worries [22:08] cmars: it's always alexisb fault [22:08] there now [22:36] axw: anastasiamac: perrito666: i have to make an emergency run to the school to drop off some stuff, so will miss standup; i'll talk to you guys when i get back to catch up [22:41] wallyworld: k [22:49] wallyworld: k