/srv/irclogs.ubuntu.com/2016/08/26/#juju-dev.txt

menn0thumper: poke regarding http://reviews.vapour.ws/r/5543/ :)00:19
thumpermenn0: sorry, got distracted01:08
menn0thumper: no worries01:08
thumpermenn0: do you recall how to get the engine as a dependency?01:25
menn0thumper: only vaguely01:25
* menn0 checks01:26
menn0thumper: is worker/dependency.SelfManifold what you want?01:29
thumperprobably01:29
thumperI'm halfway through your review01:29
thumperwallyworld: with you shortly, just want to finish this review01:29
menn0thumper: looks like it's currently only used in some tests01:29
wallyworldsure01:30
* wallyworld is doing a review too01:30
menn0thumper: regarding version.Number over the API, that's how it's done elsewhere and it's fine. version.Number has custom JSON marshalling defined which turns it into a string.01:38
thumpermenn0: if we are already doing it then fine01:43
thumperdrop em01:44
tych0natefinch: hi, i am now01:46
axwwallyworld: can you please take a look at http://reviews.vapour.ws/r/5534/diff/3-4/, made some changes in response to mhilton's review01:47
wallyworldsure01:48
natefinchtych0: hey.  I'm having difficulty figuring out this bug: https://bugs.launchpad.net/juju-core/1.25/+bug/161088001:56
mupBug #1610880: Downloading container templates fails in manual environment <juju-core 1.25:Triaged by natefinch> <https://launchpad.net/bugs/1610880>01:56
natefinchtych0: the crux seems to be that lcx-create is trying a wget for the image ... and for some reason on a manual juju environment it fails and on a normal juju environment it works01:57
natefinchtych0: I know this is only tangentially related to anything you've worked on, but I was wondering if you had any ideas01:58
thumperwhy is the lxd provider downloading a new ubuntu-xenial image?02:05
thumperdoes it auto update?02:05
natefinchnew as in - it already has one and it's getting another?02:06
natefinchand the answer is.. AFAIK, LXD maintains its own list of images, what it does with those is mysterious magic.  I don't *think* we tell it to auto-update, but I could be wrong.02:08
thumperlogging added, ci test running again, time to get food02:18
thumperugh02:29
thumperffs02:29
thumperrerunning02:29
natefinchoh interesting.... so, in a manual environment, we're not adding the cloud-local address for the machine to the cert02:38
menn0wallyworld: I like the new bootstrap output. looks much better02:44
menn0wallyworld: shouldn't these 2 things be the other way around though:02:45
menn0Installing curl, cpu-checker, bridge-utils, cloud-utils, tmux02:45
menn0Running apt-get update02:45
axwpjdc: do you have an env that's currently exhibiting CPU/mem spikes as in https://bugs.launchpad.net/juju/+bug/1587644? I'm after a CPU profile in addition to what's been provided already03:06
mupBug #1587644: jujud and mongo cpu/ram usage spike <canonical-bootstack> <canonical-is> <juju:Fix Released> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1587644>03:06
pjdcaxw: not right now. but if you can tell us how to capture what you'd like captured, i'll add it to our ticket03:07
axwpjdc: you should just use the same command as for the heap profile, but use /debug/pprof/profile instead of /debug/pprof/heap03:08
pjdcaxw: righto - will update the ticket03:08
axwpjdc: which is described here for 1.25: https://github.com/juju/juju/wiki/pprof-facility03:08
axwpjdc: thanks03:08
pjdcaxw: just testing it here; does this look right? https://pastebin.canonical.com/164042/plain/03:15
axwpjdc: hrm, nope, that doesn't look right. should be much bigger. odd, it worked for me just now03:18
axwpjdc: looks like the right command line invocation though ...03:18
pjdcthe single quote character seems pretty odd03:19
wallyworldmenn0: sorry, was at lunch. you could be right, i'll have to check03:31
anastasiamacthumper: since u r in the manul area, ci also seem to have observed long bootstrap (>45min)... if u have any thoughts on this would be awesome to have them in this bug03:38
anastasiamachttps://bugs.launchpad.net/juju/+bug/161713703:38
mupBug #1617137: Timing out fetching agent (xenial/s390x)  <bootstrap> <ci> <regression> <juju:Triaged> <https://launchpad.net/bugs/1617137>03:38
wallyworldanastasiamac: that's not related, that's due to closed network03:42
wallyworldcurtis needs to reimport the images03:42
anastasiamacwallyworld: if u can comment in the bug, m sure QA and veebers will apprecaite03:42
wallyworldanastasiamac: curits already knows - he and i disucssed03:43
wallyworldhe has more detial than i do03:43
wallyworldas to exactly what needs to be done03:43
wallyworldas he did it originally03:43
veeberswallyworld, anastasiamac ah ok, seems I missfiled that then. I'll get that fixed03:43
anastasiamacwallyworld: sure, veebers filed the bug and this info is useful for anyone who was not in on ur discussion :D03:43
anastasiamacawesome! tyvm :D03:43
wallyworldbut i don't have all the detail03:44
wallyworldi only know generalities, i'd rather get the person who knows to comment03:44
wallyworldsounds likes the QA folks need to talk to each other more :-)03:45
veebersanastasiamac, wallyworld: If we can keep the bug for now (maybe not marked critical) I've updated the rule/issue to indicate it's a ci infra issue and we'll get those in the know to comment/remove/etc. thebug03:45
wallyworldno worries03:45
wallyworldhaving a bug means it can be tracked03:45
anastasiamacveebers: feel free to adjust priority on it :D03:45
veebersanastasiamac: sweet, have done. also added affects ci with a (vague) comment about network03:49
anastasiamacveebers: wallyworld \o/03:49
wallyworldthe bug should be retargetted to CI, as curtis confirm it's not juju03:51
veeberswallyworld: it has been03:53
wallyworldawesome, tyvm03:53
veeberswallyworld: oh no wait, I didn't remove juju, just added juju-ci03:53
veebersperhaps I should have lied just now and said that I had removed juju too :-)03:54
wallyworldwe can add juju back if needed, but for now the best info is that it's a CI issue - "someone" needs to import LXD images03:54
menn0veebers: with the changes landed today, there a bunch more prechecks in place03:54
veeberswallyworld: removed now03:54
wallyworldso that LXD uses those importd instead of calling out to cloud-images03:54
wallyworld\o/03:54
veebersmenn0: oh neat :-) Does it break any assumptions the test makes currently?03:54
menn0veebers: the main one you'll be interested in is that it isn't possible to upgrade if the target controller tools version is less than the model tools version03:55
menn0veebers: no it shouldn't break the existing tests03:55
menn0veebers: the tests to ensure the source and target aren't controller are done too (mostly landed)03:56
menn0veebers: i'm implementing the prechecks to ensure that the source controller, model and target controller machines are healthy now03:56
veebersmenn0: nice. Might look at getting a test for between versions going next week03:58
menn0veebers: sounds good.03:58
menn0veebers: just keeping you informed :)03:58
veebersmenn0: :-)03:59
natefinchwallyworld: is it me, or does this seem dangerous? https://github.com/juju/juju/blob/master/worker/certupdater/certupdater.go#L119  We're updating the saved addresses before knowing if we've actually successfully updated the cert.04:16
wallyworldyeah, seems suboptimal04:17
natefinchwallyworld: I'm looking at this bug about lxc containers on manual provider, and it seems like we're not adding the cloud-local address to the cert for some reason04:18
wallyworldwe use c.addresses to short circuit any future updates, i guess if things fail, that means we'll never process those addresses again04:19
natefinchwallyworld: I don't think that's the actual problem04:19
natefinchwallyworld: it just looks suspicious04:19
wallyworldi can't recall enough about the code to know why cloud local addresses are not arriving at the cert updater04:20
wallyworldthey must be filtered out upstream somewhere04:20
wallyworldthe machine address setting code is a bit gnarly04:20
natefinchwallyworld: yeah... we call state.APIHostPorts() when the cert updater starts, and add any local-cloud addresses... on manual, it gets no addresses, on gce, it gets the correct local-cloud address04:21
wallyworldoh, manual04:21
wallyworldwe won't get any04:21
natefinchwhy not?04:22
wallyworldthe cloud local addresses come from the instance poller from memory04:22
wallyworldand there's no such thing as an instance poller for manual IIANM04:22
natefinchug04:22
wallyworldthis is a bit hand wavy04:22
wallyworldi could be wrong04:23
wallyworldbut generally the instance poller is a major source of our knoweledge of machine addresses04:23
natefinchyou're at least slightly wrong... I see juju.state address.go:137 setting API hostPorts: [[104.196.3.75:17070 10.142.0.2:17070 127.0.0.1:17070 [::1]:17070]] on manual04:23
wallyworldwith manual, we wil get machine local addresses04:23
wallyworldright, but it depends on how those are classified04:24
natefinchthat 10.142 address is what lxc-create is trying to wget the image from04:24
wallyworldby our address heuristics04:24
natefinchhmm04:24
wallyworldwe label addresses as machine local, cloud local, public etc04:24
wallyworldwhat is the machine foe which those host ports are being set above>04:25
wallyworld?04:25
wallyworlda controller or a worker machine?04:25
natefinchcontroller04:25
wallyworldanyways, 127.0.0.1 looks wrong04:25
wallyworldcause if that is handed out as a controller address, it can't work04:26
natefinchworks from that machine ;)04:26
wallyworldmight not be the same issue as your seeing, but looks wrong to me04:26
natefinchit gets set that way on my gce controller as well, so probably not the problem04:27
wallyworldso from memory, set addreses happens and we filter somehow and then hand out to cert updater, but i can't really recall exactly04:27
wallyworldmaybe the filtering takes care of localhost04:28
wallyworldaxw: i've updated http://reviews.vapour.ws/r/5533/ if you could PTAL, a bit of code was moved around05:33
axwokey dokey05:34
wallyworldaxw: added a fix and a test for the tranitive permission etc05:34
thumperwell, with menn0's help, debugging is progressing05:38
thumperit is in the proxy updater where it is trying to set the lxd proxies05:38
thumperit is just blocking forever05:38
thumperholding workers up05:38
thumperanyway05:38
thumpermore debugging for monday05:39
* thumper is done for now05:39
thumperlaters folks05:39
axwwallyworld: found an existing bug, but otherwise LGTM05:43
wallyworldta, looking05:44
wallyworldaxw: yeah, that was existing behaviour before I started this PR. it does seem wrong doesn't it05:46
wallyworldactually05:46
wallyworldit is as per the all users case above, but it makes more sense there05:47
wallyworldi'll change to errperm05:47
wallyworldaxw: ah, the existing client code will bail out with an error if *any* of the requested users results in an error05:59
axwwallyworld: :/05:59
wallyworldso that's why the server side was skipping over unpermitted users05:59
axwwallyworld: we should do that filtering on the client, not on the server06:00
wallyworldagreed06:00
wallyworldaxw: for now, how about i just modify the api caller to skip err perms06:01
wallyworldbut error for other things06:01
axwwallyworld: sounds OK I guess06:01
wallyworldor the other things is we could print the errors for tabular output06:01
wallyworldas well as the users it can find06:02
wallyworldwe don't have such a good pattern for this06:02
wallyworldbah, too much churn, i'll add a todo06:05
wallyworldand the CLI only passes one at a time anyway06:09
=== frankban|afk is now known as frankban
axw_mhilton: thanks for the review08:47
mhiltonaxw_: np09:10
tych0natefinch: replied on the bug12:11
tych0but it looks like wget is refusing to download something because the certs don't match?12:11
=== freyes__ is now known as freyes
lazyPowerinteresting new format of juju debug-log in beta16, it appears it rolled over to json formatting by default?12:54
babbageclunkmgz: around?13:20
mgzbabbageclunk: yo13:20
babbageclunkTrying to cleanup instances from running CI tests with --keep-env13:21
babbageclunkbut I can't find my AWS credentials - I may have lost them when my machine died.13:22
mgzso, what I do is JUJU_DATA=~/cloud-city/jes-homes/gz-test-env-name $GOPATH/bin/juju destroy-controller13:22
babbageclunkoh, actually, I have the user name and password, just don't have the URL for the canonical console13:23
mgzdepends if you have the env on disk still? you don't need seperate creds unless you wiped the env from disk13:23
mgzwhich creds were you using to test?13:23
babbageclunkI don't think that'll work - the api isn't up because the restore failed.13:23
mgzthe shared dev ones, or CI's?13:23
babbageclunkHmm - I guess the CI's ones.13:24
mgzbabbageclunk: then fall back to kill-controller - which again should get the aws details out of JUJU_DATA13:24
babbageclunkopk13:24
babbageclunkok13:24
mgztry that, yell if you have problems13:24
mgzthe aws console details for ci are in the consoles.txt file13:24
mgzbe careful poking around there, if you do use13:25
babbageclunkok, thanks mgz13:25
ram___andrey-mp: Hi. w.r.t your information yesterday, I created "cinder-storagedriver"  charm which will pass config data to relation to modify the configuration. I have taken your scaleio-openstack as reference. How do you certify scaleio-openstack charm? Please provide me the juu charm certification requirements.13:50
katconatefinch: standup time14:01
natefinchkatco: oops, thanks14:02
admcleodlooks like juju has overwritten authorized_keys rather than appending to it, is that normal? (1.25)14:23
mgzadmcleod: yes14:24
admcleodmgz: oh.14:24
admcleodmgz: thanks14:25
mgzadmcleod: juju expects to manage the file, so it hass list/add/delete/import14:25
mgzto manage14:25
admcleodright fair enough14:28
mgzthat is a surprise if you've edited it manually on a machine yourself perhaps :)14:29
mgzbabbageclunk: yell if you have any questions about my ssh key branch14:30
katcofrobware: dimitern: thank you for all your hard work for ivoks14:42
dimiternkatco: :) cheers14:43
babbageclunkmgz: LGTM!14:57
mgzbabbageclunk: merci14:58
katcodimitern: lmk when you have that hotfix ready so i can pass it on15:06
dimiternkatco: will do15:08
katcodimitern: ta15:08
mattywis someone able to talk to me about the new upload-tools logic?15:19
natefinchmattyw: it just works, as long as jujud is in the same directory as the juju you're running and they have the exact same version number15:20
mattywnatefinch, that's the thing - for me it didn't just work15:21
mattywnatefinch, so I'm trying to work out why15:21
natefinchmattyw: is it uploading when it's not supposed to, or vice versa?15:29
babbageclunkperrito666: ping?15:30
perrito666babbageclunk: pong15:31
dimiternkatco: I've sent this patch to ivoks - tested locally and seems to work, waiting on feedback later: http://paste.ubuntu.com/23093530/15:31
babbageclunkperrito666: I'm trying to understand backup and restore! :)15:31
katcodimitern: yay! ty! hope the feedback is good15:31
babbageclunkperrito666: various people said you were the one to talk to.15:31
perrito666babbageclunk: sadly I am15:31
alexisbdimitern, frobware you guys are rockstars thank you!15:32
katcoperrito666: don't you wish you had a... backup?15:33
katcoperrito666: it would... restore your sanity15:33
* babbageclunk lols15:33
* katco groans15:33
perrito666katco: you should do that for a living15:33
dimitern:) let's see if it'll be any good on site15:33
alexisbbabbageclunk, perrito666 I actually wanted to talk to both of you about the bugs youa reworking15:33
alexisbdo you guys have time for a quik HO?15:34
perrito666alexisb: sure15:34
babbageclunkalexisb: sure!15:34
alexisbsorry got distracted by some other fires15:34
alexisbperrito666, babbageclunk https://hangouts.google.com/hangouts/_/canonical.com/a-team-standup15:34
perrito666its a trap15:44
perrito666could anyone http://reviews.vapour.ws/r/5546/ ?15:47
perrito666its a quick short one15:47
natefinchI can look15:47
perrito666natefinch: just added QA steps15:48
natefinchahh crap, forgot about QA steps15:50
natefinchwell that quintuples the amount of time I have to spend reviewing it :/15:50
marcoceppiwhy does the Juju client still hard code support for OS?16:02
=== mup_ is now known as mup
marcoceppihttps://bugs.launchpad.net/juju/+bug/161653116:07
mupBug #1616531: "panic: unknown OS for series" when running client on Fedora <juju:Triaged> <https://launchpad.net/bugs/1616531>16:07
=== frankban is now known as frankban|afk
natefinchlol fedora16:29
perrito666natefinch: oh, that is not nice16:31
perrito666fedora is a fine distro16:31
natefinchI am sure it is.16:32
natefinchalso, why in the everloving hell does the client give a crap what OS it's running on?16:32
perrito666I thought we had fixed that bug ages ago16:33
natefinchno16:33
natefinchwe talked about it in december and never did it16:33
marcoceppi:sadpanda:16:34
alexisbperrito666, is this still an issue: https://bugs.launchpad.net/juju/+bug/153084019:08
mupBug #1530840: juju status-history too noisy with update-status <landscape> <juju:In Progress by alexis-bruemmer> <https://launchpad.net/bugs/1530840>19:08
perrito666alexisb: priv19:11
* redir lunches19:59
redirso quiet on fridays:)20:28
natefinchyep20:34
natefinchok, I give up20:38
natefinchsee you all next week20:38
redirI didn' miss anyone at the stand-up did I?23:31
redirI mean I just didn't join this week because there hasn't been anyone there since we rearranged23:32
=== zeestrat_ is now known as zeestrat
redirok23:44
* redir goes EoW soon-ish23:44
redirsee you next week juju23:57

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