/srv/irclogs.ubuntu.com/2017/06/01/#juju.txt

=== axw_ is now known as axw
kjackalGood morning Juju world!07:15
=== salmankhan1 is now known as salmankhan
Zichi here14:20
ZiclazyPower: hmm, I have a problem with a juju upgrade-charm kubernetes-worker : http://paste.ubuntu.com/24737881/14:21
Zicrunning apt-get update manually on the unit machine does not return any error, I don't understand14:21
lazyPowerZic: thats fun. if you run apt-get upgrade does it complain about the 404's now that you've run the upgrade?14:23
lazyPowertypically when i see that, its because i have a stale cache lying around14:23
lazyPower*update14:23
ZiclazyPower: nop, if I run apt-get update directly on the unit machine all is fine :(14:24
lazyPowerZic: thats funky. if you re-execute upgrade-charm does it work?14:25
lazyPoweris this in aws or your on-prem solution?14:25
Zicthis is the fully-AWS cluster14:25
ZiclazyPower: I see in juju debug-log that the upgrade-charm still retrying the apt-get update, but with the same error 40414:26
lazyPowerZic: hang on, so you ran the apt-get update && apt-get upgade on that host thats currently locked trying to do the same operation in upgrade-charm?14:28
Zicrunning it after it give-up in juju debug-log yup14:30
Zichmmmm14:30
Zicsolved \o/14:30
ZiclazyPower: I just did what it advices : apt-get update --fix-missing14:30
Zicupgrade-charm is now unlocked and proceed14:30
lazyPowergood deal14:30
Zicdid an "apt update --fix-missing" earlier before alerting you, but as the charm use apt-get and not apt, it seems to not be the same cache14:31
ZicI have just one error left, but don't know it is important: unit-kubernetes-master-0: 14:33:22 ERROR juju.worker.metrics.sender could not remove batch "6009d068-6c17-4403-8c4e-bf186e66b8ea" from spool: remove /var/lib/juju/metricspool/6009d068-6c17-4403-8c4e-bf186e66b8ea: no such file or directory14:33
ZiclazyPower: hmm, upgrade-charm kubeapi-load-balancer literally broke Juju, don't know what happened : http://paste.ubuntu.com/24738034/14:44
Zicthe juju controller machine suddenly froze then came back with this14:44
lazyPowerZic: that smells like the juju db stopped.14:45
pathclhey anybody using vsphere with distributed virtual switch having this bug ? 161981214:45
ZiclazyPower: happily it seems to recover automatically14:45
Zicall machine agent was in "unknown" but they just came back14:46
Zicand all is green, even the kube-apilb14:46
=== pathcl is now known as path
Zic-> don't know what happens but it works14:46
=== path is now known as pathcl
mattywlazyPower, ping?14:58
lazyPowermattyw: pong14:58
mattywlazyPower, hey there, the problem Zic saw about with juju.worker.metrics - that was following a charm upgrade on k8s right?14:59
lazyPoweryeah, i think so14:59
lazyPowerZic: i'm going to talk about you like you're not here ;)14:59
Zic:D15:00
Zicyup15:00
Zicwas after a juju upgrade-charm on kubernetes-master15:00
Zic(or maybe just after juju config channel=1.6/stable)15:01
mattywany idea what the before and after versions were?15:01
mattywand if metrics had been added15:02
mattywbecause if so I believe that's a known bug - just want to make sure there's not a new bug I should know about15:02
Zicmattyw: hmm, if I can find the old revision number of charm somewhere, say it to me but if it does not exist: this was a CDK cluster last fully-upgraded a month ago15:06
Zicwas already in 1.6.2, just upgrade Juju operationnal code15:06
mattywlazyPower, latest version should be recording metrics right?15:06
lazyPowermattyw: yeah, we've had metric support in the k8s charms for the last 3 releases that i'm aware of15:07
Zicunit-kubernetes-master-0: 15:07:09 INFO unit.unit-kubernetes-master-0.collect-metrics error: persistentVolume is not namespaced15:07
Zicit's not in INFO instead of ERROR15:07
Zics/not/now/15:07
mattywZic, what happens if you run juju collect-metrics kubernetes-master/0 ?15:08
ZicERROR "kubernetes-master/0" is not a local charm15:10
Zic(it is... in fact)15:10
ZiclazyPower: multi-master is still considered "not for production usage"?15:22
ZicI'm asking myself if I switch this production cluster to multimaster again now it is upgraded to the latest charms15:22
=== scuttlemonkey is now known as scuttle|afk
lazyPowerZic: its supported16:21
lazyPowerwell, supported in our solution as you're using the load balancer16:22
lazyPowerZic: sorry about the delay was out getting my walk in before the day turned up the heat :)16:22
Zicnp :)16:23
tvansteenburghcmars: i think you were right about zetcd16:28
lazyPowerwhat'd i miss about zetcd?16:28
cmarstvansteenburgh, ok :) yeah, i was trying to get it to work with the etcd charm. ended up with https://github.com/cmars/charm-zetcd but couldn't get the tls stuff working16:29
tvansteenburghlazyPower: i snapped it, cmars has been playing with it16:29
cmarslazyPower, just some hacking around. i was thinking it'd be neat to use kafka with etcd instead of zookeeper16:30
=== jcamino100080 is now known as jcamino
lazyPowerinteresting16:45
lazyPowerok :) i thought maybe this was something i should be tracking16:45
=== scuttle|afk is now known as scuttlemonkey
bdxnew use case popping up21:40
bdxI'm just having my users add their local vms to JAAS models21:41
bdxthis eliminates each user needing to bootstrap and know how to operate a controller21:42
bdxand alleviates the load of a controller on their on their dev vms21:42
bdxthis has allowed users to hop right in and deploy things to a local vm from their osx hosts21:44
bdxI have a lxd-proxy charm that I'm having users deploy to the the local vm21:44
bdxthen they just access the lxd services on the vm via the lxd proxy21:45
bdxsuper streamlines the osx dev use case21:45
lazyPower:o you can do that?22:20
lazyPower#TIL22:20
tvansteenburghbdx: blog post please :P22:22
bdxI am so backed up as far as blog posts go, oh man22:22
bdxcreating some quality blog content is going to be my summer project22:24

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