anastasiamacaxw: menn0:thumper:wallyworld: an awesome, small review plz :D http://reviews.vapour.ws/r/5523/00:22
thumperalexisb_: ping00:22
wallyworldotp with reed can look soon00:22
thumperalexisb_: we should have a quick word00:22
menn0anastasiamac: looking00:23
anastasiamacmenn0: \o/00:24
menn0anastasiamac: well that was easy. ship it00:25
anastasiamacmenn0: cmars: tyvm :) m loving to see this beta's bug count going down or fixes count going up - glass half full :D00:27
thumperdog walk time00:46
=== thumper is now known as thumper-dogwalk
mupBug #1471770 changed: TestPrunes fails occasionally still <ci> <intermittent-failure> <test-failure> <juju:Triaged by menno.smits> <https://launchpad.net/bugs/1471770>00:50
mupBug #1580501 changed: cloudimg-base-url parameters not in Juju2 anymore <4010> <cpe-sa> <orangebox> <sts> <juju:Triaged> <https://launchpad.net/bugs/1580501>00:50
axwanastasiamac: I think you might've broken something: ERROR failed to bootstrap model: model "controller" of type manual does not support instances running on "amd64"01:10
axw(I'm looking into it)01:11
anastasiamacaxw: well, the only thing i can think of is that manual constraints validator does not have arches, and if there are no images for it, then nothing will be merged...01:11
axwanastasiamac: yeah, same thought01:12
anastasiamacaxw: i think I'll need to put arches in in there01:12
axwanastasiamac: yup01:12
anastasiamack. i'll do it now :)01:12
axwanastasiamac: I can probably fix it in my branch01:12
anastasiamacaxw: ooh even better ;)01:12
axwshould be a pretty small change01:12
anastasiamacaxw: i wonder if other providers will need to have similar thing.. i think  manual slipped through finger because maybe it never had arches vocab defined..?01:13
axwanastasiamac: yeah, it doesn't01:13
anastasiamacaxw: \o/ tyvm. let me know if there is something i can do to assist01:14
axwwallyworld: have you noticed that "model-config" says FROM=model for logging-config and resource-tags in a fresh model?01:32
wallyworldaxw: loggin-config i'd expect because juju itself sets the value via the api. resource-tags i'd need to look at, but i suspect the issue is the schema coeecsion to a map from a string01:33
wallyworldbah, string to map i mean01:34
axwwallyworld: yeah, almost certainly. I was thinking we should just set the default logging-config though?01:34
axwto the same as what the agent runs01:34
axwand configure the client differently if needed01:35
wallyworldaxw: it starts out as one thing and juju sets to another (debug->info)01:35
wallyworldor something like that01:35
wallyworldbut yeah, maybe we could do better, i recall at the time it made sense how it is01:36
axwwallyworld: *shrug* it seems odd to me that OOTB the config says it's not default01:36
wallyworldagreed. i can't recall the specifics off hand, but juju messes with it01:37
wallyworldwe can clean up next week01:37
axwanastasiamac: would you please review https://github.com/juju/juju/pull/6083/commits/32fdee6ef69e1355480ed9dbd208ca69c97fdd0f01:42
anastasiamacaxw: looks awesome :) did u get a chance to test live too?01:45
axwanastasiamac: yup, bootstraps fine after this change01:45
anastasiamacaxw: \o/ LGTM for this commit :D01:45
axwanastasiamac: ta01:45
=== thumper-dogwalk is now known as thumper
mupBug #1449210 changed: cloudsigma index file has no data for cloud <bootstrap> <cloudsigma-provider> <simplestreams> <tech-debt> <juju:Triaged> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1449210>02:09
mupBug #1616197 changed: juju restore-backup error <20160826> <backup-restore> <juju:Triaged> <https://launchpad.net/bugs/1616197>02:09
mupBug #1616298 changed: DebugMetricsCommandSuite.TearDownTest fails due to "no reachable servers." <intermittent-failure> <mongodb> <unit-tests> <juju:Triaged> <https://launchpad.net/bugs/1616298>02:09
natefinchis canonical IRC down for anyone else?02:12
anastasiamacnatefinch: yes02:13
mikenJust back now02:13
natefinchoh good, then I haven't been fired yet.02:13
anastasiamacmiken: not for me... still down \o/02:13
anastasiamacnatefinch: unless we've all been :)02:13
mikenOh - I'm connecting from an internal IP address, and it just reconnected to irc.c.c 2mins ago.02:14
wallyworldthumper: you'll need to resubmit your race fix pr i think, after adding "Build failed:" comment to trick the bot02:25
thumperwallyworld: ack02:25
thumperaxw: got some time to talk manual providers?02:27
axwthumper: sure02:31
thumperaxw: https://hangouts.google.com/hangouts/_/canonical.com/manual?authuser=002:31
* anastasiamac about to lose electricity - going afk for lunch and fun02:42
natefinchthumper: you guys talking about that bug I was looking at?02:43
anastasiamacnatefinch: this one? https://bugs.launchpad.net/juju-core/1.25/+bug/161088002:45
mupBug #1610880: Downloading container templates fails in manual environment <juju-core 1.25:Triaged by natefinch> <https://launchpad.net/bugs/1610880>02:45
natefinchanastasiamac: yeah02:45
natefinchanastasiamac: was going to ask you if you had any thoughts about that one02:45
anastasiamacnatefinch: looks like the fix needs to go into 1.25 not master02:46
anastasiamacnatefinch: no thoughts whatsoever - hence, m happy to go with advice from wallyworld to mark it as Invalid. I do wish there was a bit more explanations as to why it is Invalid...02:46
natefinchanastasiamac: well, the customer who is experiencing it is on 1.25, yeah. I don't know if it happens in 2.0, honestly02:47
wallyworldit has to be invalid as it's lxc only02:47
anastasiamacnatefinch: k :) do u have enough context to fix?02:47
natefinchoh yeah, dug02:47
wallyworld2.0 uses a totlly different mechanism02:47
natefinchit's not invalid for 1.2502:47
natefinchbut it is invalid for 2.002:47
wallyworldall it did was remove the targetted juju project02:48
wallyworldleft it targetted to juju-core02:48
mupBug #1610880 changed: Downloading container templates fails in manual environment <juju-core 1.25:Triaged by natefinch> <https://launchpad.net/bugs/1610880>02:48
wallyworldyou can tell it's only 1.25 from reading the logs02:48
natefinchyes, of course.  I hadn't really thought that part through :)02:49
anastasiamaci've removed juju-core and left for 1.2502:50
natefinchI added a note as to why it's not applicable to 2.0 :)02:50
mwenningHi, is there a way to tear down a model from the gui?02:50
anastasiamacgenerally if the bug is in 1.25, we also keep it to be fixed in 2.002:50
redirwallyworld: updates in http://reviews.vapour.ws/r/5510/02:50
anastasiamachowever, in this case, lxc is not in 2.0; so bug is invalid02:50
mwenningfrom command line I can go 'juju destroy-model blah'02:50
anastasiamacnatefinch: thnx :D02:50
wallyworldanastasiamac: correct02:50
anastasiamacwallyworld: m glad that u r agreeing \o/02:51
wallyworldthat it is 1.25 only? yes :-)02:51
axwthumper: it's possible that the "should be terminated" is coming from the pkill issued by DestroyController, and the SIGABRT stack trace is due to the killall run by the CI script02:52
anastasiamacwallyworld: and to a new world order, no? :D02:52
thumperaxw: hmm... I'll poke around02:52
axwthumper: so maybe it's just a case of the agent not shutting down fast enough02:52
wallyworldthat too, peace in the middle east and all that02:52
thumperaxw: actually... you may well be right02:54
thumperperhaps we need to make the destroy controller method on the manual provider wait until the process has been removed02:55
thumperaxw: I think this is the most likely case, and what I'll try for first02:56
axwthumper: maybe, could be that the agent is wedged though? we wouldn't normally care, because the controller machine gets destroyed in cloud environments02:56
thumperthe agent will hang around for a while to answer current api calls02:56
thumperbut no, don't think it is fully wedged.02:56
thumperbut I'll look too02:56
thumperstill think it is worthwhile waiting02:57
axwthumper: hmmk. seems reasonable to wait, yeah02:57
wallyworldredir: really close, got a fix it then ship it, let me know if anything is unclear03:06
redirwallyworld: k. tc03:12
redirtx even03:12
thumperwallyworld: hmm...03:14
wallyworldthings that make you go03:14
thumperwallyworld: trying to bootstrap a manual provider in lxd03:14
thumperERROR failed to bootstrap model: model "controller" of type manual does not support instances running on "amd64"03:15
wallyworldthumper: damn, that's fallut from anatasia's changes for fixing simplestreams issues, you running from tip?03:15
wallyworldok, will need to be fixed03:16
thumpertrying to look at the manual provider leaving stuff behind03:16
thumperbut can't bootstrap03:16
thumperI don't mind fixing if I can be told what needs fixing03:16
wallyworldyou can comment out the error03:16
wallyworldit's a bit complicated, image metadata been reworked, so different rules to figure out what can be bootstrapped03:17
wallyworldcomment out the error return03:17
wallyworldie don't do the check - that will get you going so you can do your fix03:17
thumperwhere is that?03:18
wallyworlddon't commit that change of course03:19
thumperwallyworld: that'll be the s390x manual bootstrap bug too03:20
wallyworldah, yes, could be03:20
wallyworldi'll talk to her when she's back online03:21
redirSo Posgres 9.6 tl;dr notes: parallel query scans, joins, and aggregates, inceremental vacuum freeze, sycronous replication with  multiple standbys, 10 will start a new version scheme (thing firefox/chrome)03:24
redirother than that mostly lots of talk about the uber paper.03:24
thumperredir: oh?03:25
rediruber: PostgreSQL -> Some schemaless object store thing on MySQL03:26
redirAppearntly theis has caused some hubbbub https://eng.uber.com/mysql-migration/03:26
redirthumper: live from the East Bay Postgres meetup at Pandora...03:27
redirTime to go be social at the pub, getting kicked soon.03:29
redirwallyworld: http://reviews.vapour.ws/r/5530/ when you have a chance later. I haven't yet updated what we talked about earlier.03:39
redirwallyworld: also ignore the bits from the other PR,this is stacked on that so it has those issues too.03:40
redirlater juju-dev03:40
thumperaxw: in my local lxd testing, it took two to three seconds from the time kill-controller had exited to the time the jujud agent stopped running03:41
axwthumper: sounds about right. in the CI failure it's still running 10 minutes later...03:43
thumper10 minutes?03:44
thumperI thought it was much sooner than tha03:44
* thumper double checks03:44
axwthumper: terminationworker says to terminate at 3:41, then the SIGABRT stack trace comes at about 3:5003:44
axw3:51 actually, I guess the CI script is waiting 10 minutes03:44
wallyworldanastasiamac: did you see there's fallout with the arch / image stuff and manual provider with lxd?03:45
anastasiamacwallyworld: the one that axw and i discussed and he has fixed (and i lgtm-ed) on his branch?03:46
axwwallyworld: I've got a fix for manual in my branch, can't land because master is blocked03:46
wallyworldaxw: i'd say make it a blocker and use $$fixes$$03:46
anastasiamacaxw: i think u can land ur branch03:46
axwwallyworld: is there a bug #?03:46
anastasiamacaxw: if u do not have a bug, jfdi03:46
wallyworldanastasiamac: thanks, didn't see there's a fix, thumper ran into it before03:46
thumperaxw: no... wasn't 10 minutes03:46
thumperwas almost immediate03:47
axwthumper: http://paste.ubuntu.com/23087267/03:48
axwfrom http://reports.vapour.ws/releases/4301/job/manual-deploy-precise-amd64/attempt/401803:49
thumperon attempt 4017 it was more immediate03:49
thumperaxw: that timing doesn't match the log outputs at all from 401803:51
thumperkill was here: 02:34:0503:51
axwthumper: I think the logs are appended to03:51
axwthumper: I'm probably looking at something old03:51
thumperthat test log output is now in local time03:51
thumperbut still03:52
axwthumper: I was looking from the top of the log, it looks like there's multiple test runs in the same log file03:52
axwsearching from the back, I concur that it's immediate03:52
thumperok... good :)03:53
axwthumper: though there *is* a very slow one at the top of the log, so it's not consistent03:54
thumperone problem at a time :)03:55
axwwallyworld: in your lxd PR, there's another target var lower down. I didn't realise that it exited early if the alias exists - maybe the check is still needed? does CopyImage return immediately if the image is already there?04:09
wallyworldaxw: in my testing, i deleted all lxd images. bootstrap the first time downloaded the image (slowly, with progress shown). then another bootstrap did not04:10
wallyworldand lxc image list shows the one image04:11
axwwallyworld: but that might be because there's still another call to GetAlias04:11
wallyworldthe instance started immediately though04:11
wallyworldso it's using whatever it cached the first time04:12
wallyworldi can't see any obvious difference in behaviour04:12
axwwallyworld: no, I'm just saying there's still another call to GetAlias that looks like it should be removed. but I'm not sure of the impact.04:12
wallyworldoh, i miss understood you. i saw that call too but didn't follow what it did so left it04:13
anastasiamaci've seen a few cpu/mem spike related bugs... if i were a memory leak in juju, where would i be? :D04:25
thumperaxw, menn0: http://reviews.vapour.ws/r/5532/05:06
axwthumper: LGTM, thanks05:10
menn0thumper: double ship it :)05:24
wallyworldaxw: i've got a few very small reviews up if you get a chance later. one is the lxd one which seems ok to me given it behaves as expected when testing05:29
axwwallyworld: sure, just finishing up QA for my add-model changes05:30
wallyworldno worries05:30
axwwallyworld: add-model changes: http://reviews.vapour.ws/r/5534/05:36
axwwallyworld: I'm QAing your lxd branch, and bootstrap is fetching images that I have again. possibly due to that code removal05:42
wallyworldhmmm, it didn't fetch mine again05:42
wallyworldbut i started from a clean slate05:42
wallyworldwhat are your aliases?05:42
wallyworldubuntu-xenial etc?05:42
axwwallyworld: yep05:43
axwI have ubuntu-xenial05:43
wallyworldhmmm, ok, i'll bootstrap again and see what it does05:43
wallyworldnfi why it doesn't work for you05:43
axwwallyworld: yep, I put the code back in and it doesn't do it now05:43
axwwallyworld: possibly once it has the image again, it wouldn't copy again05:44
wallyworldyeah, that's what i was thinking05:44
wallyworldthere might me some implicit alias or something05:44
wallyworldwhich i think is ok behaviour - so long as it only fetches once. stephane was adament we should be doing it this way or else auto update would not work05:45
axwwallyworld: it's probably fine, just doing one last test to satisfy myself05:50
wallyworldsounds good, best to be sure05:50
wallyworldi'm testing again too05:50
wallyworldbut download is sloooooooooow05:50
axwwallyworld: so, I think the issue is that the local alias I had did not match the image that was in the source05:59
axwwallyworld: so it replaced it05:59
wallyworldyeah, whereas before maybe we were setting the alias name05:59
axwwallyworld: if you were to put that GetAlias code back in, people could continue using their existing images... but I guess they wouldn't auto-update05:59
wallyworldthat's my understanding05:59
wallyworldand we want auto update05:59
axwwallyworld: ok. seems fine, maybe just add a release note that it will force an image refresh on everyone?06:00
wallyworldaxw: in the add-model / cloud branch - i've just srted looking - do we reject add-model cloud where the controller doesn't support the cloud asked for?06:00
axwwallyworld: it will complain that "foo" is not a cloud or a region06:01
axwwallyworld: because you can't add clouds to a controller, the only cloud it'll find is the one that was bootstrapped06:01
axwwallyworld: I did test that actually, just didn't add in the QA steps06:01
axwwill do that now06:01
wallyworldta, that would be good as i was wondering06:01
axwwallyworld: updated steps under LXD06:02
wallyworldgreat ty06:02
wallyworldaxw: and you can +1 the lxd pr?06:02
axwwallyworld: sorry yes06:03
wallyworldnot sure if i should land before beta06:03
wallyworldmight be good to get auto update fixed06:04
wallyworldaxw: "is neither a cloud nor a region". i don't like that message because aws is a cloud. it's just not supported by the current controller. so people will get confused by the message i think?06:06
axwwallyworld: well, it's not a cloud so far as the controller is concerned06:07
axwwallyworld: I agree it's a sucky message06:07
axwwallyworld: I guess we could look in the client's list of clouds first?06:07
wallyworldcould we rephrase to say that this controller doesn't support models on cloud "aws", only clouds "lxd" are supported06:07
wallyworldyeah, look at client clouds, and if it is a valid cloud name, be smart about the message06:08
wallyworld"... are supported by this controller"06:08
wallyworldor something06:08
axwwallyworld: we don't have an API to list clouds yet. I suppose I could add it06:09
wallyworldaxw: that's one of the things martin asked for06:09
wallyworldso it won't go to waste06:09
wallyworldand we have the cloud facade06:09
axwwallyworld: yeah, was trying to keep this minimal. shouldn't take too long tho06:09
wallyworldbut the message sucks :-)06:10
wallyworldaxw: gotta duck out to do school pickup, but one last question - on the apiserver side where an unsupported cloud is passed in - it returns an annotated not found error but i think we can d better with the error message there also06:22
wallyworld"such and such cloud is not supported, try one of these instead" type thing06:22
axwwallyworld: where's that?06:22
axwwallyworld: "getting cloud definition" ?06:22
wallyworlddidn;t matter before but now that we are allowing people to specify the cloud themselves06:23
wallyworldneed to tighten it up IMO06:23
axwwallyworld: isn't that redundant if we have the client query the supported clouds?06:23
wallyworldthat's in add-model, what abot via the api06:24
wallyworldpython juju client, controller proxy etc06:24
axwhmm I guess so06:25
wallyworldauto pilot, conjure up etc - they all use the api06:25
wallyworldand in conjure up, someone could easily specify an unsupported cloud06:25
wallyworldgotta run, bbiab, got to update release notes at some point06:26
frobwareaxw: ping - larry shared his vsphere setup which i think you've used recently. Did you have any problems bootstrapping? For me it doesn't complete using beta15.06:45
axwfrobware: hey. I didn't get past authentication. I think the issue I was seeing was that the client downloads the cloud image and then uploads it to vsphere. I'm quite far away, so that was so slow it timed out06:46
axwfrobware: sorry I mean, it authenticated but didn't get any further (functionally) than that06:46
frobwareaxw: I get as far as... https://pastebin.canonical.com/163942/06:47
frobwareaxw: lines 75 & 76 repeat until timeout06:48
frobwareaxw: I have never bootstrapped on vsphere before so could be operator error too06:48
axwfrobware: ah, well you got further than me :p   sorry, I don't know what's up with it. I've never used vsphere before that one time06:48
axwand I was just verifying that my auth changes were good06:48
frobwareaxw: the only addition I made to the cloud definition was adding to clouds.yaml:  vsphere: regions: dc0 {}06:51
frobwareaxw: which was largely done based on a bug comment I think you made... somewhere... :)06:51
axwfrobware: if the issue was with clouds.yaml, it would have failed much earlier06:52
axwI don't think it's user error06:52
axwmore likely the provider or vsphere is broken06:52
frobwareaxw: which it did. could not bootstrap because 'datacenter' was undef06:53
frobwareaxw: I'll try going back to beta8 as that's where the bug was reported, but largely to see if bootstrap has regressed since.06:53
axwfrobware: oh I see what you mean. yeah, larry's original clouds.yaml was broken06:53
axwfrobware: this is what I've got: https://pastebin.canonical.com/163945/06:54
frobwareaxw: you mean it was broken and needed the regions bit?06:54
axwfrobware: well, and he was trying to use non-standard keys. that one I linked is in the valid format06:55
frobwareaxw: this is what I'm currently using: https://pastebin.canonical.com/163946/06:56
axwfrobware: yep that's fine06:56
axwauth-types is unnecessary but won't cause a problem06:56
axwwallyworld: how's this? https://pastebin.canonical.com/163947/06:57
wallyworldaxw: yay, much nicer, thank you06:58
axwwallyworld: cool. just gotta write some tests, and improve error messages on the server side now06:58
wallyworldaxw: you could potentially make the add-model cmd dumb and not do any checks and allow them all to be done on the server side07:01
wallyworldsince you need to make an api call to list clouds anyway07:02
wallyworldyou could avoid that call07:02
wallyworldand just make the create model call07:02
axwwallyworld: thought about it, but that makes the cloud/region unstructured which I'm not too keen on07:02
wallyworldyou could still split on /07:02
axwwallyworld: this way we may also support auto-upload of cloud definition, if we want to do that07:02
axwwallyworld: sure, but you still don't know if it's cloud or region if there is no /07:03
wallyworldok, ignore me, just thinking out loud07:03
thumperwallyworld: hey07:17
thumperwallyworld: still hanging around?07:17
wallyworldthumper: what's up?07:19
thumperpretty sure bug 1615839 is that bit you got me to comment out07:19
mupBug #1615839: Manual-provider claims s390x is not supported <ci> <manual-provider> <regression> <s390x> <juju:In Progress by thumper> <https://launchpad.net/bugs/1615839>07:19
thumperis anastasiamac on that?07:19
thumperor shall I take a look?07:20
thumpermight take me longer07:20
wallyworldthumper: i think axw landed a driveby07:20
wallyworldot has one in train07:20
thumperbut I could muddle through it07:20
wallyworldall good, we broke it, we fix it07:20
wallyworldthanks for offering07:20
thumperwho shall I assign the card and bug to?07:20
wallyworldcheck that axw is/has done it, otherwise to anastasia07:21
thumperaxw: have you fixed it?07:21
rediris hudson back?07:22
wallyworldredir: late for you, go to bed :-)07:24
rediryeah just got home and eating something, then bed07:24
redirwho knew postgres folks were such talkers:)07:25
axwthumper: sorry was on school run, it should be fixed by my latest merge, have marked Fixed Committed07:35
thumperaxw: ok, cool07:35
thumperwhat was the fix by the way?07:35
axwwallyworld: updated my PR, PTAL07:57
wallyworldaxw: looks great, ty08:03
wallyworldaxw: when it lands, let urulama and mhilton know as they've started to need the Clouds() API and are assuming a return of []string whereas we are offering a map of cloud details08:05
axwwallyworld: sure08:06
axwwallyworld: gonna have to get a second review, this is >50008:07
axwI'll point martin at it, maybe he'll be willing :)08:07
wallyworldstupid rule08:07
anastasiamacwallyworld: well, the rule would not bite if the PR are manageable08:11
anastasiamac>500 is not manageable for any reviewer08:12
wallyworlddepends on the type of change08:12
anastasiamacof course u do08:12
wallyworldand who's reviewing08:12
wallyworldwe had a much larger limit in launchpad08:12
wallyworld500 is too small08:12
anastasiamacno, usually only dev knows what they wrote for PR >50008:12
wallyworldnot just dev08:13
wallyworldi know what's in that pr and i didn;t write it08:13
anastasiamacu r very specail08:13
wallyworldaxw: off to make dinner, updated the pr, thanks for reviewing08:15
axwwallyworld: will look in a sec. I'm reviewing your show-user one now08:15
* frobware is back in ~1 hour08:17
mhiltonwallyworld, axw: what have you done to my API deisgn!08:27
wallyworldmhilton: we needed more than just the cloud names :-) you get the names as the map keys08:36
wallyworldand also you have allowable regions etc which are really useful for the gui08:37
mhiltonwallyworld: It's fine, I'm curous. We were getting the regions from the Cloud() endpoint. but doing it all in one go is probably better.08:38
wallyworldmhilton: yeah, we think so, one call to get all the info you need08:39
wallyworldrogpeppe1: thanks for review, did you just want to check my answer to you question in the review http://reviews.vapour.ws/r/5533/08:50
rogpeppe1wallyworld: i've just published a review of http://reviews.vapour.ws/r/5533/09:09
rogpeppe1wallyworld: weird, i didn't think i'd published anything until now...09:09
rogpeppe1wallyworld: i think you were maybe talking about axw's question09:10
wallyworldoh dear, i was09:10
rogpeppe1wallyworld: i was wondering about external user access too, although i forgot to mention it in my review09:10
wallyworldthis review isn't about any of that09:11
rogpeppe1wallyworld: i think if we left the access field out entirely, things would become more obvious09:11
wallyworldit's all already been done09:11
wallyworldthe access field is also pre existing so i don't realy want to move it09:11
wallyworldthis review is just about proerly looking up external user access09:11
rogpeppe1wallyworld: the problem is that it *looks* as if the access field tells you what access rights a given user has09:11
wallyworldit does09:12
rogpeppe1wallyworld: but actually it doesn't tell you that09:12
wallyworldit tell you what access that user has to the controller09:12
rogpeppe1wallyworld: because if access has been granted to everyone, everyone will have at least those rights09:12
rogpeppe1wallyworld: and when we implement general group checking, that issue will become still worse09:13
wallyworldoh, i see what you're saying. yes right now it just tells you what that user has specifically been granted09:13
wallyworldgroups will require a whole lot of change09:13
rogpeppe1wallyworld: yup. i think that's misleading, and we'd be better off fixing things now.09:13
rogpeppe1wallyworld: i.e. remove the Access field09:13
rogpeppe1wallyworld: because that's the only problematic part09:13
rogpeppe1wallyworld: otherwise it's just about looking up information about a specific user09:13
wallyworldwhy can;t we look up the access transatively and just fill in the access bit09:14
wallyworldwe need to give the access value back to the caller09:14
rogpeppe1wallyworld: why does it need to be in the same API call?09:14
wallyworldwhy not? for distributed systems you aim to minimse the api calls09:15
wallyworldfewer bulk calls is the design goal09:15
rogpeppe1wallyworld: that's an optimisation - i generally prefer to start by being as clear as possible and optimise later09:15
wallyworldwe disgaree there, i remember this discussion when juju's api was first being designed09:16
rogpeppe1wallyworld: so how many bulk calls are actually being used as bulk calls now? :)09:16
axwmhilton: heh sorry :p  but yeah, one query lets us get all the stuff we want in one go, rather than getting names and then calling Cloud a bunch of times09:16
rogpeppe1wallyworld: POitRoAE... still!09:16
wallyworldi can't answer that - i don't know what api clients people have written09:16
rogpeppe1wallyworld: juju is the only api client for all the agent stuff09:17
wallyworldi can imagine landcape etc would use bulk calls09:17
wallyworldand the gui certainly *should*09:17
rogpeppe1wallyworld: and bulk calls are used approximately zero times09:17
wallyworldthen they're doing it wrong if that's the case09:18
rogpeppe1wallyworld: no. mostly you do only have one thing to do at a time09:18
rogpeppe1wallyworld: and this isn't HTTP09:18
wallyworldmore's the pity09:18
wallyworldit should be restful09:18
wallyworldbut that's another discussion09:18
rogpeppe1wallyworld: HTTP1 is bad because the calls are expensive and cannot return replies out of order09:19
rogpeppe1wallyworld: the RPC API doesn't have that limitation09:19
rogpeppe1wallyworld: the overhead of a call is small09:19
wallyworldsure, but HTTP1 is so last century09:19
rogpeppe1wallyworld: we still only use HTTP109:19
wallyworldwhy is that out of curiouslty?09:19
wallyworldbesides that Go is stuck in the 70s :-)09:20
rogpeppe1wallyworld: for all the bulk calls we have, making several calls concurrently is faster than actually using the bulk call as a bulk call09:20
rogpeppe1wallyworld: because we make our own http transport09:20
rogpeppe1wallyworld: otherwise we'd get HTTP2 out of the box09:20
wallyworldhmmm, i'd like to see the numbers. may be fast for some things, but chatty api calls are evil for distributed system09:21
wallyworldthat's why we should just stick to standards instead of rolling out own09:21
rogpeppe1wallyworld: tell that to google, amazon, heroku, etc etc09:21
rogpeppe1wallyworld: they all use RPC systems09:21
wallyworldi've seen way too many distributed system fall over due to inefficient apis09:21
rogpeppe1wallyworld: and none of them have a "bulk calls only" policy09:21
rogpeppe1wallyworld: HTTP APIs, right?09:21
rogpeppe1wallyworld: if a system is inefficient, optimise it09:22
rogpeppe1wallyworld: it's not a hard thing to do09:22
wallyworldeasier said than done once the apis are set09:22
rogpeppe1wallyworld: that's why we have versioning09:22
wallyworldyou can use a bulk call singularly but not the other way around09:22
wallyworldand versioning is horrible for us to try and us09:23
wallyworldeach time we rev a facade verison it introuces a world of hurt09:23
wallyworldanyway, i need to change the access look up to take account of the everyone group09:24
wallyworldregardless of the api design09:24
rogpeppe1wallyworld: you can make many singular calls concurrently09:24
rogpeppe1wallyworld: there really is very little overhead in doing so09:24
wallyworldat the cost of many network reosurces09:24
rogpeppe1wallyworld: no09:24
rogpeppe1wallyworld: at the cost of *some* extra bandwidth09:24
rogpeppe1wallyworld: but much less than you'd think09:24
frobwaredo we really have bandwidth issues?09:25
rogpeppe1frobware: not AFAIK09:25
wallyworldbandwidth is a finite resource09:25
rogpeppe1wallyworld: so are developer resources09:25
wallyworldtry living in australia09:25
wallyworldthe point being?09:26
wallyworldwhere there's latency, bulk calls are much better09:26
rogpeppe1wallyworld: the point being that we've expended 1000s of hours of extra effort making every call "bulk" and we never use that capability09:26
rogpeppe1wallyworld: actually no09:26
wallyworldwhat extra effort?09:26
wallyworldwe designed the api once09:27
wallyworldand we do use it? how do you know we dont't?09:27
wallyworldhave you audited every external juju api client?09:27
rogpeppe1wallyworld: because most of the entry points in the api package don't even expose the bulk functionality09:27
rogpeppe1wallyworld: i'm talking about the agent API here09:27
rogpeppe1wallyworld: because that's easily checked09:28
wallyworldthe juju api layer only exposes singular calls, but pythin juju client, conjure up, etc etc don't use that09:28
rogpeppe1wallyworld: testing and implementing a bulk API call is probably 5 times more effort than a single one09:29
wallyworldi don't agree with that09:29
wallyworldi don't find it any different09:30
rogpeppe1wallyworld: there are lots more edge cases to be tested09:30
rogpeppe1wallyworld: zero, one, many, all error, some errors, etc09:30
wallyworldthat is true, but once you get standard patterns in place, it falls out pretty easily09:30
rogpeppe1wallyworld: BTW when there's latency, concurrent calls are better because you can get replies out of order and start dealing with them sooner, rather than waiting for all replies at once09:31
wallyworldi wonder why there's such stark difference of opinion here09:31
rogpeppe1wallyworld: you mean you copy and paste09:31
wallyworldno, we have helper structs also09:31
wallyworldlike our errors09:31
rogpeppe1% find api apiserver -name '*.go' | xargs cat | wc09:32
rogpeppe1 125883  386115 383881409:32
rogpeppe1wallyworld: in a very few cases, you can have helper structs. but if you're returning actual results, you can't use 'em09:33
rogpeppe1wallyworld: and you still need to have all those test cases09:33
wallyworldnot hard though09:33
rogpeppe1wallyworld: it all adds up09:33
rogpeppe1wallyworld: our api code is *huge*09:33
rogpeppe1wallyworld: and it's mostly noise09:33
wallyworldGo code is mostly noise :-P09:34
wallyworldso much boilerplate and copy and paste09:34
rogpeppe1wallyworld: you're writing it wrong then09:34
wallyworlddue to not having generics etc etc09:34
wallyworldso all those sort functions are wrong09:34
wallyworlddifferent ones for int vs string etc09:34
rogpeppe1wallyworld: very little of what we're doing in the API could be made better with generics09:34
wallyworldno, i was making apoint about the fact that you critised our aoi for cut and paste when the language itself is just as bad :-)09:35
rogpeppe1wallyworld: i honestly don't see that much copy and paste in decent Go code09:35
wallyworldwe have so many cut and paste functions for "is this string in this slice"09:36
rogpeppe1wallyworld: even implementing sort only involves copying and pasting two lines09:36
wallyworldand each time i have to do it i die a little inside09:36
wallyworldno other language ive used makes you do that09:36
rogpeppe1wallyworld: i guess you've never used C then09:36
wallyworldnot for years09:37
wallyworldbbiab, SIGWIFE09:37
mupBug #1616832 opened: manual environment juju-db timeout <juju-core:New> <https://launchpad.net/bugs/1616832>09:55
* fwereade bbl10:57
frobwaredimitern: ping - I tried your patch but it didn't work for me.11:04
dimiternfrobware: oh, what was wrong?11:05
frobwaredimitern: just trying to repro again to ensure it's all true...11:05
dimiternfrobware: ok11:06
frobwaredimitern: but it was eseentially the same problem that ivoks ran into initially11:06
dimiternfrobware: DNS hostname (resolved) != PUBLIC ADDRESS in status?11:07
frobwaredimitern: double-checking. have too many pots on the go.11:09
mupBug #1616832 changed: manual environment juju-db timeout <juju:New> <juju-core 1.25:New> <https://launchpad.net/bugs/1616832>11:31
rogpeppe1juju server certs need unique serial numbers, it seems. this PR adds them. small PR, review appreciated :) https://github.com/juju/juju/pull/610011:55
rogpeppe1please could someone give this small PR a review? (i need review from someone in -core), as it's blocking us right now: http://reviews.vapour.ws/r/5538/12:14
rogpeppe1dimitern, frobware: ^12:18
frobwarerogpeppe1: looking12:18
rogpeppe1frobware: thanks12:18
frobwarerogpeppe1: can you please list some QA steps12:20
rogpeppe1frobware: ah, ok, sure12:20
rogpeppe1frobware: done12:21
frobwarerogpeppe1: without your change you cannot connect?12:22
rogpeppe1frobware: no, there's no externally visible behaviour change12:23
rogpeppe1frobware: except, i guess, that if you use a browser to connect, it can do so12:23
rogpeppe1frobware: hmm, maybe the QA steps could specify that i guess12:23
=== plars_ is now known as plars
frobwarerogpeppe1: right - I wanted to look at before and after12:24
rogpeppe1frobware: let me check how they've been doing it - it involves creating a new CA key, adding its cert to your browser, and making a websocket connection to the API12:24
rogpeppe1frobware: actually, even that won't quite check it. i think you need to do that with two controllers.12:25
rogpeppe1frobware: oh yes, the controllers need to be bootstrapped using the new CA key12:27
=== mup_ is now known as mup
fwereadefrobware, http://reviews.vapour.ws/r/5539/ is up if you have a moment :)12:42
fwereadeand now I'm going to have some lunch, ping me if you need me and I'll catch up when I'm back12:42
frobwarefwereade: ack12:43
sinzuianastasiamac: when you deleted the juju-core task, but left a 1.25 task on bug 1616832, you removed the bug from search. All bugs that affed to a project series must also affect the project.12:45
mupBug #1616832: manual environment juju-db timeout <juju:New> <juju-core:New> <juju-core 1.25:New> <https://launchpad.net/bugs/1616832>12:45
mupBug #1616832 opened: manual environment juju-db timeout <juju:New> <juju-core:New> <juju-core 1.25:New> <https://launchpad.net/bugs/1616832>12:49
rogpeppe1frobware: i replied to your question12:50
frobwarerogpeppe1: ok, will take a look. looking at the other review atm12:51
rogpeppe1frobware: as we're the ones affected, perhaps we should do the QA12:51
frobwarerogpeppe1: I think so.12:52
rogpeppe1frobware: ok, cool. in that case your LGTM would be much appreciated.12:52
frobwarerogpeppe1: I dropped another question on the review13:13
rogpeppe1frobware: i don't get which line 170 you're talking about13:16
rogpeppe1the only new(big.Int) we're now using is on cert.go:13313:17
rogpeppe1frobware: is that the one you're referring to?13:17
rogpeppe1frobware: otherwise i'm seeing cert_test.go:170 is expiry, err := time.Parse("2006-01-02 15:04:05.999999999 -0700 MST", "2012-11-28 15:53:57 +0100 CET")13:18
rogpeppe1frobware: and cert.go:170 is if !ok {13:18
frobwarerogpeppe1: ah, sorry. line 170 was in the old file.13:19
rogpeppe1frobware: so we're not using new(big.Int) there any more13:20
frobwarerogpeppe1: dropped13:20
rogpeppe1frobware: ok, ta13:20
babbageclunkdimitern, fwereade: Could you look at this? http://reviews.vapour.ws/r/5540/13:25
dimiternbabbageclunk: looking13:26
frobwarebabbageclunk: looking (I'm OCR)13:26
babbageclunkIt's the machine undertaker worker with tests. (Also I worked out how to get it onto RB, since the bot wasn't helping!)13:26
babbageclunkdimitern, frobware: Thanks!13:26
frobwarebabbageclunk: one quick question, why did the pattern of s.waitRemoved() & s.waitForRemovalMark() calls appear to now be the other way around?13:27
babbageclunkfrobware: I've changed the provisioner not to remove machines anymore, so the tests can't wait for the machine to be removed.13:28
babbageclunkfrobware: Instead they wait for it to be marked for removal.13:29
babbageclunkfrobware: I'm not sure if that was quite what you were asking.13:31
frobwarebabbageclunk: yes13:32
frobwarebabbageclunk: thx13:32
babbageclunkfrobware: cool cool. I saw something weird while testing manually, just seeing if I can reproduce it.13:33
babbageclunkfrobware, dimitern: MAAS was giving the error "node with this hostname already exists" if I tried to create containers on two hosts at the same time.13:34
frobwarebabbageclunk: but goes away if done in series?13:35
babbageclunkfrobware: That was what it seemed like - trying to reproduce it now.13:36
babbageclunkfrobware: (Most importantly, trying to reproduce it on upstream/master)13:36
katcodimitern: frobware: standup time14:01
frobwarekatco: omw14:02
babbageclunkfrobware: Hmm, can't reproduce it on master or my branch now.14:02
ram____Hi. I have a question. While selecting components from landscape UI for autopilot openstack deployment , can we give set external configuration parameters for a particular component?14:10
natefinchram____: you'd do better to ask in #juju14:16
katcofrobware: sorry, didn't mean to overlap14:21
frobwarekatco: not a problem14:21
ram____natefinch: Ok. tahnk you.14:21
babbageclunkmgz: ping?15:10
babbageclunkI'm trying to investigate this: https://bugs.launchpad.net/juju/+bug/160630815:11
mupBug #1606308: Restore cannot initiate replica set <backup-restore> <ci> <mongodb> <regression> <juju:Triaged by alexis-bruemmer> <https://launchpad.net/bugs/1606308>15:11
babbageclunkI can't really remember how to go about running the CI tests.15:12
mgzbabbageclunk: so following the links through to a recent failure gives you the rough outline15:13
mgzthis is a test we run on aws, so it's pretty easy15:13
mgzwant to do a ho or something quickly to go over?15:13
babbageclunkyeah, that would be brilliant15:14
mgzbabbageclunk: okay, I am in the meeting named core15:14
natefinchfwereade: I'm looking at this: https://bugs.launchpad.net/juju-core/+bug/148578415:28
mupBug #1485784: Error creating container juju-trusty-lxc-template; Failed to parse config <lxc> <oil> <juju-core:Fix Released by cherylj> <juju-core 1.25:Fix Released by cherylj> <https://launchpad.net/bugs/1485784>15:28
natefinchfwereade: actually, srory, wrong link, this one: https://bugs.launchpad.net/juju-core/1.25/+bug/161088015:29
mupBug #1610880: Downloading container templates fails in manual environment <juju-core 1.25:Triaged by natefinch> <https://launchpad.net/bugs/1610880>15:29
natefinchthough they're similar15:29
natefinchfwereade: we're running lxc-create and trying to download the lxc image from the server - lxc-create [-n juju-trusty-lxc-template -t ubuntu-cloud -f /var/lib/juju/containers/juju-trusty-lxc-template/lxc.conf -- --debug --userdata /var/lib/juju/containers/juju-trusty-lxc-template/cloud-init --hostid juju-trusty-lxc-template -r trusty -T
natefinchThat's getting a cert error15:30
natefinchI notice that I get a similar error if I just try to curl that URL15:31
frobwarebabbageclunk: sorry, been sidetracked. I wanted to try your changes15:32
fwereadenatefinch, I don't have any immediate insight I'm afraid :(15:33
natefinchfwereade: np15:33
babbageclunkfrobware: no worries15:39
babbageclunkmgz: oops, I guess firefox gave up? I think that's enough to go on with, thanks heaps!15:39
mgzbabbageclunk: yup, think it's pretty hung15:40
mgzbabbageclunk: no problems, yell if you need more15:40
babbageclunkmgz: I almost certainly will!15:40
babbageclunkfrobware: If there are some issues that you want me to look at in the meantime you can put up a partial review while you're testing?15:43
frobwarebabbageclunk: haven't got that far. :( still trying to get vsphere to boot whilst larry is about15:44
babbageclunkfrobware: ok, fair enough :)15:44
babbageclunkfrobware: I'm not blocked, so no stress15:45
ram____Hi. For testing purpose I developed a simple charm using the shell script  to modify the cinder configuration file for the post-deployment of OpenStack. cinder configuration modified. But I am saw some error in charm log. pasted information of my issuehttp://paste.openstack.org/show/563408/16:03
ram____Please anyone provide me some solution.16:04
babbageclunkmgz: I'm getting a "no such file or directory" when it tries to call euca-terminate-instances - where should I get that from?16:19
perrito666anyone that has knowledge of migrations on this time zone?16:20
babbageclunkmgz, oh looks like euca2ools16:20
mgzbabbageclunk: hm, that really should be part of the deps16:24
mgzbut it should also be switched to boto....16:24
alexisbperrito666, voidspace but I dont see him online16:30
katcoalexisb: he is travelling16:31
alexisbkatco, thanks16:31
alexisbkatco, there is a mail I need him to respond to as well16:31
alexisbI will loop you in for tracking purposes16:31
katcoalexisb: he mentioned he might check-in. if so, i'll let him know16:32
rogpeppe1natefinch: do you know how we've ended up with 5 packages under github.com/juju/juju/resource with no tests at all?17:12
rogpeppe1natefinch: it makes life a bit awkward when refactoring in that area17:13
natefinchrogpeppe1: yeah.17:14
natefinchrogpeppe1: I think the only one with any substantial amount of code is the resourceadapters directory17:15
natefinchrogpeppe1: I don't have a good answer for that.17:16
ram____Hi. I tried to deploy "cinder-xtremio " charm in our local Juju openstack environment like $juju deploy cinder-xtremio. I was facing errors. pasted error log : http://paste.openstack.org/show/563432/. Please anyone provide me some solution for this.17:22
ram____Hi. I want to develop a cinder-storagedriver  charm. And i want to integrate it with Ubuntu-autopilot . SO can I give input parameters like san IP, san user and san password from landscape autopilot UI. Otherwise everything we have to hardcode into the charm. And different users for the same storage array have different credentials.18:23
natefinchram____: you might get a better response if you send an email to the juju mailing list18:27
natefinchram____: most of us here work on the core code for juju itself, and we don't know much about the ubuntu autopilot code, or the openstack charms in general18:28
ram____natefinch : Ok. thank you18:30
=== mup_ is now known as mup
=== mup_ is now known as mup
natefinchtych0: you around?19:28
katcotvansteenburgh: hey, have you made any progress on bug 1616574 ? still stuck?20:02
mupBug #1616574: Can't deploy local charm via API <juju:Triaged> <https://launchpad.net/bugs/1616574>20:02
tvansteenburghkatco: i haven't made progress20:07
katcotvansteenburgh: ok; did you have a look at the go code?20:08
cmarsif i'm bootstrapping and I see "2.0-beta16-xenial-amd64.tar.gz", does that mean i'm downloading the agent from simplestreams?20:08
cmarssorry "Fetching agent 2.0-beta16-xenial-amd64.tar.gz" i mean20:08
natefinchcmars: should be, yeah20:09
cmarsnatefinch, is there a way to get juju to pick up a jujud binary i've already built?20:09
cmarsnatefinch, i can do --build-agent, but if i've already built it..20:09
katcocmars: it just has to be in your $PATH i believe. see wallyworld's email a week or so ago20:10
natefinchcmars: if you're bootstrapping with a built juju, it's supposed to automagically figure it out and do upload--tools20:10
cmarsi've got jujud in my path, but it's not getting picked up20:10
cmarsso open a bug?20:10
wallyworldit needs to be in the same dir as juju20:10
wallyworld$GOPATH/bin usually20:10
cmarsyeah, i think it was20:11
cmarsbut, i'll try again20:11
wallyworldand it needs to match juju exactly in terms of version20:11
wallyworld--show-log will have more info20:11
cmarswallyworld, ok, thanks!20:11
wallyworldit should all work, let me know if now and we can debug20:11
tvansteenburghkatco: i did, yes20:12
katcotvansteenburgh: i'm looking through and comparing the 2 now; did anything pop out?20:12
cmarsit's not critical, but it would shave a minute or two off our CI to not build twice20:12
katcotvansteenburgh: the logic i'm using is: if the juju binary can do this, there's no reason python-jujuclient shouldn't be able to as well. i.e. i don't think it's a fix on our end?20:13
katcotvansteenburgh: is there a flaw in that reasoning?20:13
tvansteenburghkatco: yes :)20:13
katcotvansteenburgh: haha20:13
katcowhat am i missing?20:13
tvansteenburghkatco: the logic i'm using is, this works with juju1 but not juju220:14
tvansteenburghkatco: maybe it works with juju2 but there's another step or something, i dunno20:15
katcotvansteenburgh: there have been many many breaking api changes between the 2 versions20:15
tvansteenburghkatco: no, that's not the problem20:15
katcotvansteenburgh: but that's my point: i'm going to help you figure out what's wrong, but i don't know why this is targeted against the juju project and not python-jujuclient?20:15
tvansteenburghkatco: here's the thing. customer comes and says "how do i deploy a local charm using the juju2 api". i can't fix python-jujuclient until i know the answer to that.20:17
tvansteenburghkatco: so far no one has been able to tell me how to do it20:17
tvansteenburghthat's what the bug is for20:17
katcotvansteenburgh: ok, well let's get this figured out. the go code i pointed you at is how we do it, so we just have to figure out what the difference is20:18
tvansteenburghkatco: is it possible that the local charm should be uploaded to the controller and not the model?20:33
tvansteenburghno, that didn't work either20:36
natefinchtvansteenburgh: if a customer came and asked how to deploy a local charm using the juju2 api, I'd say "don't"20:41
natefinchour API is not designed to be used directly by third parties.  It's too granular and requires too much knowledge of the internal workings of juju.20:42
katconatefinch: well, that's why we supply libs to wrap that, which is what tvansteenburgh is trying to fix20:42
cmarswallyworld, ah, i figured out how to force bootstrap to use jujud out of $PATH. i set the agent & image metadata url to localhost and streams to "nope"20:42
natefinchkatco: yes, I get that20:42
cmarswallyworld, that fails over to the "Preparing local Juju agent binary" case20:43
cmarswallyworld, do you think that's expected behavior?20:43
cmars(actually, i'm not sure i should have messed with image... i have no idea what i'm doing!)20:44
katcotvansteenburgh: i see your placement args are empty. placement.Scope must be the model UUID i think20:44
wallyworldcmars: it will only use a local juju if it can't find any binaries in streams. setting the url like that will cause that search to fail20:44
wallyworldcmars: we gave beta16 binaries now, i bet your master source code still says beta1620:45
katcowallyworld: cmars: maybe the issue is that your client is reporting beta1620:45
tvansteenburghkatco: thanks i'll try that20:45
cmarswallyworld, ah! i bet that's it20:45
katcocmars: it has to report higher than that20:45
cmarswallyworld, i think i'll keep it like this.. i want to test exactly what i've built20:45
cmarswallyworld, kind of a hacked-up --agent-binary feature20:45
wallyworldthat will happen 99.999% of the time20:45
wallyworldit's just we have an hour windows just after a release20:45
wallyworldwhere the source code is not yet updated to say beta+120:46
* wallyworld needs coffee20:46
anastasiamacsinzui: k. thnx20:59
perrito666wallyworld: awake again?21:00
tvansteenburghkatco: no luck with that http://pastebin.ubuntu.com/23090486/21:01
tvansteenburghkatco: if i call the CharmInfo with the charm-url i also get a "charm not found" error back21:04
tvansteenburghCharmInfo api i mean21:05
katcotvansteenburgh: here is the entire client-side call-chain serialized out, freshmen in cs101 failing miserably style: http://pastebin.ubuntu.com/23090503/21:05
katcotvansteenburgh: let me ponder your CharmInfo comment a moment21:06
katcotvansteenburgh: substitutions in that pastebin can be searched by triple "/" (e.g. ///)21:07
tvansteenburghkatco: cool, looking21:07
alexisbthumper, ping21:08
katcoheya thumper21:09
alexisbmorning thumper21:09
* thumper is munching on breakfast, been a busy morning21:09
thumperkids off to ski trip21:09
alexisbthumper, do you mind joining a HO?21:10
thumperI'll just be mute21:10
alexisbif you join now no need fo ryou to be on release call21:10
alexisbthumper, ^^^21:10
* redir lunches21:11
katcotvansteenburgh: it looks like environment.py::add_local_charm is missing schema & revision queryargs21:20
katcotvansteenburgh: L65-67 in pastebin21:21
tvansteenburghkatco: i noticed that but figured i'd get an error back if they were needed. i'll try adding them though21:22
* katco doesn't know, is just pedantically going through the diff21:22
tvansteenburghkatco: after uploading my charm, and getting a url back, a call to the Charms.List api does not list my charm21:23
tvansteenburghi'll try the extra args now21:23
katcotvansteenburgh: ok, so we're narrowing it down here at least ^.^21:23
katcotvansteenburgh: fyi i have a call in 7m which EOD me21:23
katcowhich will EOD me21:23
tvansteenburghkatco: ack21:24
tvansteenburghkatco: extra args didn't seem to make any difference21:25
katcotvansteenburgh: hm, can you verify that the lib's Charms.List call works at all? just so we know the scope of this problem?21:26
tvansteenburghkatco: yeah i have output from it21:26
tvansteenburghit just doesn't include the charm i uploaded21:27
tvansteenburghit does include other charms in the model thought21:27
katcotvansteenburgh: k... so it has to be something with add_local_charm_dir down right?21:27
tvansteenburghwell i get a charm-url back from that, as if the upload was successful21:27
tvansteenburghbut then when i list via the api, it's not there21:28
katcocan you manually verify it's in the environment? i.e. look in mongo?21:28
katcoor use juju bin?21:28
tvansteenburghkatco: can the juju cli list apps that haven't been deployed?21:29
katcotvansteenburgh: it depends on if they're just "pending" or uploaded by not placed... i don't know which adding a charm does =/21:30
katcotvansteenburgh: i would just look in mongo to be sure21:30
tvansteenburghkatco: never done that, are there instructions somewhere? :D21:31
katcotvansteenburgh: yeah sec21:31
katcotvansteenburgh: https://lists.ubuntu.com/archives/juju-dev/2016-July/005772.html21:33
* tvansteenburgh tries21:34
* tvansteenburgh waits for mongo client to install21:38
tvansteenburghkatco: http://pastebin.ubuntu.com/23090623/21:44
katcotvansteenburgh: http://pastebin.ubuntu.com/23090638/21:47
katcotvansteenburgh: try this version21:47
tvansteenburghkatco: same :(21:49
tvansteenburghis my mongo shell version ok?21:49
katcotvansteenburgh: oh, no... you need >= 3.221:49
katcotvansteenburgh: sorry, didn't catch that21:50
tvansteenburghkatco: ok i'm connected21:52
katcotvansteenburgh: `use juju`21:53
menn0thumper: target prechecks infrastructure: http://reviews.vapour.ws/r/5543/21:53
katcotvansteenburgh: `db.charms.find()`21:53
tvansteenburghkatco: i see my local ubuntu charms21:54
katcotvansteenburgh: the ones you've been uploading?21:54
thumpermenn0: looking21:54
tvansteenburghi'll pastebin one21:54
thumperveebers: can we hangout?21:55
tvansteenburghkatco: http://pastebin.ubuntu.com/23090657/21:55
tvansteenburghkatco: now i notice that model uuid is not the one i passed to Placement.Scope21:55
katcotvansteenburgh: ah. wortha  try21:56
tvansteenburghkatco: no luck21:57
veebersthumper: sure thing, what about?21:58
thumperveebers: running a ci test locally21:59
veebersthumper: sure, where you want to meet?21:59
thumperveebers: https://hangouts.google.com/hangouts/_/canonical.com/friday?v=1471633360&clid=9319256218B181C1&authuser=021:59
katcotvansteenburgh: ok, we'll have to pick this up tomorrow. at least we've narrowed the scope21:59
tvansteenburghkatco: sounds good, thanks22:00
katcotvansteenburgh: np22:00
cmarsis master blocked?22:05
alexisbaaah, anastasiamac we should remove blocking tags22:06
anastasiamacyes. i will now \o/22:06
anastasiamacalexisb: there are no blocking bugs i see22:07
menn0anastasiamac: https://bugs.launchpad.net/juju/+bugs?field.tag=blocker22:10
menn0anastasiamac: I see 4 blockers22:10
mupBug #1615986 changed: Agents failing, blocked by upgrade but no upgrade performed <canonical-is> <juju:Invalid> <juju-core:Invalid> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1615986>22:11
anastasiamacmenn0: looking. i'll remove.. nothing is blocking according to juju.fail :D22:11
menn0anyone know who runs juju.fail? I suspect it needs to be updated to look at "juju" instead of "juju-core" on launchpad22:11
katcomenn0: i think it's marcoceppi22:11
anastasiamacah... it's becasue juju fail may looks at launchpad juju-core not juju project22:11
anastasiamacsideeffect of the move :)22:11
menn0that's what I said :)22:12
* menn0 emails marcoceppi 22:12
cmarsthanks all22:16
tvansteenburghkatco: i see what's happening. the uploads are being tagged with the controller uuid instead of the default model uuid. i'm not sure how to fix it though22:19
marcoceppimenn0 katco I'll update it, and add a link to bugs23:10
menn0marcoceppi: thank you23:10
marcoceppiactually, there is a link, at the bottom of the page23:10
marcoceppithat says I made it23:10
menn0marcoceppi: the awesomeness of the rest of the page must have blinded us to that part ;-)23:14
marcoceppithe citools from QA has changed, I have to go patch the scripts23:14
marcoceppimenn0: this may seem odd, but apparently there are no blockers?23:15
alexisbanastasiamac, standup23:16
menn0marcoceppi: that's correct... there were an hour or so ago, but not now23:16
alexisbperrito666, standup23:16
marcoceppimenn0: ah, I see, we'll it's switched over now23:16
marcoceppimenn0: the next time you ahve a blocking bug double check to make sure it works23:17
menn0marcoceppi: will do!23:17
tvansteenburghkatco: i figured it out. bug updated with the details. TL;DR "I'm sorry"23:20

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