Wednesday, 2020-02-05

*** sameo has quit IRC00:44
*** igordc has joined #kata-dev01:52
*** igordc has quit IRC04:59
*** davidgiluk has joined #kata-dev09:01
*** gwhaley has joined #kata-dev09:04
*** gwhaley has quit IRC09:08
*** gwhaley has joined #kata-dev09:12
*** jodh has joined #kata-dev09:15
gwhaleymorning davidgiluk. would you know, who is looking at virtio-mem who we can rope in to do some kata docs review? See https://github.com/kata-containers/documentation/pull/59209:56
davidgilukgwhaley: virtio-mem I think is Dave Hildenbrand - I can ask him09:58
gwhaleydavidgiluk: thx - I think his repo is mentioned in that PR - so, if he's willing to have a look (I imagine he might want to know), then yes please :-)10:01
davidgilukgwhaley: I've let dhildenb know;  so those docs suggest you've already got the code in runtime to turn it on - interesting10:03
kata-irc-bot<graham.whaley> ```Hello Kata Citizens,  On behalf of myself, Graham Whaley (from Intel), and Ricardo Aravena (rico) as the approved election officials, it's a pleasure to announce that the Kata Containers architecture committee elections for February 2020 are open!  The timeline for the election process is:  * Election officials approved by AC: February 4  * Candidacy open: February 5-12  * "Debate period": February 13-23  * Voting: February 24 -10:33
kata-irc-botMarch 1  * Results: March 2  The window is now open for candidates to post their submissions. The process to submit a nomination is:  1) Review the responsibilities of the Architecture Committee members [1]  2) Between now and Feb 12 at 14:59 UTC, you can declare your candidacy for one of the open seats by submitting a textfile with your name (please put your name as the file name), the reason for running and your platform/objectives to this10:33
kata-irc-botfolder [2]. Please also send a message to the kata-dev ML with this same info, declaring your candidacy.  Who can vote:  Anyone who has had a commit merged into the project in the last 12 months will be eligible to vote. All eligible voters will receive an email with a link to the voting system once the voting period opens.  More details of the election process are outlined at [3] and in the etherpad at [4]. Note, once candidacy entry has closed10:33
kata-irc-botand we enter the debate period. We will be openly asking the candidates some questions around their candidacy. The community is encouraged to submit questions via the election officials and etherpad at [4] - get your thinking caps on now in preparation... we shall then filter, review, and choose a set of suitable questions for the candidates.  Please let us know if you have any questions about running for a seat or the election process!  [1]10:33
kata-irc-bothttps://github.com/kata-containers/community/tree/master/elections#architecture-committee-responsibilities [2] https://github.com/kata-containers/community/tree/master/elections/arch-committee-2020-02 [3] https://github.com/kata-containers/community/tree/master/elections [4] https://etherpad.openstack.org/p/KataArchCommElections_Feb2020```10:33
*** sameo has joined #kata-dev10:35
*** mreznik has joined #kata-dev10:57
*** jugs has quit IRC11:17
*** pcaruana has quit IRC11:37
*** jugs has joined #kata-dev11:38
*** pcaruana has joined #kata-dev11:50
*** gwhaley has quit IRC12:00
*** dinechin has joined #kata-dev12:23
*** mreznik has quit IRC13:14
*** gwhaley has joined #kata-dev13:24
*** lpetrut has joined #kata-dev13:24
*** jugs has quit IRC13:41
*** jugs has joined #kata-dev13:42
*** devimc has joined #kata-dev14:04
*** pcaruana has quit IRC14:17
*** fuentess has joined #kata-dev14:40
*** sameo has quit IRC15:02
*** eernst has joined #kata-dev15:25
*** eernst has quit IRC15:25
*** lpetrut has quit IRC15:28
*** pcaruana has joined #kata-dev15:49
*** devimc has quit IRC15:58
*** devimc has joined #kata-dev17:02
*** eernst has joined #kata-dev17:05
*** jugs has quit IRC17:11
*** jugs has joined #kata-dev17:12
*** igordc has joined #kata-dev17:34
*** eernst has quit IRC17:35
*** sameo has joined #kata-dev17:51
gwhaleydavidgiluk: if you need a Fixes on your PR, then you can make up a fake Issue number (0 or 999999 for instance), and afaik the CI will be happy - it does not verify they are active issues ;-)17:58
gwhaleyultimately, I think I already have enough power to force merge the PR - so, if it is still stuck in the morning, I will scrutinize and then likely just merge.17:58
davidgilukah I wondered why one of the previous ones had an issue associated with it17:59
gwhaleyyeah, nominal rules of the CI. it's fine, you can leave it as is and I'll take care of it in the morning.18:00
*** jodh has quit IRC18:00
*** gwhaley has quit IRC18:01
davidgilukyeah, all checks bodged, ahem passed18:05
*** davidgiluk has quit IRC20:01
*** dklyle has quit IRC20:19
*** david-lyle has joined #kata-dev20:19
fidenciodid someone ever face an error like 'level=error msg="rpc error: code = Internal desc = Could not mount kataShared to /run/kata-containers/shared/containers/: no such device"'?20:25
fidencioI'm trying to figure out where this could come from20:25
fidenciodevimc: ^20:37
devimcfidencio, nop, any special configuration ?20:38
fidenciodevimc: yeah, using virtio-fs :-)20:38
fidenciodevimc: nothing else apart from that20:38
devimcfidencio, rootless ?20:39
devimcI mean podman20:39
devimcor just docker ?20:39
fidenciodevimc: podman, running as root20:40
fidenciodevimc: with all the shenanigans to not use SELinux20:40
devimcand no cgroups v220:40
devimcright?20:40
devimcfidencio, ^20:40
fidenciodevimc: that's a good point :-)20:40
fidenciodevimc: let me double check it20:41
devimchehe anyway I think I broke it20:41
devimcI'm facing a similar issue with podman20:41
devimcfidencio, https://github.com/kata-containers/runtime/issues/243820:41
fidenciodevimc: I'm passing "systemd.unified_cgroup_hierarchy=0" as kernel_params, meaning no cgroups v220:42
fidenciodevimc: are you running in permissive mode?20:42
devimcfidencio, would you mind applying this patch https://github.com/kata-containers/runtime/pull/2441 and try again ?20:42
fidenciodevimc: sure thing, gimme a few minutes20:43
devimcfidencio, thanks20:43
devimcfidencio, do you know what device is trying to mount?20:46
fidenciohow can I check that? :-)20:46
fidenciodevimc: about your patch, I'll really need a few minutes, as I'm mostly trying stuff on 1.10.020:47
devimcfidencio, sudo journalctl -b -t kata-runtime20:48
devimcfidencio, are you using hugepages or something in /dev/shm ?20:49
fidenciodevimc: https://paste.centos.org/view/516c9dbe20:50
fidenciodevimc: not using hugepages, the only thing in /dev/shm is libpod_lock20:51
fidenciodevimc: I'm just checking gitlog here (in order to realise how many changes were done after 1.10.0 was released) ...20:55
fidenciodevimc: if you broke it, you broke it after the release it seems20:56
devimcfidencio, I think so20:56
devimcfidencio, so 1.10 is broken ?20:56
fidenciodevimc: I'm facing the issue running 1.1020:57
fidenciodevimc: I'll still test your patch, tho. Just need some minutes :-)20:57
devimcfidencio, but using stable-1.10 branch or kata-deploy binaries ?20:57
fidenciodevimc: using Fedora RPMs for 1.1020:58
fidencioI'll do a test running upstream, then switch back to stasble 1.10 branch ...20:59
devimcfidencio, ok, then it wasn't me ^_^20:59
devimcfidencio, seems like agent is failing, would you mind enabling debug and try again?20:59
devimchttps://github.com/kata-containers/documentation/blob/master/Developer-Guide.md#enable-full-debug20:59
devimcbut this time I'd like to see kata-agent logs20:59
devimcsudo journalctl -b -t kata-proxy21:00
fidencio"where are my logs Lebowski?"21:04
fidenciocan't see any log related to agent, that's freaking weird21:05
devimcfidencio, mmm I guess you are using vsocks?21:05
fidenciodevimc: I'm. Do you wanna see the full configuration.toml?21:06
devimcfidencio, yes21:06
devimcsudo journalctl -b -t kata-shim21:06
devimcagent's logs are there21:07
devimcif use_vsocks is true21:07
devimcfidencio, ^21:07
fidenciodevimc: https://paste.centos.org/view/f0104e8721:08
fidenciodevimc: yes, use_vsocks is true21:08
devimcuhmm ok, that's not the default configurations21:09
fidenciodevimc: yeah, I've been playing with qemu + virtiofs there :-)21:09
fidencionow I have the logs21:10
devimccool21:10
fidenciodevimc: https://paste.centos.org/view/4932506c21:12
devimcfidencio, that's weird, the device is there but it can't be mounted21:20
devimcfidencio, what guest kernel version are you using?21:21
devimcls -l /var/cache/kata-containers/vmlinuz.container21:21
fidenciodevimc: that's the same as my host (RHEL)21:22
devimcfidencio, maybe that's the problem, for virtio-fs a newer kernel is required21:23
devimcwith some patches21:23
fidenciodevimc: I do have virtiofs there, but that puts a lot of light on my debugging21:23
fidenciodevimc: now, let me do the tests using upstream21:23
*** th0din has quit IRC22:42
*** devimc has quit IRC22:49

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