/srv/irclogs.ubuntu.com/2018/06/29/#juju.txt

wallyworldveebers: i left a few comments, let me know if you need further clarification00:26
kelvin__wallyworld, LGTM it's much nicer now to ensure our operator app using StatefulSet. Thanks.00:36
wallyworldkelvin__: awesome, thank you. we stil use deployment controllers for stateless pods though00:37
wallyworldthat's my understanding of best practice00:37
wallyworldalso, the operator pod is still only a single pod, not yet managed00:37
wallyworldthe workload pods using storage with be stateful sets00:38
kelvin__wallyworld, ic, we are using operatorPod() to ensure operator.00:44
wallyworldkelvin__: yeah, for now it's just a single pod. but we need to change that00:56
kelvin__yeah, i saw the TODO00:59
veeberswallyworld: sweet will do01:37
veeberswallyworld: I'm inclined to move a reciever method (member method, unsure of name) that doesn't need any state into a stand alone (i.e. checkFiles(files map[string]string)). Any reason I shouldn't02:08
veeberswallyworld: note, I'm changing that method from checkFiles(files map[string]string) -> checkFile(files string) as we iterate at a higher level now02:09
babbageclunkveebers: channelling wallyworld I reckon that sounds great02:09
veebersbabbageclunk: sweet thanks babbageworld (or would that be wallyclunk?)02:10
babbageclunkha, I like either of those02:10
veebers^_^02:10
veebersMr Babbageworld Wallyclunk.02:11
babbageclunkAlmost as good as Engelbert Humperdinck02:12
babbageclunkOr Benedict Cumberbatch02:12
veebershah, indeed!02:13
thumperveebers: the only time I don't is when I use the receiver to effectively namespace the function02:18
veebersthumper: ack, this is unexported helper function.02:18
thumperthen I think it is fine02:19
veeberswhich , actually, does use stored state so I'll leave this one, but will do the other helper that doesn't ^_^02:19
wallyworldveebers: sounds ok, i'll look once pushed02:29
veeberswallyworld: I thought the use of params.DockerInfoResponse in state might be icky. Where is best to create a core struct that will be used internally?02:44
wallyworldveebers: in the top level core package02:44
wallyworlda subpackage under there02:44
wallyworldmaybe resources02:45
veeberswallyworld, kelvin__ : develop doesn't build with the latest commit of charm.v6, are we still waiting for something to land in develop so it will?05:34
wallyworldveebers: you sure you ran godeps?05:36
wallyworldthere were several upstream changes05:36
* veebers makes sure05:36
wallyworldbuilds for me05:37
veeberswallyworld: godeps kicks charm.v6 to 0f7685c8 (the commit before kelvin__ merged his bits), but tip for charm.v6 is 6e010c5e005:38
wallyworldah, we may be waiting on a juju deps update05:39
wallyworldto bring in tip of v605:39
kelvin__i will have to update a few deps later after bundlechanges done05:39
wallyworldveebers:  so your branch should leave deps untouched05:39
veeberskelvin__, wallyworld: ah ack makes sense, all good.05:40
wallyworldkelvin__: if you have landed upstream, you can land anytime05:40
kelvin__wallyworld, yeah, i will update all them together with bundlechanges upgrade in juju.05:42
wallyworldsounds great ty05:42
ybaumyhmm i tried .. conjure-up stable/beta/edge and get the same behavior http://pastebin.centos.org/878811/05:43
ybaumyanyone can help me05:43
ybaumyah yes kubernetes canonical install going on05:44
ybaumyonly the master  is not working05:45
wallyworldybaumy: we'll need  a lot more info - k8s logs, juju logs, what substrate etc05:45
ybaumyim deploying on localhost05:45
wallyworldusing lxd cloud?05:45
ybaumywallyworld: localhost with lxd05:45
wallyworldwhich bundle? cdk or kubernetes-core?05:46
ybaumycanonical kubernetes05:46
ybaumyi enabled helm and prometheus05:47
wallyworldthat's a fairly heavy weight bundle for use on local host - you may be out of resources or something. but hard to say without more info05:47
ybaumymy localhost has 8 cores and 24GB ram05:47
wallyworldyou'll need to look at k8s logs to see why it can't schedule that pod05:48
ybaumyk mom phone05:48
thumperwallyworld: fyi https://github.com/juju/juju/pull/887505:54
wallyworldlooking05:54
thumperwallyworld: I have a follow up one that adds the values to the model config and updates api server call05:55
wallyworldrighto05:55
thumperybaumy: what does juju status say?05:56
kelvin__wallyworld, would u mind to have a quick look on this fix? https://github.com/juju/charm/pull/250/files  thanks05:59
wallyworldsure05:59
ybaumythumper: juju status says waiting for kube-system pods to start06:00
ybaumyand as you can see in the pastebin .. the scheduler cannot start the pods06:01
thumperybaumy: can you pastebin the output of juju status?06:01
ybaumyhttp://pastebin.centos.org/878896/06:02
ybaumyon beta there was 1.10.4 i think06:03
ybaumyand i had the same problem06:03
ybaumycpu and memory i think are not the problem. the vm is pretty much idle right now06:03
thumperybaumy: it looked like the kubernetes-master unit was still setting up06:05
thumperkubernetes-master/0*      waiting   idle   9        10.48.163.224   6443/tcp                                 Waiting for kube-system pods to start06:05
thumpereverything else was up and running06:05
wallyworldthumper: lgtm06:05
thumperuntil that is marked as "active" you probably won't have much luck06:05
thumperif it has been a long time06:05
thumperthere may be other issues06:05
thumperwallyworld: any ideas?06:05
ybaumythumper: http://pastebin.centos.org/878811/ this goes on forever06:05
wallyworldkelvin__: lgtm, i wondered about that at the time but forgot to ask06:05
kelvin__wallyworld, ah. missed that place.. thanks.06:06
wallyworldthumper: ybaumy: i have seen the master node take a while to start usually. sometimes a few minutes06:06
wallyworldbut if it doesn't start you need to look at k8s logs06:06
thumperJun 29 05:42:28 juju-161da2-9 systemd[1]: Failed to reset devices.list on /system.slice/calico-node.service: Operation not permitted06:07
thumperthat line looks a little suspicious06:07
ybaumywallyworld: where can i find the k8 logs06:07
wallyworldi would try just the kubernetes bundle not the CDk one06:07
wallyworldybaumy: you need to use kubectl to look at the particular artifact that is not working06:09
ybaumyah ok06:09
wallyworldkubectl logs -f ....06:09
ybaumythe kubernetes bundle has it also those features like integrated helm and elasticsearch?06:09
ybaumyand prometheus06:09
wallyworldi would start simple by trying the smaller kubernetes-core bundle06:11
wallyworldjust to ensure that works06:11
ybaumyok06:11
kelvin__wallyworld, got another one for bundlechanges, https://github.com/juju/bundlechanges/pull/41/files thanks.06:13
ybaumyi wanted to give our team a quick way to deploy a cluster on one vm with alot of features so i thought that canonical bundle would be nice06:13
wallyworldkelvin__: looking06:13
wallyworldybaumy: it is nice, but we need to step back to try and see the source of the error06:14
wallyworldstarting with a smaller bundle can help verify that the basics are all ok06:14
ybaumyinstalling.. will take few minutes.. bbl. need to got to meeting06:15
wallyworldand you can still add promethius etc is you need to. but you may not need HA06:16
wallyworldok, i'll be offline soon but other folks will be here06:16
ybaumythanks wallyworld06:16
wallyworldwe'll get it fixed for you, just may talk a bit of debugging :-)06:16
wallyworldkelvin__: lgtm!06:17
kelvin__thanks, wallyworld06:18
w0jtashello, anyone could help fixing keystone error? "ERROR Signing error: Unable to load certificate - ensure you have configured PKI with "keystone-manage pki_setup""07:07
manadartstickupkid: Hop on the guild HO when you are set up this morning.07:08
manadartstickupkid: Review? https://github.com/juju/juju/pull/887708:09
stickupkidmanadart: done08:22
manadartstickupkid: Ta.08:22
stickupkidmanadart: on da hangout08:23
manadartstickupkid: Added that test.08:33
stickupkidmanadart: approved the changes08:33
manadartstickupkid: Ta.08:33
stickupkidmanadart: i've removed the remote from the lxd provider, but i'm not sure it's worth the effort removing it from the tools/lxdclient - there is some logic there that i'm unsure is even worth unprising from it09:22
manadartstickupkid: Sure. Propose it and we can have a look.09:26
stickupkidmanadart: sorry was manual testing https://github.com/juju/juju/pull/887809:47
w0jtashow can i remove dead controller from juju ?10:00
stickupkidw0jtas: do you have access to the controller at all?10:12
manadartw0jtas: If the controller machine is dead/gone and kill-controller does not work, you can use "unregister". Note that that just removes it from your local registry and doesn't do resource cleanup.10:21
w0jtasmanadart: thanks!10:23
manadartw0jtas: Sure thing.10:23
w0jtasafter running juju upgrade-charm neutron-gateway i have error on status list: "hook failed: "upgrade-charm"" what can i do here to debug ?10:24
w0jtasok nvmd, deleted setup and starting again10:27
stickupkidmanadart: so i've removed the rawProvider from my branch now11:07
manadartstickupkid: Nice.11:07
rick_h_Morning party folks11:08
stickupkidmanadart: so the only thing left is sorting out the lxdclient when connecting to local - i guess the storage and default network11:08
stickupkidmanadart: i also introduce the server spec, there is a lot of testing to do here :D11:09
stickupkidmanadart: also i think we should consider some of the internal namings whilst we're here tbh11:10
manadartstickupkid: HO?11:16
manadartrick_h_: Morning.11:16
stickupkidmanadart: yeap11:16
stickupkidrick_h_: morning11:17
* manadart heads to GUILD HO.11:17
w0jtashow can i change storage size in juju ? during install i've set 10GB :/11:23
rick_h_w0jtas: check out the root disk size constraint.11:34
w0jtasrick_h_ where ? :)11:34
rick_h_w0jtas: https://docs.jujucharms.com/2.3/en/reference-constraints11:34
w0jtasthanks11:35
w0jtashmm "juju get-model-constraints" doesn't return anything11:36
w0jtasin nova-compute log i see "phys_disk=9GB used_disk=0GB"11:37
manadarthml: From the doc: "juju upgrade-series complete 4". What is the "4"?14:15
hmlmanadart: a machine number14:15
manadarthml: Ah, got it. Thanks.14:16
PatrickD_When trying to deploy kubernetes bundle xenial with 16.04-hwe kernel (Bionic still not supported), on maas (juju on bionic, maas on bionic, if that makes a difference), I get this error in juju status : hwe_kernel": ["xenial has no kernels available which meet min_hwe_kernel(ga-18.04)14:21
tvansteenburghrick_h_: that mean anything to you? ^14:23
PatrickD_still trying to find out where it comes from (juju or maas ?). my default_min_hwe_kernel is ga-16.04 (from get-config name=default_min_hwe_kernel) can't find where ga-18.04 comes from.14:27
rick_h_tvansteenburgh: PatrickD_ that looks like a maas error14:28
rick_h_PatrickD_: run juju status --format=yaml14:28
rick_h_See if there's any other details in the machine section.14:28
rick_h_PatrickD_: might also have to check the debug log/controller for provisioning feedback there.14:29
PatrickD_same error there... still searching. will look at logs.14:31
pmatulisPatrickD_, yes, that's a MAAS error14:45
pmatulischeck your kernel settings. easiest to do in their web UI14:47
pmatuliscurrently it looks like the minimum kernel is set at 18.04 but you are requesting 16.0414:47
PatrickD_there is no "min_hwe_kernel" only "default_min_hwe_kernel", which is right now set at ga-16.04, not even 18.04.14:49
stickupkidhml: looks good to me https://github.com/juju/juju/pull/887414:50
hmlstickupkid: ty14:51
stickupkidmanadart: trying to work out how to test the error messaging from lxd errors is interesting14:51
manadarthml: Approved #8866, notwithstanding any implementation detail to be discussed with externalreality.14:51
hmlmanadart: ty -14:52
PatrickD_Looks like I will have to wait for Bionic charms, or for soemone in MAAS to help me with this issue :) Any ETA for Bionic Charms ?14:56
manadartstickupkid: Approved #8878 with one comment on naming.14:57
stickupkidmanadart: naming is the hardest thing15:22
stickupkidmanadart: is officially NewXXX is supposed to returns a pointer and MakeXXX not15:23
stickupkidmanadart: but I guess that boats sailed...15:24
manadartstickupkid: Not going to die on that hill. Land it.15:26
stickupkidmanadart: I remove lxdclient completely and it all works for bootstrapping, i'll land my patch later15:28
stickupkidmanadart: we broke the error messaging I believe, I'm going to try and reinstate it15:32
manadartstickupkid: OK,15:32
stickupkidmanadart: by we, I probably mean me, when I moved to the new client for getting the local address15:32
tvansteenburghPatrickD_: no ETA yet, but it'll be soon. likely next week15:50
=== mup_ is now known as mup
stickupkiddoes anyone know what is supposed to happen with juju register localhost?17:26
stickupkidis that supposed to work17:26
hmlstickupkid:  localhost being a controller name?17:28
stickupkidlocalhost being lxd17:28
hmlstickupkid: is it supposed to work… juju register requires a controller name or registration string17:29
stickupkidjust hangs on my end, i'm trying to work out if i've broken anything17:29
hmlstickupkid: i wouldn’t have expected it to be possible.17:29
stickupkidit doesn't work on 2.4 either17:29
hmlstickupkid: what are you wishing to accomplish with it17:29
stickupkidhml: see if it tries to grab any credentials... etc17:30
hmlstickupkid: you need to boot strap a controller - add a user to it - which provie give the registration string17:31
hmls/provie/provide17:31
stickupkidhml: thought as much17:31
stickupkidhml: cool, well i'm done for the week - have a good weekend :)17:31
hmlstickupkid: you too!17:31

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