[00:04] wallyworld, thumper, katco or axw : fix for bug 1451674: http://reviews.vapour.ws/r/1581/ [00:04] Bug #1451674: Broken DB field ordering when upgrading to Juju compiled with Go 1.3+ [00:06] menn0: looking [00:13] wallyworld: ta [00:14] wallyworld: just saw one thing... addBsonDField could do with a docstring [00:14] sure [00:18] menn0: haven't finished reading it, but there's a but i can see in updateBsonField [00:19] well i think it's a bug [00:19] wallyworld: ok? [00:19] the loop var "field" is being updated, but needs to be assigned back into the slice [00:19] otherwise the bson.D slice passed in will remain unmodified [00:20] wallyworld: no I think that ok b/c the slice isn't being modified, just a field of a struct inside it [00:20] that's what i mean [00:20] the field loop var is a copy of the slice value [00:20] wallyworld: if that didn't work then most of the upgrade unit tests would be failing but they still all pass [00:21] menn0: http://play.golang.org/p/P3bI04FsF9 [00:21] if i comment out // this line it prints the same slice [00:22] wallyworld: hmmm ok. i wonder why everything still works then. [00:22] nfi [00:22] i hadn't finished reading it yet :-) [00:22] i'll keep reading to see if i can see why [00:27] wallyworld: no idea why it's working but I'll change it just to be sure [00:28] menn0: ok, do you agree there's an issue? or am i on crack? [00:28] wallyworld: your example is pretty convincing [00:28] wallyworld: so I'm going to fix it [00:28] ok, would be good to understand why [00:30] wallyworld: yeah there could be a wider test problem [00:30] wallyworld: i'll look at that too [00:30] wallyworld: lunch first [00:30] that's what i'm afraid of [00:30] * wallyworld is hungry too [00:31] * anastasiamac wonders why wallyworld is afraid of lunch [00:33] Bug #1452082 was opened: restore: agent old password not found in configuration [00:34] wallyworld: this is probably nicer (and faster) than copying: http://play.golang.org/p/v4b16JDzOE [00:36] menn0: that works. i still fear the test may be faulty. but have a mouthful of food so will look ina bit [00:43] menn0, wallyworld: this is what I get: http://pastebin.ubuntu.com/10993413/ === kadams54-away is now known as kadams54 [00:45] right, so there's a bug there. but also in the test because it didn't fail [00:46] wallyworld: yep, I said as much in my review [01:10] menn0: noted [01:10] let me check, that is confusing [01:16] waigani: can I get a review? http://reviews.vapour.ws/r/1579/ [01:17] natefinch: yep. Just let me get some lunch and yours is next on the list [01:17] waigani: cool, thanks [01:18] natefinch: LGTM [01:19] davecheney: thanks [01:23] waigani, wallyworld : I definitely agree that that func needs to be changed. I'm going to figure out why the tests pass despite it. [01:23] ty, sounds good [01:30] wallyworld: I see why the everything still works [01:30] waigani: ^^^ [01:30] updateBsonDField is only used to update _id [01:30] and the correct _id is used on the txn.Op [01:30] this override the value on the document (in fact you can leave _id off documents, it gets automagically added) [01:30] wallyworld, waigani: i'll fix it anyway of course [01:31] menn0: ah makes sense, glad you found it [01:36] davecheney: exact same thing, except against 1.24, where it should have been targeted in the first place: http://reviews.vapour.ws/r/1582/ [01:42] * davecheney looks [01:44] (produced by cherry picking from the first PR, ignoring the two merge commits that prevent me from just re-PRing from the same branch... stupid merges) [01:45] Bug #1442132 changed: [packaging juju-1.23] Issues met while working on debian/copyright file [01:45] Bug #1445063 changed: addressable containers cannot resolve non-FQDN in maas [01:45] [01:45] Bug #1446662 changed: Vivid bootstrap and destroy-environment intermittently fails [01:45] Bug #1446857 changed: MeterStatusWatcher tests fail on windows test slave [01:45] Bug #1447595 changed: TestLeadership fails on windows test slave [01:45] Bug #1447853 changed: Local charms are not added to storage on upgrade to 1.22.x [01:45] [01:47] waigani, wallyworld: PR updated as per review comments: http://reviews.vapour.ws/r/1581/ [01:48] wallyworld, axw Do either of you have a moment to review http://reviews.vapour.ws/r/1583/ [01:49] sinzui: done [01:49] thank you axw [01:50] axw: time for a quick chat in standup? [01:50] menn0: will look in a sec [01:50] wallyworld: sure, brt [01:52] voidspace: ping ? [01:55] davecheney: is after midnight for voidspace, unlikely to be around [01:55] and he isn't on line even [01:58] i'll wait [01:59] https://www.youtube.com/watch?v=UJkxFhFRFDA [01:59] davecheney: while you wait can you review that second PR? ;) === kadams54 is now known as kadams54-away [02:01] davecheney: https://www.youtube.com/watch?v=6g4dkBF5anU [02:06] menn0: i might be retarded driving reviewboard, but i can't get a old-new diff to show the test changes; the test was updated i assume [02:06] wallyworld: no, the tests were fine b/c the end result was correct [02:07] hmm, ok. it worried me that the test passed even though the code was flawed [02:07] wallyworld: but by side effect [02:08] i'm still a little hestitant [02:08] when a key function in the solution doesn't work and the test still passes.... [02:08] wallyworld: as I explained updateBsonDField was only used in one place and in that case it didn't really matter what updateBsonDField did b/c mgo or mongo prefers the key from the txn.Op over the document [02:08] wallyworld: may I should just remove updateBsonDField and the call to it [02:09] wallyworld: but then we're relying on an effect of mgo or mongo [02:09] if we don't need it then yeah [02:09] wallyworld: which I guess is very unlikely to change [02:09] menn0: or test the func explicitly [02:09] i'm -1 on keeping unecessary code around [02:09] wallyworld, waigani: i'm going to remove it === kadams54-away is now known as kadams54 [02:10] there's plenty of other places in juju that use the txn key [02:10] so if mgo changes, juju will break badly [02:10] maybe remove the method and add a decent comment [02:11] it's vcs. We can go back in time to get the code if we need it again. [02:12] wallyworld: Any specific it reason to mark this bug high, other than it makes us look like knuckleheads? https://bugs.launchpad.net/juju-core/+bug/1370896 [02:12] Bug #1370896: juju 1.21-alpha1 has conf files in /var/log/juju on instances [02:13] natefinch: that, plus a user has a reasonable expectation to blow away a log dir and not break things [02:13] wallyworld: yeah, that's a good point [02:14] i can imagine sysadmins doing that regularly to reclaim space etc [02:14] wallyworld anastasiamac: if you have any time today, would appreciate if you could look over https://github.com/juju/docs/pull/411 and see if we're missing anything important [02:15] wallyworld: done [02:15] will do [02:15] menn0: ty, lookng [02:15] axw: looking :D [02:16] wallyworld: the rest of our config files are under /var/lib/juju/, is that a fair place to put them? The bug mentions /etc/ but AFAIK we don't store anything there right now [02:17] natefinch: IMO, /var/lib/juju is reasonable. longer term perhaps we should put stuff in /etc/juju or wherever [02:17] not sure [02:17] wallyworld: thanks [02:17] np, thanks for finding and fixing [02:18] wallyworld, waigani: thanks both for your thorough reviews [02:18] Bug #1326091 changed: deploying into kvm with local provider, hostnames are not unique [02:18] Bug #1326799 changed: juju should log at environment URL [02:18] Bug #1436925 changed: juju status complains "config has no UUID" when no .jenv is present [02:18] Bug #1437015 changed: debug-log spammed with leader-election messages [02:18] Bug #1438489 changed: juju stop responding after juju-upgrade [02:18] Bug #1446608 changed: agent panic on MAAS network with uppercase characters [02:18] Bug #1447841 changed: eu-central-1 AWS region V4 signing required and not supported [02:18] Bug #1449302 changed: upgrades: old machines need block devices document [02:18] Bug #1449367 changed: remove storage feature flag [02:18] Bug #1449436 changed: Environment variables are not propagated to jujud on vivid [02:18] Bug #1450146 changed: vsphere provider feature flag should apply only to bootstrap [02:18] Bug #1451297 changed: Upgrade from 1.18 to 1.23 fails: password for machine agent can't be set [02:19] menn0: I was off target, but glad it helped [02:19] thumper: your opinion? our rsyslog config files are under /var/log/juju/ right now.. is /var/lib/juju/ a suitable fix, or should we start using /etc/juju/? re: https://bugs.launchpad.net/juju-core/+bug/1370896 [02:19] Bug #1370896: juju 1.21-alpha1 has conf files in /var/log/juju on instances [02:20] man that's a lot of mupping [02:20] mupping hell! [02:20] yeah, mup is pretty muppy tonight [02:20] hehe [02:20] natefinch: I'm trying to get context [02:20] axw: anastasiamac: btw one thing we should do after feedback from william is to incude "naked" provider types in the pools list - they will appear as pools with empty config [02:21] natefinch: hmm... [02:21] wallyworld: agreed [02:21] personally I think we should start using /etc/juju [02:21] thumper: yeah, i think that's ok for longer term, but for 1.24..... [02:21] natefinch: in the near future, we'll have additional acceptable certs [02:21] /etc/juju/certs.d/ [02:21] we should do this holistically [02:22] are we expected for fix this for 1.24? [02:22] if so... just use $datadir [02:22] yes, it's on the 1.24 list [02:22] which is /var/lib/juju [02:22] stakeholder bug [02:22] and we'll move to /etc/juju Real Soon Now™ [02:22] +1 [02:22] heh ok, cool [02:23] thanks thumper [02:25] (and wallyworld) [02:25] sure [02:25] thanks for fixing [02:26] axw: added my 2c to 411 :D tyvm for keeping docs uptodate!!!! :)) [02:27] anastasiamac: thanks === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [03:40] hows it going everyone?? [03:40] Can anyone give a few examples for possible values for the flat-network-providers config for quantum-gateway? [03:46] bdx: we're mostly core juju devs on this list. The intricacies of specific charms are not really our specialty. [03:47] bdx: I think most of the charm developers are in US/UK time zones, and so probably not online right now [03:48] bdx: I recommend sending an email to juju@lists.ubuntu.com with your question, that way you can get answers asynchronously. [04:20] natefinch: Thanks! [04:35] is it possible to have a subordinate relate to another subordinate? it doesn't seem to actual cause the relationship to happen, so I'm guessing not. [04:51] Bug #1452113 was opened: log files are lost when agents are restarted under systemd [04:51] Bug #1452114 was opened: Unnecessary errors emitted during init system discovery [05:04] Bug #1452113 changed: log files are lost when agents are restarted under systemd [05:04] Bug #1452114 changed: Unnecessary errors emitted during init system discovery [05:10] Bug #1452113 was opened: log files are lost when agents are restarted under systemd [05:10] Bug #1452114 was opened: Unnecessary errors emitted during init system discovery === urulama_ is now known as urulama [05:30] wallyworld: I've started looking into placement+storage. let me know if you think something else is more important [06:43] axw: placement + storage sounds great [07:53] wallyworld: there's a race condition in my storage hook order thingy, it's a bit borken :/ [07:54] oh noes [07:54] if the storage isn't provisioned fast enough, no hooks run [07:54] (for storage-using charms only) [07:54] we will be releasing a new build in a couple of days [07:54] ok [07:55] I'll switch over to fixing this [07:55] + [07:55] 1 [07:55] I've got half way through getting placement working [08:26] what's the easiest way of determining the mac address of a container deployed on a machine? [08:27] juju ssh I guess [08:31] voidspace: from outside or an agent running inside the container? [08:31] TheMue: from outside [08:31] TheMue: but I've found it via "juju ssh" [08:31] TheMue: thanks [08:31] voidspace: ok [08:36] axw: i'm off to soccer, back later. i've got maas storage working and unit tested, just finishing test double work to allow end-end start instance to run [08:37] "working" != tested live yet [08:37] done according to spec [09:01] dooferlad: jam: standup? [09:01] omw [09:33] hello folks. What version of go are we building the juju binaries with? [09:51] gsamfira: 1.2 :D except for vivid 1.3 [10:16] Bug #1452207 was opened: worker/uniter: charm does not install properly if storage isn't provisioned before uniter starts [11:25] Hi, hows it going all? [11:26] Would someone be kind enough to share what the difference is between data-port and ext-port for neutron-openvswitch charm? .... And possibly [11:27] an example of how different params could be used? [11:55] github is down at present, so I've disabled the lander [11:56] mgz_, finally figured out https://bugs.launchpad.net/juju-core/+bug/1413910 [11:56] Bug #1413910: 1.21-rc1: Ambiguous resolution of private-address [11:56] \o/ [11:56] bdx, hello [11:56] data-port is for vlan and flat networking traffic (east/west) [11:56] ext-port is for north-south traffic when using neutron dvr [11:57] ehe, so it is asciibetical sorting related? [11:58] jamespage: also liam's bug 1435283 [11:58] Bug #1435283: juju occasionally switches a units public-address if an additional interface is added post-deployment [12:04] mgz_: just before you posted this they posted "finished emergency maintenance" [12:05] yup, I'll try re-enabling shortly [12:08] mgz_, I de-duped and commented on gnuoy's bug [12:09] jamespage: thanks, Dimiter is off this week but I will poke someone else to pick this up [12:10] jam: ^ any cunning ideas on sane network selection logic when we grow a new address? currently we do insane things. [12:46] mattyw: aha, you're ocr today [12:50] mattyw: so, I have two branches to land, but I actually want to add to pr2158 and want some advice [12:50] I think the provider should log the instance type and image type it has selected [12:51] any opinions on where I should put that? [12:51] I guess in StartInstance rather than in FindInstanceSpec [13:01] voidspace, TheMue: MAAS call? [13:02] dooferlad: in saphire? because I've got no calendar entry [13:02] TheMue: Oh, if you aren't on the invite, don't worry [13:03] dooferlad: ok, I don't worry [13:03] ;) [13:03] mgz_, sorry - was feeding my face [13:03] mgz_, happy to help [13:07] mgz_: bug link? [13:08] http://reviews.vapour.ws/r/1519 [13:08] jam: bug 1435283 [13:08] Bug #1435283: juju occasionally switches a units public-address if an additional interface is added post-deployment [13:08] mgz_, I'd favour StartInstance - as you want to log what you're about to start rather than just what's been found [13:08] mattyw: okay, adding that, then I'll poke you for a re-stamp and land [13:09] mgz_, awesome [13:18] natefinch: hey are your cards on the kanban up to date? [13:19] dooferlad: wasn't that yesterday? doesn't look like I have an invite either [13:19] voidspace: Yea, I seem to have got in on that meeting. Fun. [13:19] dooferlad: :-) [13:19] voidspace: it is another one today. [13:19] dooferlad: enjoy [13:19] wallyworld: sinzui: is bug 1451283 no longer a blocker? [13:20] Bug #1451283: deployer sometimes fails with a unit status not found error [13:20] * voidspace lunches [13:20] katco: i downgraded it because it's very intermittent [13:21] katco, it is a blocker according to wallyworld (hence the tag). We agreed to lower it to high so that it doesn't block merges [13:21] still unable to reproduce [13:21] wallyworld: i.e. do we need to remove the blocker tag? [13:21] wallyworld, I saw it last night on HP [13:21] do we have logs? [13:21] wallyworld, but my change to capture logs wasn't in place yet [13:22] ok, np. next time it happens then [13:22] so is trunk blocked or not? :p [13:24] no [13:24] because it's not critical, just high [13:24] wallyworld: so can we remove the blocker tag? [13:24] so the blocker tag is new. it used to be that regression blocked. sinzui will need to comment as i'm not 100% on the new ploicy [13:25] wallyworld, I will send an email [13:25] previously demoting to high did the trick [13:25] wallyworld, blocker means this blocks something that the release team cares about, like a release or merges [13:25] gah... why is it i can never pin down how to determine the list of trunk blockers. it's easier to submit a dummy PR haha [13:25] there's a lp query [13:25] i have 3 queries saved [13:26] all of which have been wrong at times now [13:26] yeah, the policy i think has changed from critical,tag=regression, to tag=blocker [13:26] the email will clear it up [13:27] which is not true in this case? [13:27] katco, any criticals on this list https://bugs.launchpad.net/juju-core/+bugs/?field.tag=blocker+ci&field.tags_combinator=ALL [13:27] There are none [13:28] sinzui: so the absolute rule is: tagged with "blocker" and "critical"? [13:28] katco, yes [13:28] sinzui: awesome, ty! [13:29] katco, you need to query juju-core, juju-core/1.24, and juju-core/1.23 [13:29] katco: it used to be tagged with regression and critical [13:29] katco: so that's why i simply demoted that bug to high to unblock [13:30] wallyworld: gotcha [13:30] katco: it still blocks the release supposedly if not fixed, but not landings [13:30] once we can reporduce with logs it will get pushed back to critical i suspect [13:32] katco, wallyworld true. CI will close all blocker+ci bugs when a branch passes. When we have a pleased branch, CI can confidently close all blocking bugs tagged with ci [13:32] wallyworld, katco CI did that yesterday and left comments on bugs explain how it knows the bug was fixed [13:32] \o/ [13:32] sinzui: yeah that was nice :) [13:41] katco: sorry, updating kanban now [13:42] natefinch: no worries... the more up to date it is, the less i bug people ;) [13:43] mgz_: voidspace: it seems like in https://bugs.launchpad.net/juju-core/+bug/1435283 we'd want hysterisis. So if we are currently using an IP address, if we see a new one, don't switch to it. [13:43] Bug #1435283: juju occasionally switches a units public-address if an additional interface is added post-deployment [13:43] katco: one of my bugs is reviewed and ready to merge, but 1.24 is blocked, so it can't land... should I set the card to done, or in progress and blocked? It's technically something I still need to remember to do (land it once 1.24 is open). [13:43] We do that for stuff like "move the currently active API IP address to the front of the list" [13:43] we could "move the last known IP addresses ahead of the rest" [13:43] natefinch: is wwitzel3 around? [13:44] natefinch: "under review" and blocked [13:44] katco: ok thanks [13:44] I don't know what time he shows up these days [13:44] I may try to bpi [13:44] ping him later [13:44] natefinch: although i don't see that 1.24 is blocked? [13:45] katco: oh... maybe it has opened since last night [13:45] * natefinch hadn't actually checked in the last 9 hours :) [13:47] natefinch: there are no open critical bugs with the "blocker" tag [13:48] katco: cool [13:57] sinzui: xwwt: are we still expecting to cut beta1 tomorrow? [14:01] jam: hey, sorry, normally I am on earlier, I just had some errands to do this morning [14:01] sinzui: can you help me assign this bug to the right milestones etc? I have no clue how to make launchpad set it to be correctly targeted. https://bugs.launchpad.net/juju-core/+bug/1452285 [14:02] Bug #1452285: logs don't rotate [14:02] natefinch: done it [14:02] mgz_: thanks [14:02] katco, maybe. This release is taking a long time. We need to talk about a 1.23.3 release [14:02] natefinch: stand up [14:03] natefinch, I don't see a problem with it. which milestone offends you? [14:04] jam: I'll be online until 12AM, May 7th UTC [14:04] sinzui: mgz_ fixed it [14:05] * mgz_ too fast [14:05] sinzui, mgz_: I don't know how to add more milestones after creating it (or choosing more than one when creating it). [14:06] natefinch, ah, because you need to "Target to series" to add tasks, when assign the a milestone to each task [14:06] natefinch: it's "Target to series" for reference. then leave the main heading at current master (1.25 here) and add the older branches that we may want backports for [14:19] natefinch: wwitzel3: ericsnow: awesome, "the video call ended because of authentication issues" [14:19] katco: just making you log in with sso again? that seems like a weekly thing [14:20] mgz_: it just kicked me off in the middle of a meeting... refresh, and went right back in w/o any interaction from me [14:20] random... [14:21] team I see a blessed on 1.24, well done all! [14:21] nice way to come back from the dead :) [14:21] huzzah! [14:22] katco, alexisb : I think we need to cut the vmware announcement from the release notes because it is still incomplete: https://docs.google.com/document/d/1qKWvSZ06Vx3ZI2RxYg6P7sWdIvOD5QXPfvpUNEtImMA/edit [14:24] sinzui, ug, yeah we can follow-up with altoros on that today. can we add the notes before stable goes out? [14:25] alexisb, absolutely. We always add to the notable with beta releases. [14:25] sinzui, pull them then [14:25] Bug #1452285 was opened: logs don't rotate [14:35] alexisb: sinzui: eric is assigned to the work, but he has critical bugs he needs to take care of today. i would expect those release notes to slip to next week based on what he has on his plate. [14:36] alexisb: hope you're feeling better btw [14:40] jam: right, that sounds like the right thing to do [14:40] jam: IP addresses should not be merely lexicographically sorted when setting in state [14:40] *merely be [14:41] voidspace: yeah, the sort order seemed to match what jamespage found on the last post to the bug. 99 coming after 110 [14:41] or whatever the numbers were, it was 9* vs 1** [14:41] jam: so change the algorithm to preserve the first and sort the rest... [14:42] jam: sorted is a bit broken tho [14:42] jam: as it makes the assumption that the 'lowest' ip address is actually the one configured [14:42] why would the agent switch to a private-address that it knows is not actually configured on the machine? [14:47] katco, I really want to push altoros to help with that, I can follow-up with sergey today, and understood on eric's commitments [14:57] alexisb: ok sounds good [14:58] jamespage: so that's two issues then - the address changing unnecessarily, and an incorrect address being used [14:58] jamespage: *both* seem wrong, and would have different causes (fixing either might mask the other for your case) [14:58] rick_h_: ping [14:58] katco: pong [14:59] rick_h_: are you aware of this: https://docs.google.com/document/d/1vcpc1xLMdxvo_edMMlB2RS-h4I9eefkk5-a_Ey8ZoQE/edit# ? [14:59] rick_h_: we have committed to this for the cycle, and it looks like there are a lot of tasks for your team [15:00] katco: will look after standup. The feature's come up before but not seen the latest revision of the spec for it. [15:00] rick_h_: sounds good... just don't want you caught blindsided [15:00] katco: appreciate the warning [15:15] jam, if you are still around katco could use your assistance === urulama is now known as urulama__ [15:37] Bug #1441904 changed: jujud won't start if apt-get of juju-mongodb package fails [17:01] ericsnow: ping [17:01] wwitzel3: hey [17:04] Bug #1452381 was opened: Failed to deploy vivid LXCs on vivid host [17:34] Bug #1452393 was opened: Use a dependency injection approach in the bootstrap command [17:47] sinzui: ping [17:47] hi bac [18:04] Bug #1451385 was opened: LDS 15.04 - OpenStack - lxc fails to retrieve tmpl to clone [19:00] wwitzel3: ericsnow: you guys are kicking butt. wwitzel3: way to step up and help ericsnow out. [19:00] wwitzel3: +1 [19:04] hello all [19:05] mgz_: better here? [19:06] or do we turn this into an email [19:06] ? [19:06] and by we I mean you? [19:06] :p [19:06] perrito666: we fine [19:06] perrito666: so, `juju authorised-keys import --help` [19:07] we can't break cli in that the command still needs to work as written [19:07] but we can certainly do stuff like making the errors printed saner if we get structured data back over new api [19:07] or add a -v flag to do something other than silence in the success case [19:08] I would go for an extra flag [19:08] I have to ssume that someone is expecting the current output [19:08] for printing stuff to stdout, sure [19:08] not for changing the error message output [19:08] we've already done that [19:08] twice [19:09] fair [19:09] very few scripts are going to pipe stderr somewhere then care about its contents, and certainly not for manual-ish commands like this [19:10] (it is being scripted by the plugin mentioned in the bug, but that's a straight exec type thing) [19:12] mgz_: ok so, fwport the fix from 1.23 to 1.24 and then master gets the revamped one, makes sense? [19:13] yup [19:13] rick_h_: got a minute to chat about juju min version? [19:14] not at the moment otp [19:14] katco: ^ [19:14] rick_h_: no worries... ping me when you're free? [19:14] katco: sure thing [19:32] Bug #1452422 was opened: Cannot boostrap from custom image-metadata-url or by specifying metadata-source [19:34] i need a volunteer to triage bug 1452422 that is NOT already working on critical issues [19:34] Bug #1452422: Cannot boostrap from custom image-metadata-url or by specifying metadata-source [19:36] cherylj: perrito666: ^^ [19:39] katco: I got it [19:39] mgz_: ty [20:05] katco: still free? [20:05] rick_h_: yep [20:20] Bug #1450706 changed: juju-core 1.23.2 fails with an error on destroying a local environment on vivid [20:29] Bug #1450706 was opened: juju-core 1.23.2 fails with an error on destroying a local environment on vivid [20:32] Bug #1450706 changed: juju-core 1.23.2 fails with an error on destroying a local environment on vivid [21:10] thumper: did the hangout drop for anyone else ? [21:10] davecheney: nope [21:10] maybe it's google deciding i need to refresh my credentials [21:15] sinzui: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457 [21:15] Bug #1452457: Please import golang-1.4.2 from debian/sid [21:15] bug for raising the version of go in W [21:15] sinzui: how do I target this to W only ? [21:16] davecheney, we don't have permission to nominate a series [21:17] davecheney, maybe we should subscribe strikov and rbasak [21:17] sound good [21:17] i love giving others work, remotely [21:18] and done [21:19] mazel tov [21:28] alexisb: thanks for the linaro connect, the linaro folks are being very responsive [21:28] davecheney, you are most welcome and I am very glad [21:29] I also got your hardware order in and am working shipping details with an apm ops lady - who is also very responsive and nice [21:29] o/ alexisb [21:29] alexisb: did you want to catch up today? [21:29] so hopefully arm hardware woes are past us [21:29] thumper, we should [21:29] about to go into an hour of meetings [21:29] but I can ping you when I am done [21:30] sure [21:56] alexisb: aaand, i'm in [21:56] 30 muntes to get access to linaro arm hardware [21:56] 3 months to get access to canonical arm hardware ... [21:57] yay! [21:57] well on the access part [21:58] they appear to be running a very similar kernel [21:58] i wonder if i'll be able to trigger the bug ... [21:58] kernel bug that is [22:02] Bug #1435644 changed: private cloud:( environment is openstack )index file has no data for cloud [22:10] wallyworld, re: bug 1442719. This is a case where the affected series is very old. and even if we try to fix it, there is no guarantee that users will get a 1.20.15 [22:10] Bug #1442719: juju sync-tools fails with windows streams [22:10] sinzui: maybe mark as won't fix? [22:10] wallyworld, I think we need to confirm the issue is not in 1.21 and above and maybe move my work around into the description [22:11] sinzui: sounds reasonable [22:11] wallyworld, well I don't see how the bug can be in 1.21 because that is the series that introduced windows streams [22:11] yes [22:12] wallyworld, yes, it is not possible because generate-tools made the data [22:12] wallyworld, so, wont fix and update work around [22:12] +1 [22:15] alexisb: sorry, google hates me, still trying to get in [22:16] lol [22:16] I thought it was on my side [22:16] I just restarted chrome [22:20] waigani_, We think bug 1384549 is out of scope for 1.24. I want to delete the 1.24 task on the bug that says you are working on it now [22:20] Bug #1384549: Running Juju ensure-availability twice in a row adds extra machines [22:22] wallyworld: we have several fixes up that aren't blockers but need to land for the next 1.24 release... [22:22] ericsnow: otp, be with you soon [22:22] wallyworld: np [22:26] Bug #1442719 changed: juju sync-tools fails with windows streams [22:28] sinzui: yep. I've unassigned myself. Thanks for the heads up. [22:29] np waigani_ [22:32] gah, adding logging to golxc - by default logs to stdout, which results in the logging lines going to the tools version output by jujud so I can't bootstrap (invalid tools version) [22:33] have to reconfigure logging for golxc [22:41] voidspace: ahh... wat? [22:41] voidspace: IIRC, no [22:41] voidspace: happy to chat about logging with you [22:42] thumper: hey, hi [22:42] thumper: I just changed a logging call in golxc from logger.Tracef to Warningf and suddenly couldn't bootstrap [22:42] ERROR failed to bootstrap environment: cannot upload bootstrap tools: invalid version "2015-05-06 22:20:30 WARNING golxc.run.lxc-config golxc.go:448 run: lxc-config [lxc.lxcpath]\n2015-05-06 22:20:30 WARNING golxc.run.lxc-config golxc.go:448 run: lxc-config [lxc.lxcpath]\n1.23.3.1-trusty-amd64" printed by jujud [22:43] thumper: so what do you mean by "no" [22:43] voidspace: haha [22:43] ah [22:43] voidspace: hangout? [22:43] thumper: sure [22:44] voidspace: https://plus.google.com/hangouts/_/canonical.com/golxc [22:45] thumper: omw [22:48] export JUJU_LOGGING_CONFIG=juju=DEBUG;golxc=TRACE [22:57] juju set-env logging-config=... [22:59] thumper, I am free for a while if you are available to chat [22:59] ericsnow: so, thse fixes, you going to land them? [22:59] alexisb: yep [22:59] alexisb: our normal hangout? [22:59] wallyworld: landing is blocked [22:59] oh, i see, didn't realise [22:59] yep [23:00] ericsnow, wallyworld I don't see any critical blockers [23:00] sinzui: me either [23:00] i just checked [23:01] ericsnow: why do you say landings are blocked? [23:01] "Build failed: Does not match ['fixes-1444861', 'fixes-1451297']" [23:01] That isn't even a ci bug [23:02] ericsnow: that isn't blocking 1.24 [23:02] * sinzui checks code on server [23:02] but it does block 1.23 [23:02] wallyworld: ah, I was trying to merge into 1.23 (and then forward-port) [23:02] i'll reduce to high [23:02] no reason to be critical for 1.23 and high for 1.24 IMO [23:03] bug 1451297 is fix release in master and 1.24. the bug is closed from CI's view [23:03] Bug #1451297: Upgrade from 1.18 to 1.23 fails: password for machine agent can't be set [23:04] wallyworld, that bug was only critical while there wasn't a fix, but still, 1.24 and master haven't been blocked for 1.5 days [23:04] sinzui: ericsnow was trying to land in 1.23 first. that was blocked but i degraded a bug to high [23:04] me too :) [23:05] to match it's severity on 1.24 and master [23:05] lol [23:05] ericsnow: try again [23:05] severity is different for each branch [23:05] wallyworld: trying [23:05] sinzui: agreed, but in this case.... [23:05] i think high is ok [23:07] ah ericsnow wallyworld are you using the check blocker's script from 2 weeks ago. The current script has a different command line [23:07] sinzui: i just use a lp query [23:08] i guess i could or should use the script [23:12] wallyworld, You will probably be angry because it wants you to login even for anon requests. [23:12] we haven't fixed it yet [23:12] sinzui: np, i'll stick with my bookmark :-) [23:14] Bug #1452490 was opened: jujud version fetched with combined output for bootstrap tools [23:31] davecheney, I am on our 1x1 hangout if you would like to meet today [23:41] sinzui: so bug 1444912, just confirming, we will mark as Incomplete [23:45] alexisb: oh, is that today ? [23:45] it's not on my calendar [23:45] but you're ill and i have nothing to say [23:45] so let's skip it [23:45] davecheney, heh ok [23:45] davecheney, I trust you know how to reach out to me if needed [23:46] alexisb: history has shown that to be true :) [23:47] :)