/srv/irclogs.ubuntu.com/2017/03/07/#juju.txt

Hetfieldhi there. i'm using juju (2.0.2) to deploy an openstack cloud over maas 2.1. each server has 2 eth ports, one for management/internet the other for openstack internal communication. problem is juju picks the "internal" ip instead of the first one.08:00
Hetfieldlooks something like in https://bugs.launchpad.net/juju/+bug/161609808:00
mupBug #1616098: Juju 2.0 uses random IP for 'PUBLIC-ADDRESS' with MAAS 2.0 <4010> <cpec> <juju:Fix Released by dimitern> <https://launchpad.net/bugs/1616098>08:00
kjackalGood morning Juju world!08:38
kjackalHetfield: you might want to also report this at #juju-dev and #openstack-charms08:39
Hetfieldkjackal: i created a separated network space in maas may fix the issue. how to pass it in a bundle.yaml?10:22
kjackalHetfield: this is for deploying openstack on top of maas, right?11:23
kjackalHetfield: Is the extra network suposed to be a configuration parameter on a charm?11:24
kjackalHetfield: You might need to grab the bundle and edit it to put in the parameter11:24
cnfhmm11:45
cnfi just can't get juju working with sshuttle :(11:45
cnfhmm, not sure how to solve this11:48
cnfand juju doesn't seem to understand ssh jumphosts :P11:49
kklimondabbcmicrocomputer: do you have a minute to talk about contrail charms?11:53
cnfugh, why can't juju ssh :(12:09
cnfhmz, i don't understand what juju is doing12:18
Hetfieldkjackal: i got the yaml13:00
Hetfieldbut where to put the contraint? i could not find docs about supported params13:01
kjackalHetfield: I am not familiar with how openstack is deployed so you will have to help me abit to understand13:21
kjackalHetfield: Is there a parameter in any of the charms on the bundle you are deploying that should/could consume the extra interface?13:21
kjackalWhich bundle are you deploying13:22
kjackal?13:22
Hetfieldit's not important which bundle13:23
Hetfieldi mean: you can use contraints: tags=storage arch=amd6413:23
Hetfieldi dunno if i can put space=internal there too13:24
cnfnow it's just stuck at "Fetching Juju agent version 2.1.1 for amd64"13:25
cnf--debug should really put all tools it uses into debug13:25
kjackalHetfield: would that help: https://jujucharms.com/docs/2.1/network-spaces ?13:26
cnfhmz13:34
cnfdammit >,<13:34
cnfok... i think, maybe. i got it working13:43
cnfmaybe13:43
cnfhow do I remove a deployed charm?13:47
kjackalcnf: juju remove-application13:49
cnfok, ty13:50
cnfhmm13:51
cnfnow i can't deploy juju-gui to the juju controller13:51
cnfhmm, and I have a machine stuck in "0        pending  172.20.20.14  nx6rta   xenial  default"13:53
cnfmaas shows it as ready13:53
kjackaljuju gui should be integrated to the controller in juju 2.013:56
cnfyeah, it seems so13:56
cnfi'm new to juju, this is my first setup13:56
kjackalcnf: do a juju gui --show-credentials13:57
cnfyeah, _just_ figured that out :P13:57
cnfthanks :P13:57
cnfok, only took me 5 days to get maas/juju working :P13:58
cnfnow i just need to figure out how I clear this one "0        pending  172.20.20.14  nx6rta   xenial  default"14:00
kjackalcnf: if this is a provisioning issue you could try juju retry-provision14:02
cnfERROR unrecognized command: juju retry-provision ?14:02
cnfand the machine is down, i basically want it to release it14:02
kjackalcnf: sorry it is juju retry-provisioning14:05
cnfhmm14:44
cnfno, it's stuck in pending14:44
disposable2i have tried for days to do a juju bootstrap on a maas kvm node. every single time it ends the same way - "Fetching GUI 2.4.3" followed by "ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state". i'm watching the kvm node running through ridiculous amount of cloud-init and useless package installations but always after 20 minutes, it ends at this error. if it's a timeout issue, how do i increase the 20 minute t15:14
cnfdisposable2: did you run with --debug?15:16
disposable2more debug info at pastebin.com/vxQ4WEs715:16
cnfthere is a command to increase the timeout15:16
cnfbut 20 minutes i think should be plenty?15:16
disposable2cnf: i don't understand why the kvm node on ssd is slower than physical nodes.15:17
cnfare you sure it is?15:17
cnfit might be timeouting on something else15:17
cnfcan the node reach the internet?15:17
disposable2cnf: i don't know how to find out15:18
cnfyeah, i just spent 5 days playing to get the right nobs set :P15:18
cnfdisposable2: in maas, you can see the ip of the kvm node15:18
cnfssh to it, and checlk?15:18
disposable2cnf: as far as i can tell, every time i switch the node on, it gets pxebooted, runs through cloud init and shuts down.15:20
cnfwell, ssh to it as soon sas maas says it's up15:20
disposable2cnf: since the cloud-inits run through fine and don't give me errors i'd say it's got internet access through the maas server (as a gateway)15:21
cnfwell, maybe15:24
cnfbut why not test?15:24
cnfdisposable2: i had to add --config https-proxy=http://<ip of maas controller>:8000 to my deploy15:27
cnfand --config http-proxy15:27
=== joedborg_ is now known as joedborg
disposable2cnf: well, i've finally logged in (the kvm machine is ridiculously slow) and no, i can't ping anything. the default route is through the maas server but it hasn't got masquerading/nat-ing so traffic isn't passed further. which is weird bcause at the same time i can see cloud-init installing shitton of stuff15:36
cnfpass the --config http-proxy and --config https-proxy15:36
disposable2cnf: pass that how to what15:37
cnfjuju bootstrap --config http-proxy=http://172.20.20.1:8000 --config https-proxy=http://172.20.20.1:8000 dsmaas dsmaas-controller --debug15:37
cnfis what I ran15:37
cnf172.20.20.1 beeing the maas controller ip15:37
disposable2there is a field in x.x.x.x/MAAS/settings -> Network Configuration -> Proxy for APT and HTTP/HTTPS. is that the same thing?15:38
disposable2cnf: i meant http://x.x.x.x/MAAS/settings15:39
cnfno15:39
cnfnot that i know, anyway15:39
cnfmind, i am new at this15:40
disposable2cnf: ok, ihave to wait for the commissioning to stop before i can try it.15:40
cnfuhu15:40
disposable2cnf: ok, i'm bootstrapping it with those proxy parameters now. in the meantime, would you happen to remember how to increase the timeout value?15:55
cnf--bootstrap-timeout ?15:57
cnf--config bootstrap-timeout15:58
jamespagerogpeppe: hey can you remind me of the dance to promulgate something in the charm store please16:00
rogpeppejamespage: one mo, let me remind myself first16:01
disposable2cnf: where do you get thees config options from? man juju is utterly useless.16:01
cnfhaha16:01
cnfgoogle16:01
cnfand lots of time16:01
disposable2cnf: i'm ordering a "marco ceppi voodoo doll". every time there's something missing from the documentation i'll poke it with a fork. that'll teach them... years and years with almost no usable documentation. unless that's the entire point - to have to buy server support from canonical.16:04
rogpeppejamespage: two possibilities: it seems there's a "charm promulgate" plugin (but i don't know where it is). alternatively this command should work:16:06
rogpeppejamespage: bhttp -j put https://api.jujucharms.com/charmstore/v5/$charmid/promulgate 'Promulgate:=true'16:06
cnf:P16:07
jamespagerogpeppe: that's the one16:07
jamespagehow do I get bhttp?16:07
cnfdisposable2: i just want to install openstack, that's all16:07
rogpeppejamespage: go get github.com/rogpeppe/bhttp16:07
disposable2cnf: i need ceph + openstack cinder16:07
rogpeppejamespage: you might need to do: cd $GOPATH/src/github.com/rogpeppe/bhttp; godeps -u dependencies.tsv16:08
rogpeppejamespage: if you've got some older packages still lying around16:08
cnfgl16:08
jamespagerogpeppe: ok that sorted me out - thanks!16:10
* jamespage goes to rewrite promulgate-thing16:10
disposable2cnf: ok, same result, i'll try later with increaset timeout value. thanks for now16:11
disposable2s/easet/eased16:11
jamespagerogpeppe: any idea when that might make it into the charm tool itself?16:17
rogpeppejamespage: cool16:28
rogpeppejamespage: there is an external (canonical-only) command to do it16:28
jamespagerogpeppe: ftr its "'Promulgated:=true'"16:29
rogpeppejamespage: oh drat, thanks16:29
jamespageno worries16:29
rogpeppejamespage: ftr it's documented here: https://github.com/juju/charmstore/blob/v5-unstable/docs/API.md#put-idpromulgate16:29
jamespageta16:30
rogpeppejamespage: go get github.com/CanonicalLtd/charmstore-client/cmd/charm-promulgate16:30
rogpeppejamespage: actually you'll probably have to manually git clone that16:31
rogpeppejamespage: as go get doesn't like interactive authentication16:31
rogpeppejamespage: (there's a useful git config setting to make it work)16:31
lutostagsys.path.insert(0, os.path.join(os.environ['CHARM_DIR'], 'lib'))17:08
=== hml_ is now known as hml
Budgie^Smoreo/ juju world19:04
Budgie^Smorehey lazyPower am I reading this right, running juju deploy canonical-kubernetes will update an existing cluster?19:08
=== Budgie^Smore is now known as stormmore
stormmoreok I just ran juju upgrade-juju -m controller and now I keep getting permission denied errors, just how screwed am I?19:45
stormmoreapparently not much, updated my client system and reran the upgrade and now it behaving19:47
stormmorewell that seems to have worked nicely :)19:59
marcoceppistormmore: yes, you are correct (re juju deploy) it'll upgrade the charm revisions if that's where you started your k8s deploy20:09
stormmorethanks marcoceppi, I just updated my dev cluster20:14
=== tbc is now known as Tim
=== Tim is now known as tbc0
=== tbc0 is now known as tbc
stormmorehmmm now I am getting "an error on the server ("unknown") has prevented the request from succeeding " when I try and look at the logs in the k8s dashboard21:22
lP|lappystormmore: cdk or kube-core?22:30
stormmorelP|lappy, cdk22:31
lP|lappystormmore: this is a manifestation of the api-load-balancer i suspect. The layer7 proxy causes a lot of not-obvious errors like that.22:31
lP|lappystormmore: we have a spike coming this week or next to hack on a layer haproxy replacement to bring that down to a layer4 proxy so it can talk SPDY22:31
stormmore:-/ yeah and now after a test reboot of one of the nodes, containerd isn't starting :-/22:31
lP|lappystormmore: make sure you're capturing these as issues so we can address them with minimal pain on your side. I've done some reboot tests and the units survived, but that doesn't mean there aren't hidden dragons in there22:32
stormmorelP|lappy, you know me, first "try" and determine if the issue is my side or yours :P22:33
lP|lappythis is true :)22:33
lP|lappybut this is also my mantra22:33
lP|lappyi'd rather close bugs than never know they exist.22:33
stormmorelol metrics at their finest :P22:33
=== hml_ is now known as hml
lP|lappyi honestly wish i could instrument the charms like that22:35
lP|lappybut that also feels like a quick way to lose users22:35
stormmorelP|lappy, this is the error Docker is giving me: FATA[0001] Error starting daemon: error initializing graphdriver: driver not supported22:37
stormmorewhich seems odd as it was running just "fine" before the reboot22:37
lP|lappystormmore: is there a "NONE" in /etc/default/docker?22:40
lP|lappystormmore: i ran into a stray bug i wasn't able ot reproduce last week where a None got rendered in th edefaults file22:40
stormmoreOnly line worth mention is DOCKER_OPTS="  "22:44
stormmorelooks like an issue with the aufs driver22:59
stormmore"modprobe: FATAL: Module aufs not found in directory /lib/modules/4.4.0-65-generic" looks suspiciously like my problem!23:01
stormmorelooks like the updates I ran didn't update the linux-image-extras package!23:05
Budgie^Smorelove when I am multitasking trying to setup the office network while also troubleshooting cdk!23:10
stormmoreOK figured out what the problem was, just needed to install the correct linux-image-extra package23:47
stormmoreI am surprised that that doesn't get updated by apt update / upgrade though23:48

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