axwevilnickveitch: any significance to the pear and cake? what you happened to be eating at the time you merged? ;)01:12
rick_h_axw: heads up. I've added you to a seattle session per alexisb's request as the expert as we got poking at an issue with ssh keys being requires for createEnvironment. Some notes in the doc linked to the session: https://docs.google.com/document/d/1JsVFVx0P6wKdBIPqYPOBiYqYNRpb5kR8ept_NfmkXPw/edit#heading=h.13n2f81u0zpj01:15
rick_h_axw: just a heads up in case there's any pre-thought required :)01:15
axwrick_h_: thanks01:15
davechen1ythumper: fyi https://github.com/gorilla/websocket#gorilla-websocket-compared-with-other-packages01:23
thumperdavechen1y: handy01:33
davechen1yhopefully it helps01:37
davechen1yhttp://reviews.vapour.ws/r/2742/, anyone ?01:43
perrito666davechen1y: ship it01:46
perrito666I thought I was the only one changing deps by hand01:46
davechen1yPosted 7 minutes from now (Sept. 24, 2015, 11:56 a.m.)01:49
davechen1y^ reviewboard lives in the future01:49
anastasiamacdavechen1y: yes, bleeding-edge technology :P01:50
davechen1yperrito666: thanks01:50
davechen1yaxw: cherylj natefinch-afk you have reviews that have been approved01:53
davechen1yplease land then01:53
axwdavechen1y: mine are all blocked01:54
axwI would love to land them :)01:55
davechen1yaxw: blocked on what ?01:55
davechen1yare they against master, or a branch ?01:55
axwdavechen1y: 1.24 and 1.25 are blocked01:55
axwthose two01:55
thumperI think I've landed an unblocker for 1.2401:59
thumperwaiting the bless01:59
thumperand I'm looking at 1.25 bug01:59
thumperbut missing info01:59
thumperdavechen1y, waigani: team meeting time02:03
davechen1ythumper: see you there02:05
waiganithumper: coming02:07
=== natefinch-afk is now known as natefinch
perrito666davechen1y: if you spoke spanish I would get you to record my answering machine message02:22
axwthumper waigani: fixed the link. for some reason the event shows up on my calendar twice: one I can edit, one I can't02:25
waiganiaxw: nice work :)02:25
perrito666axw: one is your event (it copies when you accept it) the other one is the actual event02:26
axwperrito666: ah.02:26
natefinchgood god our watcher code needs better documentation02:42
natefinchwhat's the correct way to watch a collection where I just want a notification whenever anything is added to the collection?  Looks like I should use newEntityWatcher or newDocWatcher, but they're both woefully underdocumented as to what "key" is supposed to be, and it is ever so helpfully an interface{} :/02:51
thumpernatefinch: I have no idea sorry02:51
thumperhazaah, blessed 1.2402:59
* thumper forward ports to 1.2503:00
wwitzel3aka patch or commit03:03
natefinchperrito666: http://www.amazon.com/gp/product/B004UWY4KG03:05
perrito666ok ok,ill buy one03:09
natefinchperrito666: lol03:10
perrito666k ppl gnight03:11
natefinchperrito666: I think I don't have a tron poster, oddly enough.  I have several others - star wars (a reproduction), hackers, 5th element... forget what else.  I had a dedicated movie room for a long time that I decorated... now they're just in storage.  I'll take out the hackers poster and put it next to my desk, though.03:12
natefinchperrito666: night03:12
perrito666natefinch: ill send one of those to the hotel once I figure where it is03:12
thumperis there any way to go back through the logs of a closed hangout?03:53
natefinchthumper: not to my knowledge03:55
thumpercmars: ping?04:08
* thumper is being hopeful04:08
davechen1ygoogle says you can retrieve them via gmail04:10
thumperdavechen1y: and if you dn't use gmail?04:11
davechen1ywell, i couldn't find it in gmail04:15
davechen1yit might allso be in the hangouts app on g+04:15
* davechen1y tries to help, but hits is knee on the coffee table04:16
davechen1ymongo is one shithouse piece of software04:29
thumperdavechen1y: what brought this on?04:54
* thumper is amused with "shithouse" as Ian uses that too04:54
thumpermust be an ozzie thing04:54
* thumper back later for TL meeting04:55
=== thumper is now known as thumper-afk
davechen1ythumper-afk: i'm fucking sick of loosing 1 CI run out of 5 because mongo shits itself on startup04:58
axwwwitzel3: you're not working, right? I'm going to fix this 1.25 blocker if you're not actively working on it atm06:23
axwdavechen1y: would you kindly review http://reviews.vapour.ws/r/2745/? fixes the 1.25 blocker06:45
rogpeppeaxw: hiya06:55
davechen1yaxw: ship it06:55
axwdavechen1y: ta06:55
axwrogpeppe: howdy06:55
rogpeppedavechen1y, axw: do you know what the procedure is meant to be for merging a feature branch, by any chance?06:55
axwrogpeppe: nope. I do know that it has to be blessed by CI first06:56
axwother than that, no06:56
rogpeppeaxw: it has (finally!) been blessed06:56
davechen1yrogpeppe: nfi06:56
rogpeppeaxw: and i wanna get it merged quickly before it gets loads more conflicts and consequent CI cursing06:56
axwrogpeppe: simplest way would be to create a new branch and rebase it onto master, then propose06:58
rogpeppeaxw: i'm not sure that it should be rebased06:58
axwrogpeppe: well maybe not "simplest"... but easiest :)06:58
rogpeppeaxw: but in this case, perhaps it should06:58
rogpeppeaxw: 'cos it's only one commit anyway06:58
rogpeppeaxw: ok, i'll give that a go06:59
axwrogpeppe: quick, while master's still unblocked :)06:59
* rogpeppe types like lightning06:59
axwit's been a nightmare week for getting stuff merged06:59
rogpeppeaxw: yeah07:00
rogpeppeaxw: my last branch failed because of this error:07:00
rogpeppe... value *errors.Err = &errors.Err{message:"", cause:(*net.OpError)(0xc2103e3640), previous:(*errors.Err)(0xc21028a050), file:"github.com/juju/juju/state/open.go", line:114} ("cannot create index: local error: bad record MAC")07:00
rogpeppeaxw: do we know what causes that sporadic failure?07:01
axwthat old chestnut07:01
axwI think it's a mongo WONTFIX07:01
rogpeppeaxw: marvellous07:01
axwfixed in 3.0 IIRC07:01
axwor maybe 2.607:01
rogpeppewell, let's just change mongo versions! :)07:01
axwrogpeppe: perrito666 is working on that, making good progress07:01
rogpeppeaxw: moving to 3.0 ?07:02
axwrogpeppe: yup07:02
axwthere's some fun migration steps required, that's the main issue07:02
axwyou have to go 2.4 -> 2.6 -> 3.007:02
rogpeppeyay! another day, another bunch of conflicts.07:03
rogpeppeaxw: really? the db format has changed?07:03
axwrogpeppe: I don't know why it's necessary07:04
rogpeppeaxw: so any old juju installation needs to go through that upgrade path. that's awkward.07:04
axwrogpeppe: yes, but perrito666 is working on making it all automated07:05
rogpeppeaxw: yeah, still awkward and probably error-prone and slow though :)07:06
rogpeppeaxw: any chance of a quick LGTM on this branch please (now officially blessed :]) https://github.com/juju/juju/pull/327507:13
axwrogpeppe: looking07:14
rogpeppeaxw: ta07:14
axwrogpeppe: LGTM07:16
rogpeppeaxw: ta!07:16
* rogpeppe hits the $$merge$$ button after more than two weeks...07:17
rogpeppeaxw: really hoping that your in-merge-progress branch won't conflict :)07:19
axwrogpeppe: mine's to 1.2507:20
rogpeppeaxw: phew07:20
voidspacedooferlad: frobware: omw to standup - just wrestling firefox09:00
frobwarefwereade, coming to standup?09:02
fwereadefrobware, oops, ty09:02
voidspacefwereade: when you have some time could you check the transaction in this updated PR: http://reviews.vapour.ws/r/2593/09:18
voidspaceI *think* it's complete :-)09:18
natefinchfwereade: you around?09:54
fwereadenatefinch, yeah, what can I do for you?09:54
natefinchfwereade: I'm trying to set up a watcher that'll notify me whenever anything is added to a collection.  Am I right in thinking we don't have a general purpose type/function for doing this yet?09:56
fwereadenatefinch, take a look at the action watcher, it's implemented in a couple of layers, I suspect one of them will solve at least half of it for you09:56
fwereadenatefinch, newIdPrefixWatcher?09:58
natefinchfwereade: so, let me make sure I'm not going down the wrong path here.  This is for the unit assignment worker... when a service is added, I store the unit assignment data as a document in this new collection.  then with this watcher I'm building, the worker will get notified and do the assignment09:58
fwereadenatefinch, yeah, that sounds entirely sane to me09:59
fwereadenatefinch, and notifying only on add is also entirely sane, just make sure you clearly document what the strings it sends actually mean10:00
natefinchfwereade: so, I'm not sure I can properly act on just the information in the ID.... I need the unit name and the placement directive for the unit.  dumping that all into the id seems like too much10:01
fwereadenatefinch, yeah, definitely, I'd be inclined to just send out the unit ids10:02
fwereadenatefinch, then have the worker request the relevant info in bulk10:02
fwereadenatefinch, or, indeed, just send the list of units back up -- I doubt you'll have the opportunity to extract the actual assignment logic from state10:04
natefinchfwereade: is the list of units useful?  I wasn't even going to bother since I'd have to get the rest of the data from the collection anyway, I was just saying "hey, go run everything in the collection"10:04
fwereadenatefinch, I'll cop to it being a bit forward-looking -- you could just have a NotifyWatcher that triggers on any add, and an assign-everything api method10:06
fwereadenatefinch, but as it is I think we have way too much detailed assignment logic in state10:07
fwereadenatefinch, which responsibility could/should be extracted10:07
fwereadenatefinch, so, if anything, I'm thinking the ideal is (1) watcher sends unit list (2) worker requests corresponding assignments in bulk (3) worker requests application of corresponding assignments in bulk10:08
natefinchfwereade: I can do that - it at least keeps the logic of where we get the assignments separate from the actual assignment logic.10:12
fwereadenatefinch, because (1) that opens a path towards putting some of the machine-selection/addition logic outside state, and thus towards *consolidating* the various implementations that have grown up around deployer, gui, et al; and (2) assuming we properly separate the "service" from the facade that exposes it, we ensure the assignment service is decoupled from the worker that implements it10:12
fwereadenatefinch, awesome10:13
fwereadenatefinch, (I mean "service" as in https://github.com/juju/juju/wiki/Managing-complexity )10:14
natefinchfwereade: btw, is it me, or is idPrefixWatcher a terrible name for that type?10:14
fwereadenatefinch, I think you're right10:14
fwereadenatefinch, I would not want you to think you should preserve horrible type names just because they happen to exist10:15
natefinchfwereade: ha, no worries there10:15
natefinchmattyw: you around?10:18
mattywnatefinch, I am10:18
mattywnatefinch, what can I do for you?10:19
natefinchmattyw: document this better  :)  https://github.com/juju/juju/blame/master/state/watcher.go#L148810:19
mupBug #1499277 opened: api: Client.UploadTools does not use error code <juju-core:New> <https://launchpad.net/bugs/1499277>10:20
mattywnatefinch, like this https://github.com/juju/juju/blame/master/state/watcher.go#L1474. or is that not good enough10:20
natefinchmattyw: no... wtf is the key in dockey?10:21
mattywnatefinch, I tak you're point - I'll tell you and then turn it into docs10:22
natefinchmattyw: thanks :)10:23
mattywnatefinch, the original watcher just took keys ..string that it would watch for changes. The changes I made was to allow you to do that across collections. so you need to associated each key with a collection. So having those in a struct seemed like the best approach10:23
mattywnatefinch, I'm embarrassed, I thought I documented this much better, I certainly remember wiring something somewhere10:24
natefinchmattyw: luckily easily fixable10:26
mattywnatefinch, do you think that's sufficient documentation?10:26
mattywnatefinch, (what I just typed)10:26
natefinchmattyw: you still haven't explsained what the key is :)10:27
axwfwereade: any chance of another review on http://reviews.vapour.ws/r/2685/ later?10:27
fwereadeaxw, sure10:28
mattywnatefinch, the key is actually the id of the document, now that you mention it, it's a terrible name10:28
mattywnatefinch, I was keeping in line with the existing getTxnRevno function which calls that value key, but I probably should have renamed that as well10:29
mattywnatefinch, https://github.com/juju/juju/blame/master/state/watcher.go#L151110:29
natefinchmattyw: if it's just an id (which is a string, right?), why is it interface{}?10:29
mattywnatefinch, that's a good question, probably a hangover from whatever was before10:30
mattywrogpeppe, ping?10:30
rogpeppemattyw: pong10:31
mattywrogpeppe, do you know why the key in this function is an interface{} https://github.com/juju/juju/blob/master/state/watcher.go#L151110:31
rogpeppemattyw: yes10:31
rogpeppemattyw: but i'm not telling you10:31
mattywrogpeppe, because it's only used to findId, but id will always be a string right?10:31
mattywrogpeppe, I'll let you win next time we play dominion10:32
mattywtrying to work out if you're really not going to tell us, or just typing...10:33
rogpeppemattyw: it's an interface 'cos theoretically you don't need to use strings10:34
rogpeppemattyw: although in practice we only use strings10:34
mattywrogpeppe, I thought mongo required it to be a string10:37
mattywrogpeppe, or stringable10:37
rogpeppemattyw: i don't think so10:37
rogpeppemattyw: it can be an int for example10:37
* mattyw consults the mongodb he felt forced into buying last week10:37
mattywrogpeppe, natefinch huh, TIL10:41
mattywdb.foobar.insert("_id": {"foobar":"foo"})10:41
mattyw{ "_id" : { "foobar" : "foo" }, "bar" : "foo" }10:41
mattywnatefinch, I'll improve the docs, is there anything else you need?10:42
mattywrogpeppe, I reckon getTxnTevno should take id interface{} rather than key10:46
mattywrogpeppe, natefinch I'm doing that now unless ther are objections10:46
rogpeppemattyw: it looks like the word "key" is used more than just there in that file10:47
rogpeppemattyw: e.g. newEntityWatcher, docKey, etc10:47
rogpeppemattyw: so it might be better to be consistent in the naming there10:47
rogpeppemattyw: it would probably be fine to change it all though, docKey -> docId etc10:49
rogpeppemattyw: (if you do, please do it as a separate PR)10:49
urulamadid anyone try to bootstrap an env with 1.26 and then bootstrap it again (by mistake) with 1.24.6, reusing the .jenv file? bootstrap will continue and environment set up with 1.26 will get wiped out11:51
mattywurulama, that sounds nasty - can you open a bug?11:56
=== psivaa is now known as psivaa-lunch
urulamamattyw: i'll verify it first, then yes, will do ...11:57
mattywnatefinch, http://reviews.vapour.ws/r/2748/12:06
mupBug #1499332 opened: "no such host" when bootstrapping manual provider <juju-core:New> <https://launchpad.net/bugs/1499332>12:17
mupBug #1499332 changed: "no such host" when bootstrapping manual provider <juju-core:New> <https://launchpad.net/bugs/1499332>12:20
mupBug #1499332 opened: "no such host" when bootstrapping manual provider <juju-core:New> <https://launchpad.net/bugs/1499332>12:26
mupBug #1499338 opened: charm GET endpoint is not authenticated <juju-core:New> <https://launchpad.net/bugs/1499338>12:47
mupBug #1499338 changed: charm GET endpoint is not authenticated <juju-core:New> <https://launchpad.net/bugs/1499338>12:50
mupBug #1499338 opened: charm GET endpoint is not authenticated <juju-core:New> <https://launchpad.net/bugs/1499338>12:56
=== psivaa-lunch is now known as psivaa
mupBug #1499356 opened: all units have false hook errors after reboot <sts> <juju-core:New> <https://launchpad.net/bugs/1499356>13:26
mupBug #1499356 changed: all units have false hook errors after reboot <sts> <juju-core:New> <https://launchpad.net/bugs/1499356>13:32
* fwereade collecting laura, bbiab13:41
mupBug #1499356 opened: all units have false hook errors after reboot <sts> <juju-core:New> <https://launchpad.net/bugs/1499356>13:44
sinzuicherylj: 1.24 is unblocked, you can merge if you were waiting14:08
cheryljsinzui: thanks!14:09
mupBug #1499400 opened: number of disks constraint for maas provider <juju-core:New> <https://launchpad.net/bugs/1499400>14:36
mupBug #1499400 changed: number of disks constraint for maas provider <juju-core:New> <https://launchpad.net/bugs/1499400>14:48
mupBug #1499400 opened: number of disks constraint for maas provider <juju-core:New> <https://launchpad.net/bugs/1499400>14:57
frobwarebootstrapping on ec2 with 1.25 I just got "WARNING expected one instance, got 2." Is this a warning I can/should ignore?15:06
frobwaredooferlad, voidspace: more spaces related issues https://bugs.launchpad.net/juju-core/+bug/149942615:22
mupBug #1499426: deploying a service to a space which has no subnets causes the agent to panic <network> <juju-core:New> <https://launchpad.net/bugs/1499426>15:22
voidspacefrobware: I've tracked down the cause of the bug dooferlad reported15:25
mupBug #1498982: failed configuring a static IP for container "1/lxc/0": cannot allocate addresses: instId not supported <network> <juju-core:New> <https://launchpad.net/bugs/1498982>15:25
voidspacefrobware: fixing the new bug you reported should be easy enough15:26
voidspacefrobware: but it should be fairly high priority15:26
frobwarevoidspace, I think I set it as high - no?15:27
voidspacefrobware: yeah15:27
voidspacefrobware: I'm also playing with bootstrapping to ec2 - and I'm seeing the "WARNING: expected one instance, got 2"15:27
voidspacefrobware: it's probably / possibly because we're both using the account15:27
frobwarevoidspace, ahh15:28
voidspacefrobware: bootstrapping seems to be successful anyway15:28
voidspacedooferlad: interestingly, deploying a container to ec2 with addressable containers switched on seems to work for me!15:29
dooferladvoidspace: what address does it get?15:30
frobwarevoidspace, dooferlad: so who wants to pick up which bug? voidspace does it make sense for you to continue with 149898215:30
dooferladvoidspace: does it manage to assign a static IP?15:30
voidspacedooferlad: it got a 10.0 address, which is correct I think15:30
dooferladvoidspace: 10.0.3.* is wrong.15:30
voidspacedooferlad: ah, right15:31
dooferladvoidspace: those are from the LXC bridge15:31
voidspacedooferlad: nothing at all in the logs15:31
voidspacedooferlad: I'm confirming the flag is set properly and rebootstrapping15:31
voidspacewith a better log level15:31
voidspacefrobware: I've assigned 1498982 to myself15:31
voidspacefrobware: I think that's a critical regression15:31
dooferladvoidspace: all-machines.log doesn't have "failed configuring a static IP for container "0/lxc/0": cannot allocate addresses: instId not supported" in it?15:32
voidspacefrobware: I still need my unit address bug completed too though15:32
frobwarevoidspace, thanks; yep agreed. the other one I just raised may not happen if I remember to add some subnets to my space15:32
voidspacefrobware: we really should have that fixed in 1.25 final though15:32
voidspacefrobware: panics are bad!!15:32
voidspacedooferlad: I've blown away the environment and am trying again15:32
frobwarevoidspace, yep agreed to unit address bug. which is why I was asking ...15:33
voidspacefrobware: just waiting on a review from fwereade15:33
voidspacefrobware: so working on the one dooferlad reported in the meantime15:33
voidspacefrobware: dooferlad: I know the cause of the bug - just not sure of the best fix15:33
voidspacefrobware: dooferlad: implementing ec2 support for instance Id filtering of subnets may be the path of least resistance15:34
fwereadevoidspace, frobware: only just started looking; think I'll take you up on that "focus on the txn" thing15:34
voidspacegoing to look at how the code used to look first15:34
voidspacefwereade: sure, I realise you're a slightly busy man!15:34
voidspacefwereade: I would get dimiter to look at it if he was here15:34
voidspacefwereade: the substantial change is the transaction is completely different - and it's now done on address setting not on preferred address fetching15:35
voidspacefwereade: the rest of the changes are just logical consequences of those changes15:35
voidspacebut it still amounts to effectively a complete rewrite of the original PR :-)15:35
voidspacefwereade: the race condition tests fail if you comment out the assert - which makes me believe they are both good tests and that the assert works...15:37
voidspaceof course I may well be deluded on both counts...15:38
fwereadevoidspace, no, I think it's good15:41
fwereadevoidspace, reviewed the state changes, just one naming quibble15:41
voidspacefwereade: thanks, looking15:41
mupBug #1499426 opened: deploying a service to a space which has no subnets causes the agent to panic <network> <juju-core:New> <https://launchpad.net/bugs/1499426>15:42
voidspacefwereade: hah, that did occur to me15:42
voidspacefwereade: but I thought getSetPreferredAddressOps was just silly...15:42
voidspacesetPreferredAddressOps it is15:42
fwereadevoidspace, I think of <verbPhrase>Ops as being conventional15:43
voidspacecool, thanks15:43
natefinchjw4: you around?15:44
natefinchfwereade: btw, that idPrefixWatcher is surprisingly action-specific: https://github.com/juju/juju/blob/master/state/watcher.go#L217315:46
jw4natefinch: yeah, but otp15:47
natefinchjw4: no worries... lunch just arrived, back in a bit15:47
jw4natefinch: I believe the idPrefixWatcher is a 'base' type that the action specific code uses?15:48
voidspaceif you bootstrap a dev version of juju the toolsversionchecker spams your log with errors15:58
fwereadenatefinch, ha, I'd missed that bit16:04
fwereadenatefinch, at first glance it looks as though it could be parameterised?16:04
voidspacedooferlad: ok, the error I see (at INFO level!) is the same one you do "machine-0: 2015-09-24 15:56:55 INFO juju.provisioner lxc-broker.go:114 not allocating static IP for container "0/lxc/0": cannot allocate addresses: no interfaces available"16:07
voidspacethis is on master16:07
voidspacelatest master I think16:07
voidspaceso the error you reported as coming from an earlier revision16:07
voidspacedooferlad: I'm going to switch to getting the unit address stuff merged and ported16:08
voidspacedooferlad: then I'll come back to this16:08
jw4natefinch, fwereade: crap, it's in mergeIds too16:09
jw4I wonder if that conversion could happen later, when consuming those id's instead16:09
jw4although... actionNotificationId just passes the original back in harmlessly if the id isn't an actionId16:10
jw4maybe the name of the function just needs to change to make it less confusing16:11
jw4I'd be happy to make a quick PR if that seems like an acceptable approach16:12
alexisbcherylj, ping16:16
alexisbwwitzel3, ping16:18
natefinchjw4, fwereade: it definitely looks like it could be pretty easily converted to be more generic.16:19
natefinchjw4: don't change the name... I'm going to change the name and see if I can make those conversions injected rather than hard coded.16:19
cheryljalexisb: what's up16:19
alexisbheya cherylj critical bug on 1.24 came up in the interlock call16:19
alexisbdo you have a time to have a look?16:19
cheryljalexisb: sure, what's the bug #?16:20
mupBug #1499356: all units have false hook errors after reboot <sts> <juju-core:Triaged> <https://launchpad.net/bugs/1499356>16:20
dooferladvoidspace: Just stopping for the day, sorry for missing your message 10 mins ago. I was running from the 1.5 branch with the bug I reported if that helps.16:22
natefinchbiab, gonna run home from the office.16:24
natefinchbbiab that is16:24
=== meetingology` is now known as meetingology
jw4natefinch: I have (what I think is) a better idea... I'll change the filterFn in the idPrefixWatcher to return a modified if necessary id when running the filter16:24
jw4that way we can inject the action specific modifier in the action specific constructor call16:24
natefinchjw4: ok, that's cool16:24
jw4kk.. I'll make a quick PR and you can decide if you like it :)16:25
natefinchjw4: cool :)16:25
natefinchback in like 45 mins.16:25
natefinchjw4: btw I think I have most of the changes needed to rework the idprefixwatcher into a generic collection watcher18:45
jw4natefinch: okay - I'll push up my changes anyway and you can pick and choose at least.  I think the actions stuff is more tightly coupled than I thought at first18:46
jw4just running the final tests18:47
jw4(and setting up reviewboard again)18:47
natefinchjw4: doesn't look too too bad if you just factor out the actionNotificationIdToActionId into a generic "id conversion" function that gets inserted... but I may have missed something18:47
jw4natefinch: that's essentially what I'm doing18:48
jw4I just did a bit of refactoring and cleanup there too for the tests, etc.18:48
jw4natefinch: http://reviews.vapour.ws/r/2749/  do with it as you wish18:54
mupBug #1499499 opened: juju-deployer reports that config specifies num units for subordinate when it doesn't <juju-deployer> <juju-core:New> <https://launchpad.net/bugs/1499499>19:09
mupBug #1499501 opened: com_juju_juju_testing.InitCommand / nil pointer dereference <ci> <intermittent-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1499501>19:09
mupBug #1499499 changed: juju-deployer reports that config specifies num units for subordinate when it doesn't <juju-deployer> <juju-core:New> <https://launchpad.net/bugs/1499499>19:12
mupBug #1499501 changed: com_juju_juju_testing.InitCommand / nil pointer dereference <ci> <intermittent-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1499501>19:12
natefinchjw4: I know dave had said the var _ foo = thingies should be in tests... but, why?19:17
mupBug #1499499 opened: juju-deployer reports that config specifies num units for subordinate when it doesn't <juju-deployer> <juju-core:New> <https://launchpad.net/bugs/1499499>19:24
mupBug #1499501 opened: com_juju_juju_testing.InitCommand / nil pointer dereference <ci> <intermittent-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1499501>19:24
mupBug #1499499 changed: juju-deployer reports that config specifies num units for subordinate when it doesn't <juju-deployer> <juju-deployer:New> <https://launchpad.net/bugs/1499499>20:39
jw4natefinch: I forget the exact rationale, but I remember that being raised as an issue before.  I guess we don't want the interface type assertions in production code.20:40
mupBug #1499499 opened: juju-deployer reports that config specifies num units for subordinate when it doesn't <juju-deployer> <juju-deployer:New> <https://launchpad.net/bugs/1499499>20:43
mupBug #1499499 changed: juju-deployer reports that config specifies num units for subordinate when it doesn't <juju-deployer> <juju-deployer:New> <https://launchpad.net/bugs/1499499>20:46
mupBug #1347322 changed: juju ssh results in a panic: runtime error <panic> <ppc64el> <juju-core:Fix Released> <juju-core (Ubuntu):Fix Released> <https://launchpad.net/bugs/1347322>21:10
mupBug #1347322 opened: juju ssh results in a panic: runtime error <panic> <ppc64el> <juju-core:Fix Released> <juju-core (Ubuntu):Fix Released> <https://launchpad.net/bugs/1347322>21:19
mupBug #1347322 changed: juju ssh results in a panic: runtime error <panic> <ppc64el> <juju-core:Fix Released> <juju-core (Ubuntu):Fix Released> <https://launchpad.net/bugs/1347322>21:31
alexisbthumper-afk, ping21:33
=== thumper-afk is now known as thumper
perrito666well it would seem that asus intends to make really hard for me to buy a replacement power brick for my laptop23:02
perrito666none of you lives near an asus retailer by any chance ?23:02
mupBug #1489142 changed: cpu-power constraint conflicts with with instance-type when trying to launch a t2.medium <constraints> <juju-core:Fix Released by cox-katherine-e>23:04
mup<juju-core 1.24:Fix Released by cox-katherine-e> <juju-core 1.25:Fix Released by cox-katherine-e> <https://launchpad.net/bugs/1489142>23:04
mupBug #1490603 changed: TestSubnets fails <ci> <intermittent-failure> <test-failure> <juju-core:Fix Released by dooferlad> <juju-core 1.25:Fix Released by dooferlad> <https://launchpad.net/bugs/1490603>23:04
mupBug #1493444 changed: juju upgrade from 1.24-beta2 to 1.24.5 broken <status> <upgrade-juju> <juju-core:Fix Released by hduran-8> <juju-core 1.24:Fix Released by hduran-8> <juju-core 1.25:Fix Released by hduran-8> <https://launchpad.net/bugs/1493444>23:04
mupBug #1491398 changed: RebootSuite test failures on windows <ci> <regression> <test-failure> <windows> <juju-core:Fix Released> <https://launchpad.net/bugs/1491398>23:10
perrito666thumper: after experimenting a bit I found out that the flags are not available in cmd/jujud/bootstrap for some reason23:12
* thumper thinks23:13
perrito666thumper: featureflags.All is an empty array23:13
thumperyeah... I know why23:13
thumperperrito666: quick hangout?23:14
perrito666sure let me dig my headphones23:14
thumperperrito666: https://plus.google.com/hangouts/_/canonical.com/boostrap-sucks?authuser=123:14
perrito666meh, google put me on hold to enter the call wtf23:15
perrito666I am in23:16
perrito666you are not23:16
mupBug #1491398 opened: RebootSuite test failures on windows <ci> <regression> <test-failure> <windows> <juju-core:Fix Released> <https://launchpad.net/bugs/1491398>23:22
mupBug #1491398 changed: RebootSuite test failures on windows <ci> <regression> <test-failure> <windows> <juju-core:Fix Released> <https://launchpad.net/bugs/1491398>23:25

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