veeberswallyworld: fyi my initial test shows that the latest log forward changes has *fixed* the cpu/loop issue (wrt to logforwarding and what I saw previously)00:02
wallyworldveebers: yay, ty00:02
=== natefinch-afk is now known as natefinch
axwwallyworld: http://reviews.vapour.ws/r/5236/00:44
wallyworldaxw: lgtm, ta00:48
mupBug #1602895 opened: log forwarding sends all messages on enabling <2.0> <juju-core:Triaged> <https://launchpad.net/bugs/1602895>00:49
redirThis http://reviews.vapour.ws/r/5153/ is still longing for a shipit00:51
axwthumper: probably not going to have time to review your pubsub stuff today, will try to get to it tomorrow if nobody else does in the mean time01:20
thumperaxw: that's fine, it isn't urgent01:20
axwwallyworld: log forwarder test panicking: http://juju-ci.vapour.ws:8080/job/github-merge-juju/8407/artifact/artifacts/trusty-out.log/*view*/01:26
wallyworlddamn, i wonder why use of dying channel didn't prevent that01:27
natefinchman, I really wish we'd stop using maps of name to struct everywhere... especially when the struct doesn't even contain the name :/01:41
thumpernatefinch: like where?02:29
natefinchthumper: almost all the new cloud & credential stuff.  github.com/juju/juju/cloud.Cloud doesn't even have a Name field :/02:30
natefinchthumper: cloud.Credential has no Name field.02:31
thumperwell, we know why02:31
thumperwe could trivially add a Name in there with things like `yaml:"-"`02:32
thumperwhich means don't serialize this value02:32
thumperso the output stays clean02:32
thumperand we could add them in when parsing02:32
thumperjust a thought02:32
natefinchthumper: the fact that our internal data structures are being dictated by serialization formats is a bad thing02:33
thumperit is a thing02:33
natefinchhmm... bootstrap sometimes letting you use the provider name rather than the cloud name is sort of annoying02:39
natefinchand by annoying, I mean confusing02:40
natefinchjuju bootstrap foo lxd works, juju bootstrap foo ec2 does not.02:41
natefinchoops, heh... uh... wallyworld... bootstrapping lxd requires --upload-tools02:53
wallyworldnatefinch: i miss the point?02:55
wallyworldalso, lxd is a cloud name as well as a provider name02:55
natefinchwallyworld: just that I was only doing interactive if the user specified no other flags... but then you can't do interactive with lxd, because you need to specify --upload-tools02:55
wallyworldwhat happens if you don't?02:56
natefinchthis wonderful error: ERROR failed to bootstrap model: cannot start bootstrap instance: tools info mismatch ({2.0-alpha1-xenial-amd64  b67c1484745bd58e7fac6ad672a7f6e45042ebef7a1e0e995f3f0f3c2baa7d33 18556414}, {2.0-alpha2-xenial-amd64  ceb165a45206eddadc06a7c986b44a3f76195c71a317d0c87810727c71bcc0f8 18073871})02:56
wallyworldthat's a bug then02:56
wallyworldupload-tools should not be required02:56
wallyworldmaybe the streams data is wrong02:57
natefinchhmm... I was under the impression that unless you were running a released version of the client, you always had to use upload-tools... but maybe that was only true if you needed the dev jujud02:58
natefinchI've just always used upload-tools02:59
wallyworldok, so from dev yes, you need upload tools02:59
wallyworldbut not for lxd in general02:59
wallyworldthre same applies for other clouds02:59
natefinchwell right, and in this case, I don't care what binary the jujud uses02:59
wallyworldi'd have to check the rules - but the client and agent versions generally need to match03:00
natefinchthat's probably what I'm hitting, yeah.  I guess that's ok.  It makes it a PITA to test though :)03:02
wallyworldyes it does03:06
wallyworldi just hack the juju version03:06
natefinchwell, the problem is that the code is checking for a command line that is just "juju bootstrap" and what I need it to also accept it "juju bootstrap --upload-tools" ... now the question is, do we want that to trigger interactive mode in production, or only as a hack for development?03:07
natefinch...and this is why I'd prefer to just have a flag for requesting interactive mode :D03:08
wallyworldinteractive mode is for when there are not enoug positional args03:20
wallyworldaxw: a small one http://reviews.vapour.ws/r/5237/03:22
natefinchwallyworld: should I go into interactive mode even if they specify flags, then?03:23
wallyworldwhen we talked yesterday, it was about missing positional args i think03:24
natefinchwallyworld: ahh, ok, I misunderstood the spec, then.03:24
wallyworldthe spec was/is unclear03:24
wallyworldi'm just giving my interpretation03:24
wallyworldi think it makes sense03:24
wallyworldalthugh to start with, we could just limit interactive to no args or fags03:25
wallyworldperhaps it's better to start out conseratively03:25
wallyworldno args or flags03:25
wallyworldbut i can see that allowing --upload-tools and still doing interactive for no positional args would be desirable for dev03:28
natefinchI hate that juju help constraints doesn't work anymore03:30
wallyworldoh yeah, i wonder what happened03:30
natefincha ton of the "help topics" were stripped out.  I don't know why03:31
natefinchalso juju help placement... gone03:32
natefinch$ juju help topics03:33
natefinchbasics          Basic Help Summary03:33
natefinchcommands        Basic help for all commands03:33
natefinchglobal-options  Options common to all commands03:33
natefinchtopics          Topic list03:33
wallyworldnatefinch: i have to duck out, but how about interactive for juju "juju bootstrap", maybe special case --upload-tools if it makes it easier for dev?03:33
natefinchwallyworld: seems fine for now.  Hoestly, looking at the flags, there's almost no flags that would be a problem with interactive mode03:34
wallyworld--credential would be03:34
wallyworldas it doesn't make sense until you select a cloud03:34
wallyworldso i reckon start simple03:34
wallyworldthen we can get the basics done and iterate03:35
wallyworldaxw: i have to go to doctor, bbiab, if you review branch and i don't respond, i'm not ignoring you :-)03:37
veeberswallyworld: re: logfwd, what's the expected behaviour when forwarding isn't on at bootstrap but is toggled later on the track? Are backdated logs sent or just from the toggle point onwards sent?03:40
veebersI see it as an open question on that spec foc03:40
axwwallyworld: sorry I've had a very disrupted morning, looking now04:15
natefinchwallyworld: well, first pass, needs a bunch more tests, but you can bootstrap interactively if you already have credentials, at least. https://github.com/juju/juju/pull/579704:45
mupBug #1602935 opened: Juju 2.0 DB2 charm giving error while deployed using ZFS as storage backend   <juju-core:New> <https://launchpad.net/bugs/1602935>04:50
=== urulama|___ is now known as urulama
mupBug #1602952 opened: provider/azure: we should be checking "provisioningState" on entities before adding relationships <azure-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1602952>06:35
rogpeppejam: any chance you could take a look at http://reviews.vapour.ws/r/5166/ please? I'm just about to make some changes to that code and it would be much easier to work on the simpler version if you approve of it.07:32
axwrogpeppe wallyworld: http://reviews.vapour.ws/r/5232/ -- this is ready for review now, I think this one could do with both 2 sets of eyes on it07:53
axwfairly simple changes, but a lot of them07:53
rogpeppeaxw: is this what we've just been working on?07:54
axwrogpeppe: yes07:54
axwrogpeppe: it lacks migration at the moment, I'll work on that now07:54
rogpeppeaxw: ah, i'd say the PR description is a bit misleading then07:54
axwrogpeppe: bleh, I updated the commit message but not the description07:54
rogpeppeaxw: it's quite a bit more than "allow empty username"07:54
axwrogpeppe: updated, I hope that's a bit better07:55
rogpeppeaxw: s/rejiggered/rejigged/ ?07:56
rogpeppeaxw: otherwise, looks good07:57
axwrogpeppe: apparently rejigger is an americanism, I've been infected07:57
rogpeppeaxw: ha, and apparently "rejig" is a britishism07:58
rogpeppeaxw: so rejigger looks fine - i just hadn't seen it before07:59
axwrogpeppe wallyworld: one bit of ugliness this change exposes: when you logout, any memory of what your current model is wiped; then when you login you have to set your current model again08:00
rogpeppeaxw: that didn't happen before?08:00
axwrogpeppe: nope, we weren't ever wiping info from models.yaml on logout before. so you could logout as admin, login as bob, and admin's current-model will still be in models.yaml08:01
rogpeppeaxw: ah, of course, because "current-account" was separate08:01
axwit won't be *used*, but it'll be there08:01
axwthen if you logout and log back in, you'll be back on the same08:01
wallyworldhmm, that may be ok perhaps? if there's no current model, we prompt right?08:01
rogpeppeaxw: hmm, why are we wiping info from models.yaml now?08:01
axwrogpeppe: because now models.yaml is entirely linked to the logged in user08:02
axwwallyworld: we tell the user what to do ("Please use "juju models" ... and "juju switch")08:02
wallyworldaxw: maybe if there's just the one model we should switch automatically08:03
rogpeppeaxw: perhaps the current model info should include both username and model name08:03
rogpeppeaxw: otherwise there's no way to be switched to a model that's under a different username, right?08:03
axwrogpeppe: that'll be part of the model name, when I update/land my other change: i.e. current-model will have the format "modeol-owner/model"08:04
rogpeppeaxw: ah, in which case the problem you mention above won't happen, right?08:05
rogpeppeaxw: because models.yaml won't be linked to the logged in user08:05
axwrogpeppe: I guess, if we want to say that current-model doesn't change between users08:06
axwrogpeppe: that seems a bit odd to me though08:06
rogpeppeaxw: i think it's better than wiping it08:06
axwmaybe it's ok08:06
axwyeah, probably08:06
axwalright, I'll just take out the code that wipes models.yaml for now then08:06
rogpeppeaxw: i think that it would be surprising if i couldn't log out, then log back in to the same model08:06
rogpeppeaxw: 'cos logged in user is almost entirely orthogonal to what model's currently being used.08:07
wallyworldrogpeppe: what happens if i log back in and new user can't access model?08:09
rogpeppewallyworld: then you'll get permission denied08:09
rogpeppewallyworld: seems better than just forgetting it always08:10
wallyworldseems reasonable i think08:10
wallyworldaxw: changes look ok to me, if rogpeppe is happy that it solves his problem and allows beta12 this week to fit their requirements08:11
rogpeppewallyworld: it doesn't solve the problem in itself, but it lays the groundwork for solving it08:11
frobwaredooferlad, voidspace, babbageclunk: PTAL @  http://reviews.vapour.ws/r/5235/ and http://reviews.vapour.ws/r/5234/08:12
rogpeppewallyworld: and it seems like a good change in general08:12
axwrogpeppe: well you can craft a file, like you could before. there are more changes due of course tho08:12
wallyworldrogpeppe: agreed, sorry i just meant that it unblocks you08:12
rogpeppeaxw: have you tried crafting a file with these changes in place?08:13
rogpeppeaxw: i'm not sure if it'll work08:13
axwrogpeppe: yes, it does. I don't have an idm to test with, but I verified that it tried to connect without a user/pass08:14
rogpeppeaxw: you do have an idm to test with08:14
rogpeppeaxw: identity-url: https://api.jujucharms.com/identity08:14
axwokey dokey08:15
voidspacefrobware: can take a look08:19
voidspacefrobware: I still need a full review on http://reviews.vapour.ws/r/5162/ :-p08:19
voidspacefrobware: in the first one, was prefix already unused by all those methods?08:21
voidspacelooks like it08:21
frobwarevoidspace: yes - was tidying up08:21
voidspacefrobware: cool08:21
voidspacethat first one is nice and easy08:22
voidspacefrobware: LGTM08:22
frobwarevoidspace: will look at your PR after standup08:23
voidspaceI'm looking at your second one08:23
voidspacefrobware: I wish we could encapsulate all this in a general purpose library08:25
voidspacefrobware: it's extremely precious knowledge08:25
frobwarevoidspace: yes, it has got to that stage now. It's quite different from the original sed script we started with.08:25
voidspacefrobware: second one LGTM as well - modulo the comment from babbageclunk08:26
frobwarevoidspace: thanks08:26
jamrogpeppe: looking08:28
rogpeppejam: thanks a lot08:28
jamrogpeppe: so does it still try the first one and then with a delay try the rest?08:30
rogpeppejam: it still tries all the addresses08:30
rogpeppejam: it just doesn't fall back to the bootstrap config (provider-specific) connection08:31
jamsure, but I thought the parallel try was the thing that did it, but that got removed if I'm reading the diff correctly.08:31
rogpeppejam: no, there are two levels of parallel tries08:31
rogpeppejam: the API connection code also does it08:31
rogpeppejam: the Try in the top level connection was entirely for the bootstrap config fallback08:32
frobwarebabbageclunk: sync?08:33
babbageclunkfrobware: oh, torry08:33
jamah good08:43
urulamawallyworld: could you give your +1 on http://reviews.vapour.ws/r/5232/ if it's ok? or if not, to fix it before beta12?08:44
axwwallyworld: nearly forgot about this one https://github.com/juju/romulus/pull/5208:47
jamrogpeppe: lgtm08:57
rogpeppejam: thanks!08:58
axwrogpeppe: I've added migration code to my PR, and dropped the code that was wiping models.yaml. should be good to go once it's stamped09:14
rogpeppeaxw: ah, i'll take another look09:14
rogpeppeaxw: added a couple more review comments09:22
axwrogpeppe: I think adding a test is a waste of time. I've manually tested it, and the code will be deleted as soon as the beta is out (which is imminent)09:23
rogpeppeaxw: fair enough, just a thought09:24
rogpeppeaxw: as long as you've actually run the code :)09:24
axwrogpeppe: thanks. yeah I did, it was broken the first two times :p09:25
rogpeppeaxw: BTW ignore my first comment (sorry, can't work out how to reply on reviewboard) - i hadn't realised the lines moved between types.09:26
axwrogpeppe: no worries - it's not super clear. thanks09:26
axwrogpeppe: I'm going to look at temporarily disabling the romulus dependency to break the cycle09:26
rogpeppeaxw: what do you mean by "disabling the dependency" ?09:26
axwrogpeppe: well, just stop importing the commands actually09:27
rogpeppeaxw: the "push temporary branch" thing works pretty well actually09:27
rogpeppeaxw: wait until you've got a LGTM on both romulus and the juju-core branch before doing it though09:28
rogpeppeaxw: and means you don't need to change the code at all09:28
axwrogpeppe: how does one push a temporary branch? don't I need to be able to write to master?09:29
rogpeppeaxw: you'll need the capability to make new branches in romulus09:30
rogpeppeaxw: you can ask ashipika1 to do it if you can't09:30
axwrogpeppe: which I don't have. I think I'll have to come back later, I think ashipika1 has gone back offline09:31
axwneed a review first anyway09:31
ashipika1axw: who is offline?09:31
axwashipika1: or not :) I just saw you're offline on canonical09:32
ashipika1axw: ah, who know.. i have a probabilistic internet connection..09:32
=== ashipika1 is now known as ashipika
axwnot even there, my IRC client is telling lies09:32
ashipikaaxw: you need a feature branch?09:33
axwashipika: yes please09:33
ashipikaaxw: pick a name, please :)09:33
axwashipika: modelcmd-no-account09:34
ashipikaaxw: done09:34
ashipikaaxw: enjoy :)09:35
axwashipika: ta09:35
axwashipika: I'm not going to be able to push to that though am I? can you please push my change over there.09:36
ashipikaaxw: https://github.com/juju/romulus/pull/53  ?09:40
axwashipika: yes, but the lander's not going to like it because juju/juju's API changed09:40
ashipikaaxw: shall i (ab)use the green button?09:41
axwashipika: ah, if you have that then yes please09:41
ashipikaaxw: done :)09:41
axwashipika: thanks09:41
rogpeppejam: do you think that https://github.com/juju/juju/pull/5719 can land even though it doesn't fix one of the blocking critical bugs?10:45
jamrogpeppe: I would check with Cheryl about that more than myself. If they are trying to stabilize this is more likely to cause a regression than others10:49
rogpeppejam: fair enough. FWIW it does fix at least one bug I've seen recently, just not any of the critical blockers.10:56
rogpeppejam: and if it doesn't land, getting branches that depend on it landed for beta12 might be hard.10:58
frobwarevoidspace: still owe you your review - sidetracked...11:05
rogpeppetrivial dependency update anyone (stops juju-core depending on an external feature branch)? https://github.com/juju/juju/pull/579811:51
frobwarebabbageclunk: could you take another look over http://reviews.vapour.ws/r/5235/11:54
babbageclunkfrobware: LGTM11:57
frobwarerogpeppe: just the one question, see RB11:59
mupBug #1603060 opened: upgrade-charm arguments don't support tilde expansion <juju-core:New> <https://launchpad.net/bugs/1603060>12:00
rogpeppefrobware: thanks12:07
rogpeppefrobware: i just replied12:07
rogpeppefrobware: it seems that it was a left-over dep12:07
rogpeppefrobware: unless you can find somewhere where that package is used12:08
frobwarerogpeppe: Was just (trying to) being diligent. Wanted to ensure that it was not accidental.12:08
rogpeppefrobware: yeah, it made me think again too12:09
frobwaredooferlad: one for you - https://c9.io/blog/great-news/12:10
frobwaredooferlad: you'll get bugs faster with prime! :)12:11
dooferladfrobware: I need coffee, but I would also like to talk through our current LXD bugs. Can you join a hangout in ~5 minutes?12:39
frobwaredooferlad: yep13:09
dooferladfrobware: team hangout?13:12
frobwaredooferlad: http://reviews.vapour.ws/r/5040/13:34
frobwaredooferlad: https://bugs.launchpad.net/juju-core/+bug/156680113:46
mupBug #1566801: LXD containers /etc/network/interfaces as generated by Juju  gets overwritten by LXD container start <cdo-qa-blocker> <landscape> <network> <juju-core:In Progress by frobware> <https://launchpad.net/bugs/1566801>13:46
frobwaredooferlad: https://bugs.launchpad.net/juju-core/+bug/160054613:47
mupBug #1600546: lxd subnet setup by juju will interfere with openstack instance traffic <network> <sts> <juju-core:Triaged> <nova-compute (Juju Charms Collection):New> <https://launchpad.net/bugs/1600546>13:47
alexisb__dooferlad, sorry, I have a conflict14:05
dooferladfrobware: not in a meeting if you want to talk again.14:12
frobwaredooferlad: need to resolve my conflict on my other PR first14:12
dooferladfrobware: sounds good14:13
mupBug #1559299 opened: cannot obtain provisioning script <bootstrap> <ci> <manual-provider> <regression> <xenial> <juju-core:Triaged> <juju-core 1.25:Fix Committed by anastasia-macmood> <juju-core api-call-retry:Fix Released by axwalk> <https://launchpad.net/bugs/1559299>14:18
rogpeppeanyone got an idea what the failure is here, and whether it has anything to do with the branch being landed? http://juju-ci.vapour.ws:8080/job/github-merge-juju/8414/console14:19
rogpeppemgz, sinzui: ^14:22
rogpeppei've tried again in hope that it's just a sporadic infrastructure failure14:22
mgzrogpeppe: looking14:22
rogpeppemgz: t14:22
rogpeppemgz: ta, even14:22
mgzrogpeppe: see trusy-err.log14:24
mgzrogpeppe: juju/api_test.go:132: undefined: noBootstrapConfig14:24
rogpeppewhere can i see that file?14:24
mgzrogpeppe: juju/api_test.go:132: too many arguments in call to newAPIConnectionFromNames14:24
mgzit's in the job artifacts14:25
mgzso, up one level from /console14:25
mgzat the top of the page14:25
mgzwe're still looking at making this output clearer than it is at present14:25
rogpeppemgz: ah, so you don't see test failures in the console output any more.ir14:26
mgzjust for now. they should be there again at some point.14:26
rogpeppewhat a great failure mode the IRC client has - if you're typing under heavy load, the input box goes into a state where text comes out randomly14:27
natefinchrogpeppe: I've seen that.  not sure if it's IRC or linux14:28
rogpeppenatefinch: i blame the app14:28
rogpeppemgz: it's in trusty-out.log, not trusty-err.log14:29
mgzrogpeppe: both have revelent things14:29
rogpeppemgz: oh yeah14:29
mgzsplitting them is actually a little confusing14:29
rogpeppemgz: it's really hard to see the pertinent data in trusty-err.log14:30
mupBug #1559299 changed: cannot obtain provisioning script <bootstrap> <ci> <manual-provider> <regression> <xenial> <juju-core:Triaged> <juju-core 1.25:Fix Committed by anastasia-macmood> <juju-core api-call-retry:Fix Released by axwalk> <https://launchpad.net/bugs/1559299>14:30
mgzrogpeppe: yep14:30
rogpeppemgz: can you monitor the build artifacts in real time like the console log?14:31
rogpeppemgz: i find it really useful to see a test error before all the tests have completed14:31
mgzrogpeppe: nope, that's another problem with parallel setup at present14:33
mupBug #1559299 opened: cannot obtain provisioning script <bootstrap> <ci> <manual-provider> <regression> <xenial> <juju-core:Triaged> <juju-core 1.25:Fix Committed by anastasia-macmood> <juju-core api-call-retry:Fix Released by axwalk> <https://launchpad.net/bugs/1559299>14:33
rogpeppemgz: is there any way to abort a jenkins run that's already started?14:34
rogpeppemgz: i know this one's gonna fail and i've fixed the issue already http://juju-ci.vapour.ws:8080/job/github-merge-juju/8417/14:34
mgzthere is, but the safest way is to ask me14:34
mgzokay, I can do that14:34
rogpeppemgz: please, martin, could you? :)14:34
rogpeppemgz: thanks14:34
babbageclunkSo, looking at bug #1602192 - why might systemctl be reporting that / didn't mount, when it's definitely available?14:36
mupBug #1602192: deploy 30 nodes on lxd, machines never leave pending <lxd> <juju-core:In Progress by 2-xtian> <https://launchpad.net/bugs/1602192>14:36
frobwarebabbageclunk, dooferlad, voidspace: can you take another look over http://reviews.vapour.ws/r/5234/. My other PR gave me a few conflict so had to rebase.14:46
mupBug #1600237 changed: ErroredUnit: 0 is in state cannot complete machine configuration: model configuration has no authorized-keys <deploy> <regression> <juju-core:Fix Released by axwalk> <https://launchpad.net/bugs/1600237>14:48
babbageclunkfrobware: lgtm14:50
rogpeppeanyone got any idea why a controller-only login doesn't send userinfo back in the response?14:56
rogpeppeapiserver/admin.go:150: if isUser && !serverOnlyLogin {14:56
voidspacefrobware: still need that review?15:13
frobwarebabbageclunk: actually, yes. just to be on the safe side as there were quite a few conflicts15:14
frobwarevoidspace: that ^ was supposed to go to you :)15:14
babbageclunkfrobware: I already did! :)15:14
frobwarebabbageclunk: the bridgescript.go is back - another push fixed that. was lost in my conflict resolution15:14
voidspacefrobware: ok15:15
frobwareoh, interesting. last 12-24 hours no $(juju add-machine lxd:0) on MAAS 1.9. Just tried MASS 2.0 and it worked. Coincidence? Or is 1.9 broken?15:39
mupBug #1603133 opened: Application Get api call doesn't return deployed series for multi-series charms <juju-core:New> <https://launchpad.net/bugs/1603133>15:42
voidspacefrobware: a couple of minor issues - but feel free to drop them if you don't think it's worth it15:46
babbageclunkfrobware: I guess I should really have opened an issue for that.15:46
frobwarevoidspace: const as in some constant list someplace?15:47
frobwarevoidspace: I was trying for locality; in some case we remove mtu, in other mtu+others.15:47
voidspacefrobware: I meant the same as you do for BRIDGE_OPTIONS15:48
voidspacefrobware: but if you don't feel it aids readability then feel free to drop it15:48
mupBug #1603133 changed: Application Get api call doesn't return deployed series for multi-series charms <juju-core:New> <https://launchpad.net/bugs/1603133>15:48
frobwarevoidspace: yep, but chatted with babbageclunk about this earlier. Didn't want the constant to be updated (in some future change) without really understanding the implication, hence the locality15:49
frobwarevoidspace: regarding performance, ... don't think it's an issue here15:50
frobwarevoidspace: this script will only ever run once15:50
voidspaceI just like to see the *right* data type used...15:50
voidspacebut I don't really care15:50
voidspaceit's not an optimisation it's a semantic correction15:50
frobwarevoidspace: and as long it is the same in python 2 & 3 I'm happy to change it15:50
voidspaceit's an unordered collection not a sequence15:50
voidspacefrobware: it is15:51
voidspacejust wrap a set constructor round it15:51
frobwarevoidspace: given the nature of this code anything I don't have to change make me delirious.15:51
voidspaceup to you, it's such a minor detail15:51
frobwarevoidspace: in a follow-up, sure. but have been testing it as-is so don't want to start over (though I cannot believe it would be an issue)15:52
frobwarevoidspace: but thanks anyway15:52
mupBug #1603133 opened: Application Get api call doesn't return deployed series for multi-series charms <juju-core:New> <https://launchpad.net/bugs/1603133>15:54
frobwarevoidspace: as in http://pastebin.ubuntu.com/19376777/ ?16:02
babbageclunkvoidspace, frobware: no, just write {'address', 'gateway'...}16:11
frobwarebabbageclunk: yep, done already. :)16:11
frobwarebabbageclunk: http://reviews.vapour.ws/r/5234/diff/4-6/16:12
babbageclunkfrobware: I've already clicked Ship It twice on that. I think it looks good!16:17
frobwarebabbageclunk: yep. thanks. was just confirming my SET LITERAL! :)16:18
babbageclunkfrobware: :)16:18
natefinchsuper easy review anyone? http://reviews.vapour.ws/r/5242/diff/#16:39
natefinchcherylj: ^ ?16:42
frobwarenatefinch: reviewed16:42
natefinchfrobware: thanks!16:42
natefinchalexisb__: I have a fix for hatch's bug, should I mark it critical and submit it, or... ?16:44
alexisb__yes please16:45
hatchooo critical :)16:46
hatchthanks natefinch16:46
natefinchhatch: welcome.16:49
natefinchhatch: luckily it was as easy as it looked :)16:49
hatchhaha great!16:50
perrito666we are spoiling hatch, he got 2 bugs in a week16:52
hatchmaybe I just work on important stuff ;)16:52
urulamano worries. he's spoiled already.16:53
perrito666hatch: nah, you are using some of these canadian superpowers of yours16:53
hatcha well placed "sorry" goes a long way16:54
perrito666nonsense, witchcraft I say16:55
urulamahatch: do keep an eye on that branch and test it with gui when it lands, please, just in case to catch the beta12 train with any last changes16:56
urulamai'm sure it'll be fine though16:56
hatchurulama: yep will do!16:56
=== urulama is now known as urulama|afk
cheryljnatefinch: just fyi - for bug 1603133 , you'll also need to give it the blocker tag to use the fixes-1603133$$17:08
mupBug #1603133: Application Get api call doesn't return deployed series for multi-series charms <juju-core:In Progress by natefinch> <https://launchpad.net/bugs/1603133>17:08
cheryljsigh, missed the first $$.  But whatevs17:09
hatchnatefinch: just wanted to point out that https://github.com/juju/juju/pull/5801 failed building17:18
cheryljhatch: retrying...17:24
mupBug #1578059 opened: Default route not coming up with juju 1.25.5 and bonding <canonical-bootstack> <juju-core:New> <MAAS:Incomplete> <MAAS 1.9:Incomplete> <https://launchpad.net/bugs/1578059>17:45
natefinchcherylj, hatch: thanks17:46
natefinchit's so much more nerve wracking watching jenkins now...17:52
natefinchthere's no play by play update, you just have to wait for the newspaper in the morning to tell you if your team won or lost17:53
perrito666natefinch: oh? what changed?17:56
natefinchperrito666: we're running multiple unit tests in parallel (well, in theory, I think right now, multiple == 1), and so they can't/don't update the jenkins console output with the test output.  It's only when the test run is done that the test output is linked to by the jenkins job page17:58
natefinchperrito666: so like, here, the tests are running, but you don't get real-time output of go test anymore: http://juju-ci.vapour.ws:8080/job/github-merge-juju/8421/console17:58
katcocherylj: maybe we should send out another email on this =|17:58
natefinchheh yeah, seems like everyone missed that little caveat at the end17:59
perrito666at least I did18:00
natefinchthis is like when they try to slip in some bad news behind an otherwise banal headline:18:02
natefinchPokemon go now accepts bitcoin!18:02
natefinchᵃᶫˢᵒ ᴼᵇᵃᵐᵃ ʰᵃˢ ᵈᵉᶜᶫᵃʳᵉᵈ ᵐᵃʳˢʰᵃᶫ ᶫᵃʷ18:02
perrito666pokemon accepting bitcoin is not banal, check your priorities dude18:05
natefinchTestResumeTransactionsFailure failed... yay18:05
natefinchwhelp. half hour of the test machine's time wasted.  Let's retry18:05
mupBug #1603176 opened: juju debug-log returns not logged-error <juju-core:New> <https://launchpad.net/bugs/1603176>18:30
mupBug #1603176 changed: juju debug-log returns not logged-error <juju-core:New> <https://launchpad.net/bugs/1603176>18:37
perrito666redir: ping?18:45
perrito666redir: was it remove user you where working on?18:45
mupBug #1603176 opened: juju debug-log returns not logged-error <juju-core:New> <https://launchpad.net/bugs/1603176>18:46
perrito666if so, did that ever land?18:46
redirperrito666: yup18:46
perrito666ah, ok, tx :) ill stop looking for it then :p18:47
redirperrito666: http://reviews.vapour.ws/r/5153/ I think the shipit button is broken or something;)18:47
redirI am trying to parse the latest review.18:48
redirthe client side bits are just waitin for it18:48
redirperrito666: ^^18:48
perrito666redir: oh I can't hear you, I am entering into a tunnerl, shh shh <toot><toot><toot>18:52
redirI think we're really close18:53
natefinchhatch: fix committed :)18:56
alexisb__thank you natefinch19:00
alexisb__redir, how are you feeling?19:01
hatchnatefinch: thanks!19:03
mupBug #1593850 changed: Deployment stuck in "Pending" for all containers <cdo-qa> <cdo-qa-blocker> <juju-core:Invalid> <https://launchpad.net/bugs/1593850>19:07
=== urulama|afk is now known as urulama|____
rediralexisb__: meh. Still drugged up. If I don't feel better by the weekend I'll go to the doc next week.20:18
mupBug #1603202 opened: kill-controller didn't do anything <juju-core:New> <https://launchpad.net/bugs/1603202>20:28
mupBug #1603202 changed: kill-controller didn't do anything <juju-core:New> <https://launchpad.net/bugs/1603202>20:37
rick_h_redir: did you catch my cold?20:38
mupBug #1603202 opened: kill-controller didn't do anything <juju-core:New> <https://launchpad.net/bugs/1603202>20:40
redirrick_h_: caught something somewhere.20:40
redirnose,ears,throat. Hopefully it'll be gone soon. I got a decent night sleep after a delayed flight. Another good night and I hope to report I'm on the upswing.20:42
mupBug #1603208 opened: (Windows unit test) ConfigSuite.TestConfigNonExistentPath failure in config_test.go <blocker> <ci> <unit-tests> <windows> <juju-core:Triaged by axwalk> <https://launchpad.net/bugs/1603208>20:58
mupBug #1603208 changed: (Windows unit test) ConfigSuite.TestConfigNonExistentPath failure in config_test.go <blocker> <ci> <unit-tests> <windows> <juju-core:Triaged by axwalk> <https://launchpad.net/bugs/1603208>21:01
mupBug #1603208 opened: (Windows unit test) ConfigSuite.TestConfigNonExistentPath failure in config_test.go <blocker> <ci> <unit-tests> <windows> <juju-core:Triaged by axwalk> <https://launchpad.net/bugs/1603208>21:10
mupBug #1602192 changed: deploy 30 nodes on lxd, machines never leave pending <lxd> <juju-core:Invalid by 2-xtian> <lxd (Ubuntu):New> <https://launchpad.net/bugs/1602192>21:28
mupBug #1602192 opened: deploy 30 nodes on lxd, machines never leave pending <lxd> <juju-core:Invalid by 2-xtian> <lxd (Ubuntu):New> <https://launchpad.net/bugs/1602192>21:31
mupBug #1602192 changed: deploy 30 nodes on lxd, machines never leave pending <lxd> <juju-core:Invalid by 2-xtian> <lxd (Ubuntu):New> <https://launchpad.net/bugs/1602192>21:40
mupBug #1603221 opened: Charms utilizing storage fail on LXD <juju-core:New> <https://launchpad.net/bugs/1603221>21:58
wallyworldrick_h_: we are still in release standup, running a bit late22:02
rick_h_wallyworld: ah ok ty for heads up22:02
wallyworldwe didn't abandon you :-)22:03
rick_h_...yet :p22:03
mupBug #1603228 opened: Juju does not support simplestreams for Azure-ARM <azure-provider> <simplestreams> <streams> <juju-core:Triaged> <https://launchpad.net/bugs/1603228>22:40
wallyworldniemeyer: hey, we want to use the latest and greatest mgo stuff in juju for beta12 (with the E1100 fix). but the fix is landed in a v2-unstable branch and so that now means a lot more than a godeps update to get it in. is there any chance you can merge the work to the v2 branch?23:10

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