[00:05] * thumper wonders if os.Rename is stable under stress [00:05] it is the only think that would be causing this to fail imo [00:05] ah fuk [00:06] ?? [00:07] I wasn't checking errors [00:07] * thumper has a screed of them [00:07] bzzzt [00:07] directory not empty... [00:08] that is an error I didn't expect [00:08] is there is a .turd in there ? [00:08] or an editor file, or something ? [00:13] c.Check(err, IsNil) [00:13] ... value *os.SyscallError = &os.SyscallError{Syscall:"readdirent", Err:0x2} ("readdirent: no such file or directory") [00:13] huh? [00:13] this is on Unlock [00:15] ah.. I think I know what this is... [00:15] maybe [00:20] \o/ [00:20] stress test passes now [00:20] * thumper ups the stress [00:21] davecheney: what is a reasonable amount of stress in your opinion? [00:21] 3*100 showed the problem, which is now fixed [00:21] obvious joke is obvious [00:22] had to make unlock atomic at fs level too [00:22] and rename returned more errors than just ErrExists [00:22] which caught me out [00:22] it comes down to time [00:22] 1000 iterations with 10 concurrent locks takes about 2.5 seconds [00:23] wow, or 7s without the max procs [00:23] I really don't want 7s of time added to the test :( [00:24] 200 and 10 is 1.5s, which is bareable [00:24] just [00:25] ok, that has taken longer than I wanted... [00:25] but I'm off for lunch [00:26] which is really heading into town to go to the supermarket and buy the new device CD [00:43] davecheney: does juju core have any kind of automated integration testing? [01:02] bigjools: i think the best answer to that is the charm testing harness that m_3 has built [01:07] 2013/04/18 01:06:45 INFO environs/openstack: started instance "1517935" [01:07] 2013/04/18 01:06:45 NOTICE worker/provisioner: started machine 45 as instance 1517935 [01:07] 2013/04/18 01:06:45 INFO worker/provisioner: found machine "46" pending provisioning [01:07] 2013/04/18 01:06:45 INFO worker/provisioner: found machine "47" pending provisioning [01:07] ^ we need to log when the PA reloads [01:08] ok thanks [01:08] Hi there bigjools [01:08] jtv: you're doing an awesome impression of someone who has the week off :) [01:09] I get the hint [01:09] I'll be off later, through a region with spotty GSM coverage let alone internet. [01:09] I just wanted to pop online for a moment, and then had a long fight with bluetooth tethering in Raring. [01:10] (I checked out of the resort earlier this morning) [01:10] Apart from bluetooth tethering still not working except once just after installation, raring is working out pretty well so far. [01:11] Why does the Ubuntu Software Center now have a big A on it? [01:11] jtv: you can re-enable virtual desktops in settings btw [01:11] Yeah, already did thanks. [01:11] I tried to say it on IRC yesterday, but I think my network connection was in a bit of a limbo state at that point. [01:15] it seemed so! [01:19] Oh, gotta go [01:20] You may not get this message because my IRC ping time just now was 44 seconds. [01:42] https://bugs.launchpad.net/juju-core/+bug/1170176 [01:44] that's nasty [01:54] thumper: i think a nil in instance is being stored in that map [01:54] checking now [01:57] thumper: ubuntu@juju-hpgoctrl2-machine-0:~$ juju bootstrap -v --upload-tools [01:57] 2013/04/18 01:57:18 INFO environs/openstack: opening environment "goscale2" [01:57] 2013/04/18 01:57:22 INFO environs/tools: built 1.9.15.1-precise-amd64 (2193kB) [01:57] why does upload tools append a build number to the tool ? [01:58] davecheney: I don't know [01:58] that kind of sucks [01:58] i wanted to use those numbers [01:59] ask fwereade [02:02] thumper: https://bugs.launchpad.net/juju-core/+bug/1170176/comments/1 [02:03] hmm, that would explain it :) [04:49] jam: hi there, I've munged all my fslock branches into one, and addressed all the comments (I think) [04:49] jam: spent most of the day writing tests actually :) [04:50] and fixing the fallout when something failed... [05:59] "17": [05:59] instance-id: "1520273" [05:59] dns-name: 15.185.165.35 [05:59] agent-version: 1.9.15.1 [05:59] agent-state: started [05:59] "18": [05:59] instance-id: "1520275" [05:59] dns-name: 15.185.165.81 [05:59] agent-version: 1.9.15.1 [05:59] agent-state: down [05:59] agent-state-info: (started) [05:59] whut ? [06:45] * davecheney away til 18:00h [06:46] * thumper just realised that the meeting is not in 15 minutes [07:16] jam: heya, let me know when you can pair up === ChanServ changed the topic of #juju-dev to: https://juju.ubuntu.com | On-call reviewer: dimitern | Bugs: 2 Critical, 61 High - https://bugs.launchpad.net/juju-core/ [07:25] morning all [07:25] dimitern: hiya [07:25] mornin' everyone else too! [07:25] darn internet is still down [07:26] rogpeppe1: hey, what happened to status? [07:26] dimitern: sorry, it changed [07:26] rogpeppe1: I like it :) [07:26] dimitern: glad to hear it :-) [07:29] rogpeppe1: me too, even i wondered this morning [07:30] rogpeppe1: i know ctx as abbrev for context, so i wondered here too. the context argument for the command execution btw has the name ctx ;) [07:30] TheMue: now not a single occurrence of .(someType) or interface{} in sight? [07:31] TheMue: yeah, i'd forgotten that. maybe i should change ctxt to ctx to fit in [07:32] TheMue: i hadn't even realised that i'd got "ctx" and "ctxt" in the same function scope... [07:33] rogpeppe1: would be nice. the introduction of a context (or a similar type) as brace for all status operations would have been the next refactoring step, as well as getting rid of this pseudo generic structure [07:33] rogpeppe1: but i thought due to other needs with respect to the code freeze we could do this later [07:34] TheMue: i figured it was easier to do the refactoring than to get the subord and relation stuff to work nicely [07:35] TheMue: i'm afraid i found processService entirely opaque. and i think there was a problem with it too. [07:36] thumper: i don't think you've pushed your latest changes to https://codereview.appspot.com/8602046/ [07:37] TheMue: oh, i see, you've made the changes in the final branch only [07:37] oops [07:37] thumper: ^ [07:37] rogpeppe1: which changes do you refer to? [07:38] rogpeppe1: ah, you meant thumper [07:38] TheMue: yeah, sorry, tab malfunction :-) [07:41] rogpeppe1: i know that, happens often to me with robbiew, *shit* ^H^H^H^H^Hg *lol* [07:43] * TheMue just got the order to write an article about rust. will be interesting to see the differences to go [07:47] 'sup ? [07:48] davecheney, heyhey, sorry late [07:48] davecheney, it appends a build number so that uploaded tools always have dev versions [07:49] fwereade: right [07:49] but we never made any use of the concept of dev version [07:49] so now it just sticks out there like a sore thumb [07:49] fwereade: the reason I wish to complain is I need to use the build version, as I will discuss in the hangout in T-10 [07:50] davecheney, ok, cool [07:52] fwereade: https://codereview.appspot.com/8648045/ [07:52] looking for a 2nd lgtm [07:52] * fwereade looks [07:53] this turned up today in laod testing [07:53] davecheney, I don;t think that's correct [07:54] davecheney, why hide state info if the instance is missing? [07:54] davecheney, (this is not to say that panicing is correct either) [07:55] fwereade: ok, that is fine, but this is just making, https://codereview.appspot.com/8842043 work [07:55] i'm not changing the behavior [07:57] https://docs.google.com/a/canonical.com/document/d/1bSiicbYOV25fq73dZqXz738OU5l96QjkY3mqnXFdLlE/edit [07:59] hi rogpeppe1 [07:59] thumper: hiya [07:59] rogpeppe1: yes, changes all in fslock-mashup [07:59] rogpeppe1: thanks for doing this [08:00] thumper: am just reviewing. a few more comments on the fslock code after some pondering. [08:00] well, it's making it *slightly* less broken, and mea culpa for not spotting that in the review yesterday, but it's not really following intent [08:01] where did the g+ link from the even go? [08:01] event [08:01] can anybody send me the link? [08:02] fwereade, rogpeppe1: ? [08:04] davecheney, thumper: link please? [08:04] dimitern: https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.gdt9rkp5uspih9n3db6b95kccc [08:04] rogpeppe1: cheers [08:04] dimitern: i'm probably not going to be able to make it. [08:04] dimitern: will try through my phone connection, but i have my doubts [08:06] 1:05 AM [08:06] Thursday, April 18, 2013 (PDT) [08:06] Time in Portland, OR, USA [09:49] um [09:50] do we have any expectation that the packaged version will work? we don't know what the critical differences were in 1.9.14 [09:50] (other than that they shouldn't exist) [09:50] jam, rogpeppe2, dimitern: ^ [09:51] fwereade: we should try the packaged version and see whether we see the same problems [09:51] fwereade: not sure i understand your question [09:51] fwereade: it looked like the problem was client-side, so shouldn't be too hard to diagnose [09:53] * fwereade is trying to remember what the hell he saw going wrong when he tried ap-southeast-2 [09:53] ok, rogpeppe2 and dimitern, you should not be worrying about this [09:53] you have code to land :) [09:53] fwereade: I'll try with the ppa and one random region [09:54] fwereade: (after I land my stuff) [09:54] dimitern, awesome [09:54] TheMue, would you pick a region, let us know what it is, and get bootstrapping from the PPA please? [09:54] * TheMue just prepares a test image with ppa [09:55] TheMue, AFAICT us-east-1 works [09:55] fwereade: hehe, just wrote when you sent [10:00] TheMue, except... hmm, no, I think that maybe even that does not [10:04] Hi guys, I just put up for review a branch which adds constraints support in the MAAS provider: https://codereview.appspot.com/8842045/ [10:04] Please have a look. [10:05] rvba: i'm glad to see you got lbox working! [10:05] rvba, cool [10:05] dimitern: yeah, I must admit the problem was my fault, wrong bzr config. [10:06] rvba: please share your findings with the rest of the red squad, so they can set it up too :) [10:06] dimitern: already done :) [10:07] rvba: great, thnaks! [10:07] rvba, I will take a look at it but can I please ask you not to land anything today, while we try to handle the release frenzy [10:07] fwereade: what do think about reporting agent-state=pending when instance-state==pending or missing? [10:07] fwereade: sure, no problem. [10:07] rogpeppe2, I'd rather not pretend we can give an instance-state when we can't [10:07] fwereade: oops, sorry, i meant instance-id not instance-state [10:07] rogpeppe2, the list appeared sanguine about the prospect of (temporarily) missing agent-state [10:08] rvba: I'll review it shortly [10:08] ta [10:08] fwereade: the current tests assume no agent-state when instance-id is pending or missing [10:08] rogpeppe2, while an instance id is pending I'm fine with reporting only machine series [10:08] rogpeppe2, missing is a different matter [10:08] fwereade: my changes are pushing towards reporting it always [10:09] fwereade: otherwise i have to special-case [10:09] fwereade: which seems kinda unnecessary. [10:09] rogpeppe2, that's probably simplest -- the downside is that not-yet-provisioned machines are nicely visually distinct today [10:09] rogpeppe2, and this would work against that [10:10] fwereade: yeah, maybe i'll make pending the only special case [10:10] rogpeppe2, when you say special-case... ISTM that it's just one branch in one place [10:10] fwereade: sure [10:10] rogpeppe2, if it has tentacles that's a different matter [10:10] rogpeppe2, +1 on early exit on pending [10:10] fwereade: every if statement doubles the number of reachable states :-) [10:10] rogpeppe2, but I thought dimitern was doing that? [10:11] fwereade: it's actually "if id==pending {agentstate=""}. [10:11] fwereade: it meshed too closely with what i was doing already [10:11] fwereade: we agreed rogpeppe2 to take life and I'll do series [10:11] rogpeppe2, agreed, but we are trying to report on a very large number of states ;p [10:11] dimitern, rogpeppe2: isn't that just asking for conflicts? [10:11] fwereade: i was already mucking with processMachine [10:12] rogpeppe2, you have one to land and one to write and get reviewed already though [10:12] fwereade: one to land? [10:12] rogpeppe2, https://codereview.appspot.com/8821043/ ? [10:12] rogpeppe2: cmd logging [10:13] rogpeppe2, that one on top [10:13] fwereade: oh yeah; will do [10:13] dimitern, it's a significant reduction in logspam when the allwatcher's running, been approved for a day or 2 [10:14] rogpeppe2, dimitern: regardless, rogpeppe2 is messing with exactly the method dimitern needs to change [10:14] fwereade: what's that? [10:14] dimitern, processMachine [10:14] fwereade: that is true [10:15] rogpeppe2, I do not think this work is sanely parallelisable [10:15] the changes shouldn't conflict (or not badly) [10:15] fwereade: the tests are the main part of the work [10:15] fwereade: i don't care about conflicts in the code - it's all trivial [10:15] rogpeppe2, so dimitern needs to modify every one of your tests, and also your code [10:16] fwereade: hmm. dimitern shall i pass over my WIP to you? [10:16] rogpeppe2, I appreciated the ninja-rewrite last night very much but I think this is decidedly less convenient tbh [10:17] fwereade: i think that all the changes we agreed to do will clash [10:17] rogpeppe2: I'm proposing mine now [10:17] dimitern: cool [10:17] rogpeppe2, dimitern: cool, I think that is a much cleaner direction to merge [10:18] rogpeppe2, dimitern: objections withdrawn [10:19] rogpeppe2, please focus on the other branches while waiting on dimitern's to land though [10:19] fwereade: will do [10:19] fwereade: only one branch, right? [10:20] rogpeppe2, cheers -- well, 290 to land if not already done, command output to propose with the logging just in SuperCommand [10:20] fwereade: ah, thanks for reminding of that one. i should've made a list! [10:22] I'm having trouble authenticating on rietveld while proposing :( tried 10 times, sign out/in from the web site works, I authorized the app (again), still no joy - probably related to the recent google apps / ubuntu sso change? [10:36] dimitern, np, it's pretty easy to review on LP [10:37] dimitern, you have an LGTM, but considering the current circumstances I'm not keen to call it a trivial [10:38] rogpeppe2, would you glance at https://code.launchpad.net/~dimitern/juju-core/034-status-shows-machine-series/+merge/159589 briefly please? [10:38] fwereade: sure [10:42] TheMue, fwiw my current findings are that eu-west-1 works perfectly but I *think* the us-east-1 issues were down to ec2 not us [10:42] fwereade: looking [10:43] fwereade, dimitern: i might remove the omitempty, 'cos if we do have a blank series for some reason, we'll want to know [10:43] rogpeppe2: ok [10:44] rogpeppe2: can you pull my branch and merge it for me please? [10:44] rogpeppe2, you can't create a machine without a series, and you can't set a machine's series once it's created [10:44] fwereade: so it can never be empty? [10:44] rogpeppe2, yeah, I think that is a guarantee that state makes [10:44] rogpeppe2, hence no ,bool or ,error [10:44] fwereade: in which case we don't need the omitempty, right? [10:44] rogpeppe2: i'm still struggling to get lbox/lpad working - auth failing [10:44] rogpeppe2, ha, that is true [10:44] fwereade: i don't care much though [10:45] dimitern: ok, i'll merge it for you [10:45] rogpeppe2, AFAICT omitempty is entirely academic [10:45] rogpeppe2: tyvm [10:45] rogpeppe2, follow your heart [10:46] fwereade: yeah. i might leave it there for consistency [10:46] rogpeppe2, +1 [10:47] TheMue, ok, yes, us-east-1 problem confirmed as an unhappily-timed connection loss to s3 causing apparent lack of tools [10:48] TheMue, where are you looking? [10:48] fwereade: Put needs to retry :-) [10:48] rogpeppe2, it's List actually [10:48] ; [10:48] fwereade: hmm. i thought List did [10:49] wtf is this: 2013/04/18 12:48:49 RIETVELD 0xf840000150 client.Get returned (*http.Response)(nil), &url.Error{Op:"Get", URL:"http://example.com/marker", Err:(*errors.errorString)(0xf8400a26d0)} [10:49] fwereade: wanted to look at us-east-1, but will now choose a different one. had troubles with my test image. :( [10:49] TheMue, what's this test image? [10:50] TheMue, you can just install from the ppa, can't you? [10:51] fwereade: have an extra vm for it [10:52] Get http://example.com/marker: redirect blocked ??? [10:52] reported by net/http/client.Get [10:52] dimitern, have you ever visited example.com? [10:53] dimitern, it's a placeholder basically [10:53] fwereade: i *know* what it is, but why is lbox misbehaving? [10:54] fwereade: interestingly, searching for that message in google gave me a #juju-dev log where I complained about the same thing on 2012/11/21 :) [10:54] http://irclogs.ubuntu.com/2012/11/21/%23juju-dev.txt [10:54] dimitern, I was taking the use of example.com to be evidence of lbox hitting the crack pipe pretty hard today, but I don't know *why* [10:55] dimitern, does nuking your various relevant .files and reauthing help? [10:55] fwereade: tried that already [10:55] dimitern, sorry, out of ideas then :( [10:59] fwereade: yeah... drawing knowledge from my earlier self in that conversation - it seems it's a go 1.0.3 issue, which was fixed on tip, and I need to rebuild lbox with go tip [11:00] cmd/juju tests almost take 3 minutes! [11:02] FFS this is altogether too eventual for my liking [11:02] and I need food [11:03] rogpeppe2, I'm aware of those tests, they are for now the price we pay for coverage [11:03] rogpeppe2, I will be trying to figure out what the hell is taking so long very soon [11:03] fwereade: me too :-) [11:03] but for now, lunch is an absolute necessity [11:03] maybe the instance will have shown up next hour [11:04] dimitern, rogpeppe2: if you can find someone else to review everything before I return, I would encourage one of you to set the build number and follow up on my juju-dev email [11:05] dimitern, rogpeppe2: but please, whoever does that, make sure it works live ;p [11:06] dimitern, rogpeppe2: if not I'll bbiab [11:06] fwereade: ok; i'm currently doing the manual diff thing on DeepEqual output [11:10] it worked! [11:12] so, for the record: goetveld is broken before a patch from wallyworld_ (https://code.launchpad.net/~wallyworld/goetveld/auth-cookie-fix/+merge/147585) [11:13] now it works with go 1.0.3, the "redirect blocked" issue is gone and I can use it normally [11:34] everything crashes [11:34] jam: dimitern: ping [11:34] * rogpeppe2 thanks thumper for passing on the nm-applet hack [11:35] I cannot bootstrap on any region with 1.9.14 from the ppa: http://paste.ubuntu.com/5718528/ [11:36] fwereade: any idea? [11:38] currently it looks as i can bootstrap but status doesn't return :( [11:39] ah, now, a pending machine 0 [11:39] TheMue: how did you manage? with the ppa version and just "juju bootstrap" on ec2? [11:40] TheMue: no --upload-tools or --series, right? [11:41] rogpeppe2: you managed to get my branch? [11:41] dimitern: my phone went down, and i've run into unexpected difficulties with the Life change. [11:41] dimitern: will submit your branch now [11:42] dimitern: with the ppa version [11:42] dimitern: and a pure juju bootstrap [11:42] TheMue: which region? [11:43] TheMue: ah, you're running precise! [11:43] dimitern: i wanted to start from west to east, so us-east-1 now [11:43] dimitern: yes, precise [11:44] so it's not working on quantal [11:46] dimitern: i'm trying to figure out the correct logic for processAgent [11:46] dimitern: i can't convince myself that it's currently right, and the tests aren't great [11:46] dimitern: i've been writing out a truth table [11:46] rogpeppe2: I see [11:47] TheMue: i wonder if you could talk me through the logic in processAgent (it was processStatus) [11:48] rogpeppe2: the idea is to have Life(), AgentAlive(), AgentTools() and Status() for entities that support it - units and machines [11:48] rogpeppe2: and process them similarly [11:48] i can't quite get my head around this condition: status != params.StatusPending && !agentAlive && !entityDead [11:49] dimitern: i realise that [11:49] rogpeppe2: I can help with that [11:49] dimitern: it's just that under *some* conditions the agentAlive status is lost [11:49] rogpeppe2: this is used to determine if the agent is down [11:50] rogpeppe2: it's down if the machine is alive, but the agent is not and the status is not pending (i.e. provisioned and started) [11:51] rogpeppe2: never touched processAgent(), sorry [11:51] TheMue: it's the same logic you wrote in processStatus [11:53] rogpeppe2: one moment, have to open then code [11:53] TheMue: it's ok, i think i'm there [11:53] rogpeppe2: I wrote that actually [11:54] dimitern: ah, ok [11:54] rogpeppe2: see above, does it make sense? [11:54] dimitern: it's all those double-negatives makes me see boggle-eyed [11:55] rogpeppe2: simple logic :) [11:57] dimitern: yeah. i have a better intuitive grasp when it's if !(status == params.StatusPending || agentAlive || entityDead) { [11:57] rogpeppe2: change it, if you think it'll be more readable [11:57] rogpeppe2: as long as it's the same logic [11:58] dimitern: i'm not sure. it helped me, but probably only 'cos i'd been staring at it the other way [11:58] dimitern: standard boolean transformation [11:58] rogpeppe2: yeah [11:58] dimitern: i can't remember the name of the rule though [12:00] dimitern: i think there's no point in calling AgentAlive if the status is pending [12:01] rogpeppe2: yeah [12:01] rogpeppe2: correct [12:04] http://paste.ubuntu.com/5718578/ - still cannot bootstrap from the ppa (tried both us-east-1 and eu-west-1) [12:05] dimitern, 2013/04/18 14:00:46 ERROR command failed: cannot find tools: use of closed network connection [12:05] dimitern, I have been seeng that sometimes, but not always [12:05] dimitern, I don't *think* it's us [12:05] dimitern: i now have a problem with us-west-2 when creating the s3 control bucket (conflicting condition) [12:06] dimitern: us-east-1 worked fine [12:06] TheMue, s3 bucket names are global [12:06] dimitern: i've reworked the code a little (the logic should still be the same though) http://paste.ubuntu.com/5718581/ [12:06] fwereade: yeah, the issue before (with uncommented public-bucket) was different (no compatible tools found) [12:06] TheMue, you need a new name [12:07] rogpeppe2: looks good [12:07] fwereade: even if the former is destroyed? [12:07] dimitern: at least my small brain can wrap itself around it now :-) [12:07] rogpeppe2: :) [12:08] TheMue, I don;t recall that ever working, no [12:08] TheMue, dimitern: I have successfully bootstrapped and deployed in both us-east-1 and eu-west-1 with the ppa [12:08] fwereade: hmm, so when testing between east and southeast i seem to have switched my buckets. can't remember, but it looks like. [12:09] fwereade: you're running precise, maybe that's why [12:09] fwereade: and i successfully to us-east-1 [12:09] TheMue, dimitern: I have "successfully bootstrapped" in ap-southeast-2, as in I have a bootstrap instance running, but it's been running for an hour and I'm still unable to get the instance [12:09] fwereade: do we have an issue or doc to collect the test results [12:10] TheMue, creating an issue now [12:11] fwereade: thx, +1 [12:12] * rogpeppe2 hates the spot-the-difference competition when a DeepEqual fails: http://paste.ubuntu.com/5718597/ [12:14] rogpeppe2: hehe, i know that from my tests. i then replaced those map[i]i by \n and some manual sorting. so it gets easier [12:14] current mostly-manual solution: Edit ,|gofmt Edit ,x/"}/c/",\n}/ Edit ,x/,/a/\n/ Edit ,x/{./v/}/x/{/a/\n/ [12:14] :-) [12:14] TheMue, dimitern: https://bugs.launchpad.net/juju-core/+bug/1170326 [12:14] dimitern, rogpeppe2: btw how is progress? should I be reviewing, supporting, etc? [12:15] fwereade: I'm done - mine has landed [12:15] dimitern, awesome [12:15] fwereade: just working out the right way to fix the tests. at least i'm convinced the logic is good now. [12:15] rogpeppe2, ?/3 [12:16] rogpeppe2, excellent [12:16] fwereade: i've submitted the log changes [12:16] rogpeppe2, cool [12:16] fwereade: not the finished ones though [12:16] fwereade: i think status life is 100x more important [12:17] rogpeppe2, well, I did originally ask dimitern to do it because (1) he'd already started and (2) you had 2 other branches to do [12:17] rogpeppe2, and now he is kickinghis heels [12:18] fwereade: yeah, sorry, i thought life was trivial to do along with what i was doing anyway [12:18] rogpeppe2, I didn't think you were actually doing anything with status [12:18] fwereade: for some reason i thought i was [12:20] rogpeppe2, we agreed and minuted otherwise [12:20] rogpeppe2, https://docs.google.com/a/canonical.com/document/d/1bSiicbYOV25fq73dZqXz738OU5l96QjkY3mqnXFdLlE/edit# [12:21] rogpeppe2, but hey ho [12:21] fwereade: ah, i think it was because i was already half way through some changes when that was minuted [12:22] so, with tip I'm able to bootstrap with default region and public-bucket (commented out) (no --upload-tools or --series), with default-series: precise [12:22] but not with 1.9.14 from the ppa [12:22] dimitern, what's the error? [12:23] fwereade: the same - use of closed network connection [12:23] dimitern, and it's meaningless to compare tip and 1.9.14, I think [12:23] hey! [12:23] has goamz updated recently? [12:23] so 1.19.14-amd64-quantal1 is confirmed broken [12:23] fwereade: it has i think [12:24] GAAAH [12:24] magic dependency updates FTL [12:24] right, tests pass. [12:25] the difference between agent-state=pending and instance-id=pending is subtle [12:26] hmm, no goamz changes since march it seems [12:27] fwereade: you might be stuck [12:27]