Thursday, 2018-10-18

*** LinuxMe has joined #kata-dev00:04
*** LinuxMe has quit IRC00:10
*** annabelleB has joined #kata-dev00:35
*** annabelleB has quit IRC00:37
*** LinuxMe has joined #kata-dev01:05
*** zerocoolback has joined #kata-dev01:09
*** LinuxMe has quit IRC01:11
*** annabelleB has joined #kata-dev02:22
*** annabelleB has quit IRC02:31
*** changcheng has joined #kata-dev03:14
*** changcheng has quit IRC03:16
*** LinuxMe has joined #kata-dev03:23
*** LinuxMe has quit IRC03:28
kata-irc-bot<eric.ernst> @xu how’d the meetup go?04:02
kata-irc-bot<eric.ernst> @james.o.hunt - wanted to see how the agent tracing work is going. I was helping with some debug and thinking how helpful it’d be. Or at least fun, anyway. :)04:15
kata-irc-bot<xu> not bad, will summary it later today05:19
*** annabelleB has joined #kata-dev05:48
*** LinuxMe has joined #kata-dev06:05
*** annabelleB has quit IRC06:08
*** LinuxMe has quit IRC06:10
*** marcov has quit IRC06:39
*** marcov has joined #kata-dev06:39
*** lpetrut has joined #kata-dev07:09
*** LinuxMe has joined #kata-dev07:53
*** gwhaley has joined #kata-dev07:56
*** LinuxMe has quit IRC07:58
*** davidgiluk has joined #kata-dev08:03
*** jodh has joined #kata-dev08:15
* gwhaley throws a mebibyte @marcov ;-)08:53
marcov@gwhaley mebibyte, aka the old trick used by hd manufactures to rip you off  ))09:01
davidgilukis there something to forcibly clean up after crashed containers?  Given the proddings I'm doing with qemu I can leave things in quite a mess09:46
gwhaleyhi davidgiluk. not specifically in kata, no. I tend to use a combination of pgrep/pkill to clear out any kata-* (proxy and shim) and qemu* . We probably accumulate cruft down in the /var work dirs though. Yeah, crashing out containers can leave a little mess around.09:49
* gwhaley sees 'k a t a' turn up as 'j e s s f r a z' over on slack. meh, tired of chasing that - but will note to @openstack in case they want to go fix again...09:51
davidgilukhaha09:51
davidgilukperhaps it would be easier to rename the project :-)09:51
gwhaleyor rename jess :-)09:51
gwhaleyapparently it's an issue with the 'mappings' - I think if something fails/falls out then it ends up either taking the first or the next answer - which ends up mapping k-a-t-a to jess - ho hum.09:52
*** LinuxMe has joined #kata-dev09:54
davidgilukgwhaley: I get things like k-runtime list   hanging after I've nuked a qemu09:57
davidgilukor at least taking a long time09:57
davidgilukand then lieing to me telling me it's still running09:57
gwhaleyah, that's not a good thing. I've chased a few of those down before. In the past we could end up with something stuck holding a lock down in the /var/vc area. or...09:58
gwhaleymaybe you still have the shim/proxy pair for that container running, so the runtime is asking them to ask the qemu, and they are sat and then time out...09:58
gwhaleyyes, there is work to do on capturing bad death/shutdowns.09:58
gwhaleyI have been killing proxy's this week, and that takes the shim with it, but leaves the qemu around I think09:59
*** LinuxMe has quit IRC09:59
gwhaleydavidgiluk - have you tried a 'docker kill' on the conatiner (even though your qemu has gone away), maybe that will hit the proxy/shim pair, and nuke them (after potential timeout), and clear up the docker side as well10:00
davidgilukoh I've already nuked the proxy10:01
gwhaleyI wonder where the runtime list is hanging up then. If you are curious, you could enable the runtime debug in the config file and capture what it tells you in the journal logs - and then post us a github Issue ;-)10:02
davidgilukoh, I hadn't realised that even 'list' would follow that debug; in that case I can chase it10:03
gwhaleyI think it will - list will go walk the /var/lib/vc/sbs dirs gathering info. I'm presuming that will get some debug out of virtcontainers... If you get a solid hang up, then you can 'dlv' debug the hung up runtime and get the stacks of the goroutines. That is where I used to find we deadlocked on a lockfile in that area - but, sboeuf rewrote all that code (much nice/faster now), and I've not seen one of them for some time10:05
davidgilukin the past I have recovered it by nuking the sbs dir10:06
gwhaleyoh, you might want to check how many subdirs you have down in that dir btw - I think things might leak under some circumstances :-( for instance, my test box has 0 containers running, and I have 221 dirs there :-(10:06
gwhaleyand I suspect 'list' walks them all, even if they are not 'active'10:07
davidgilukI also have to forcibly clean up the overlays when that happens, otherwise I wonder where the free space went10:08
gwhaleyyeah. docker eats space... it collects up images, volumes and stuff.... I had to 'docker system prune -a --volumes' yesterday to grab 5G back... and that is not a k a t a thing - that is just docker :-)10:09
gwhaleyjodh - did you just cherry pick the same PR 3 times? I thought we only ever had to do 2 picks, as we only have one master and two stables - what did I miss? ;-)10:14
jodhgwhaley: we have 3 stable branches now, but maybe we need to discuss that ;)10:14
jodhgwhaley: also, it wasn't a simple cherry pick - conflict resolution was required ;)10:15
gwhaleyand, you hit a cyclo complexity on one of them already ;-)10:15
jodhgwhaley: I'm a bit confused though - is there a problem with raising PRs for the stable branches?10:18
gwhaleyjodh - nope. I just wondered why you had done 3 of them when we are only meant to have 2 maintained stable branches at any one time. I suspect we have not deprecated the oldest one when we were meant to.10:23
kata-irc-bot<james.o.hunt> @eric.ernst - we have 3 stable branches now, but we document we only maintain 2: https://github.com/kata-containers/documentation/blob/master/Stable-Branch-Strategy.md#branch-management10:25
kata-irc-bot<james.o.hunt> @eric.ernst - regarding agent tracing, nothing significant to add since last update - trying to track down why the trace transaction is not completing.10:27
*** gwhaley has quit IRC10:59
*** devimc has joined #kata-dev11:57
*** gwhaley has joined #kata-dev12:15
*** dims has quit IRC12:30
*** lpetrut has quit IRC12:33
*** dims has joined #kata-dev12:34
*** zerocoolback has quit IRC13:22
*** sameo has joined #kata-dev13:38
*** annabelleB has joined #kata-dev14:34
*** annabelleB has quit IRC14:40
*** dklyle has joined #kata-dev15:06
*** annabelleB has joined #kata-dev15:10
*** fuentess_ has joined #kata-dev15:14
*** annabelleB has quit IRC15:27
*** devananda has joined #kata-dev15:30
*** annabelleB has joined #kata-dev15:33
*** sameo has quit IRC16:05
*** annabelleB has quit IRC16:12
*** dklyle has quit IRC16:16
*** dklyle has joined #kata-dev16:16
*** LinuxMe has joined #kata-dev16:33
*** dklyle has quit IRC16:37
*** annabelleB has joined #kata-dev16:39
*** annabelleB has quit IRC16:43
*** annabelleB has joined #kata-dev16:52
*** gwhaley has quit IRC16:58
*** jodh has quit IRC17:14
*** dklyle has joined #kata-dev17:30
*** dklyle has quit IRC17:42
*** dklyle has joined #kata-dev17:50
*** sjas has joined #kata-dev17:56
*** dklyle has quit IRC18:02
*** annabelleB has quit IRC18:07
*** dklyle has joined #kata-dev18:20
*** annabelleB has joined #kata-dev18:25
*** dklyle has quit IRC18:29
*** annabelleB has quit IRC18:32
*** annabelleB has joined #kata-dev18:34
*** dklyle has joined #kata-dev19:07
*** dklyle has quit IRC19:14
*** davidgiluk has quit IRC19:30
*** annabelleB has quit IRC19:32
*** devananda has quit IRC19:47
*** annabelleB has joined #kata-dev20:54
*** dklyle has joined #kata-dev21:36
*** devimc has quit IRC21:37
*** dklyle has quit IRC21:45
*** LinuxMe has quit IRC22:47
*** LinuxMe has joined #kata-dev23:23
*** LinuxMe has quit IRC23:27
*** annabelleB has quit IRC23:31
*** LinuxMe has joined #kata-dev23:56

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