Monday, 2018-06-18

kata-irc-bot<verytired1> @eric.ernst i think we might have grabbed the katacontainers namespace on docker hub. let me see if we did00:50
kata-irc-bot<krsna1729> there does exist a page https://hub.docker.com/u/katacontainers01:30
*** zerocoolback has joined #kata-dev03:01
*** sjas has joined #kata-dev04:18
*** sjas_ has quit IRC04:21
kata-irc-bot<caihaomin> Can find CI retrigger  button after update... where did it go buddies~~~ @sebastien.boeuf @james.o.hunt05:16
*** Ankita_ has joined #kata-dev05:20
*** Ankita_ has quit IRC06:16
*** jodh has joined #kata-dev07:16
*** jodh has quit IRC07:16
*** jodh has joined #kata-dev07:16
kata-irc-bot<james.o.hunt> @caihaomin - I see a "rebuild" button when I login (click top right button) on http://jenkins.katacontainers.io/. If you don't have that option, please ping @salvador.fuentes / @mnaser.07:25
*** zerocoolback has quit IRC07:25
*** sameo has joined #kata-dev07:25
*** zerocoolback has joined #kata-dev07:30
*** zerocoolback has quit IRC07:35
kata-irc-bot<eric.ernst> Thanks @verytired107:50
*** davidgiluk has joined #kata-dev08:02
kata-irc-bot<caihaomin> @james.o.hunt thx  and then ping @salvador.fuentes  Plz help me solve this ~~~ :grinning:08:03
*** gwhaley has joined #kata-dev08:04
*** zerocoolback has joined #kata-dev08:05
*** eernst has joined #kata-dev08:16
kata-irc-bot<niteshkonkar007> Hey, do we pass rootfs using DAX to our kata-container? Also if I understand correctly, the rootfs approach is basically making a qemu-img disk, copy rootfs into it, install gpart etc binaries into it, pass it to the VM using DAX. Why do we not include kernel inside our rootfs image? Why do we pass it seperately?08:34
*** zerocoolback has quit IRC08:37
*** zerocoolback has joined #kata-dev08:44
stefanhaniteshkonkar007: Maybe boot-from-NVDIMM doesn't work, I don't remember if the guest firmware supports it.08:55
stefanhaniteshkonkar007: If you tell the Kata Runtime to use a disk image then it should use NVDIMM (DAX) for the rootfs.08:56
stefanhaniteshkonkar007: Make sure your configuration.toml file has the path to the disk image.08:57
kata-irc-bot<niteshkonkar007> Yes, I know the approach of using rootfs instead of initrd. I was curious to know how the rootfs approach works in kata Vs the initrd approach(not enuf documentation on it) and why do we pass the kernel seperately and as part of the rootfs disk.08:59
stefanhaniteshkonkar007: Like I said, the kernel is probably separate because guest firmware cannot boot directly from NVDIMM.09:03
stefanhaniteshkonkar007: Regarding disk image vs initramfs.  On a host running multiple Kata VMs the disk image will be shared in the host page cache.09:03
*** zerocoolback has quit IRC09:04
stefanhaIf you use an initramfs then the memory is duplicated until Kernel Samepage Merging decides to deduplicate it.09:04
stefanhaniteshkonkar007: So there could be memory savings if you using a disk image.09:04
*** zerocoolback has joined #kata-dev09:11
*** zerocoolback has quit IRC10:06
*** eernst has quit IRC10:08
kata-irc-bot<niteshkonkar007> @stefanha: Thanks a lot for the info.10:38
*** zerocoolback has joined #kata-dev10:54
*** gwhaley has quit IRC11:02
*** devimc has joined #kata-dev11:54
*** gwhaley has joined #kata-dev12:18
*** fuentess has joined #kata-dev12:23
kata-irc-bot<salvador.fuentes> ping @caihaomin, hi, can you give me your github user so I can add the rebuild button for your user?12:26
*** dklyle_ has joined #kata-dev12:57
*** manjeets_ has joined #kata-dev12:58
*** david-lyle has quit IRC12:59
*** manjeets has quit IRC13:00
*** LinuxMe has joined #kata-dev13:11
*** lamego has joined #kata-dev13:33
*** zerocoolback has quit IRC13:40
*** zerocoolback has joined #kata-dev13:40
gwhaleyhey folks - in case any of the github org owners were wondering, that jenkins app that just requested org access was myself and @salvador.fuentess sorting our more wrinkles in the new CI13:41
*** zerocoolback has quit IRC13:42
*** zerocoolback has joined #kata-dev13:45
*** isaagar has quit IRC13:57
*** zerocoolback has quit IRC14:04
*** isaagar has joined #kata-dev14:06
*** annabelleB has joined #kata-dev14:11
*** annabelleB has quit IRC14:30
kata-irc-bot<caihaomin> @salvador.fuentes jshachm thx a lot14:37
kata-irc-bot<salvador.fuentes> @caihaomin can you check if you already have permissions?14:38
clarkbif anyone has a moment this morning, it would be helpful to understand why the cpu allotment tests seem to check for N+1 CPUs instead of just N cpus and pass under jenkins but fail under zuul.14:40
clarkbhttp://logs.openstack.org/74/74/3250f409797a162789a5078496b6977caaf319e8/third-party-check/kata-runsh/873d8f8/job-output.txt.gz#_2018-06-15_23_22_03_773254 shows the test for 2 cpus failing because it is actually looking for 3 cpus (cpus are zero indexed so cpu2 is third cpu)14:40
clarkbhttp://jenkins.katacontainers.io/job/kata-containers-tests-centos-7-4-master/3/console shows this test checking for 3 cpus instead of 2 under jenkins and passing (which makes it extra confusing)14:40
*** annabelleB has joined #kata-dev14:42
kata-irc-bot<caihaomin> It works thanks @salvador.fuentes14:46
kata-irc-bot<salvador.fuentes> @julio.montes ^^14:47
*** dklyle_ has quit IRC14:49
devimcclarkb, Hi14:51
devimcclarkb, https://github.com/kata-containers/documentation/blob/master/constraints/cpu.md14:51
*** sameo has quit IRC14:51
devimchttps://github.com/kata-containers/documentation/blob/master/constraints/cpu.md#do-not-waste-resources14:52
clarkbdevimc: (30000 + (20000 -1)) / 20000 = 2.49995 and the test is for 2 vcpus which seems to line up, but why check for 3 cpus in that case?14:56
clarkbdepends on rounding maybe?14:56
*** manjeets_ is now known as manjeets14:58
devimc(30000 + (20000 -1)) / 20000 = 2.49995 = 2vCPUs14:59
devimcclarkb, runtime will hot add 2 vCPUs14:59
devimcbut the VM already have 1 vCPUs14:59
clarkboh its addin that absolute value not bringing the total available to that value?14:59
devimcyes15:00
clarkbok that explains my confusion. Should probably update the test labels at the very least (it is checking for 3 cpus not 2)15:00
clarkbdoesn't explain why it fails under zuul though15:01
clarkbwhich log files would be helpful to debug that? docker and kata runtime?15:01
devimcclarkb, runtime and agent15:02
devimcsudo journalctl -b -t kata-proxy15:02
devimcsudo journalctl -b -t kata-runtime15:02
clarkbthanks, I'll start by grabbing that info15:02
clarkb(just thinking out loud here, it is odd to me that if you set the quota on an instance you would get more than that quota, as a user I would probably find this unintuitive. I would expect quota to be absolute not additive)15:09
devimcclarkb, why?15:17
clarkbdevimc: because quota is an explicit limit, if I set a quota that should be the limit15:17
devimcclarkb, yes, but you can also update that quota15:18
clarkbyup and that will be the new limit. The issue is that the limit I am setting is not the limit that is used15:18
devimcreally?15:19
devimcthat's weird15:19
clarkbdevimc: yes instead it is the quota I set + some default configuration value of the service I may not even know about (if I am consuming the service and not administrator of it)15:19
clarkbre journalctl about did you mean kata-runtime and kata-agent instead of kata-runtime and kata-proxy? or is the proxy equivalent to the agent for logging?15:20
devimckata-proxy contains agent logs15:21
devimcclarkb, but you have to add agent.log=debug as kernel parameter15:21
devimcin runtime configuration file15:21
devimckernel_params = "agent.log=debug"15:21
clarkbdevimc: I'm just running .ci/setup.sh && .ci/run.sh fwiw15:22
devimcohh15:22
devimcclarkb, please edit runtime configuration file15:23
devimcand enable debugging15:23
devimc\/usr/share/defaults/kata-containers/configuration.toml15:23
clarkbwill do thanks15:23
devimcclarkb, is http://logs.openstack.org/74/74/3250f409797a162789a5078496b6977caaf319e8/third-party-check/kata-runsh/873d8f8/job-output.txt.gz#_2018-06-15_23_29_31_744467  your log file?15:24
clarkbdevimc: yes15:24
devimcuhmmm I see15:25
*** dklyle has joined #kata-dev15:29
*** fiddletwix has joined #kata-dev15:37
clarkbdevimc: do you see something odd other than the tests failing?15:47
clarkblooks like it claims to enable all debug options in the config file already, I'm just going to make sure I collect the data15:47
devimcclarkb, yep15:48
devimccommand failed error 'exit status 1'15:49
devimcseems like vCPUs are not connected15:49
devimcwould you mind modifying a test and re-run them?15:49
clarkbdevimc: or not enough of them were connected. Another update may be to run nproc before the sysfs check (so that we can see it)15:50
clarkbdevimc: ya once I've got log collection going I think I will push an update to the test side to see if we can get more info there as well like ^15:50
kata-irc-bot<mnaser> fyi: clarkb is using the same exact vms we're using in jenkins.katacontainers.io15:51
kata-irc-bot<mnaser> so something to keep in mind15:51
devimcclarkb, ok, try modifying https://github.com/kata-containers/tests/blob/master/integration/docker/cpu_test.go#L24615:51
clarkbmnaser are you using our images? this is running on infra images which may be different15:51
devimcincrease that number15:51
clarkbflavor is the same though15:51
devimc10 or  1515:51
kata-irc-bot<mnaser> clarkb: images are different, using 100% 'upstream' images15:51
kata-irc-bot<mnaser> also, is this still on bionic or on xenial?  seems xenial is the stablest of the bunch15:52
clarkbxenial, switched when bionic wasn't working due to lack of docker-ce packages15:52
devimcclarkb, FOCUS="Update number of CPUs" RUNTIME=kata-runtime make -e integration15:52
clarkbI've asked it for a new run where it should collect logs, will see what that tells us then do test updates if necessary15:56
clarkbthank you for the help15:57
kata-irc-bot<salvador.fuentes> @mnaser, can you provide me a VM with 17.10 to check if the script I created can hang the machine?15:58
kata-irc-bot<mnaser> oh yes15:59
kata-irc-bot<mnaser> sure15:59
*** annabelleB has quit IRC16:00
kata-irc-bot<mnaser> @salvador.fuentes rebuild the same machine on same ip -- 162.253.55.17016:00
kata-irc-bot<salvador.fuentes> thanks @mnaser16:01
devimcclarkb, how many CPUs do you have?16:01
devimcyou need at least 416:02
clarkbdevimc: should be 8, it is the same flavor in vexxhost that jenkins is using16:02
clarkbdevimc: but I can double check that as well16:02
*** annabelleB has joined #kata-dev16:02
devimcclarkb, how much RAM?16:03
clarkbdevimc: 16GB iirc, mnaser is that right?16:04
kata-irc-bot<mnaser> devimc, clarkb: correct, same *exact* flavor16:14
devimcmnaser, ok16:18
devimcclarkb, probably you are doing something different16:19
clarkbdevimc: right now my hunch is something different in the images. Possibly a missing kernel module or different kernel version? On the job execution side I'm basically just installing build-essential, golang, and docker then running .ci/setup.sh && .ci/run.sh16:21
devimcclarkb, what version of docker?16:23
clarkbdevimc: oh sorry I don't install docker anymore, I was on bionic, but switched to xenial so that setup.sh can do it16:23
kata-irc-bot<mnaser> clarkb: in ci, we don't rely on setup.sh to install docker16:24
kata-irc-bot<mnaser> not sure if that has to do with anything16:24
*** gwhaley has quit IRC16:49
kata-irc-bot<anne> Would folks ping me or reply here if they intended to come to the Kata in-person meeting in September in Denver? (trying to get an approximate head count)17:04
*** jodh has quit IRC17:11
*** annabelleB has quit IRC17:17
*** annabelleB has joined #kata-dev17:22
*** sameo has joined #kata-dev17:27
*** dklyle has quit IRC17:36
*** dklyle has joined #kata-dev17:37
clarkbdevimc: Jun 18 17:23:18.467727 ubuntu-xenial-vexxhost-vexxhost-ca-ymq-1-0000202446 kata-runtime[22561]: time="2018-06-18T17:23:18.467708584Z" level=debug msg="the actual number of vCPUs will not be modified" arch=amd64 container-id=67cdc1f89636ef60a6e99aabade0105f213c12603ec176aef5ebde4c3bee1edd name=kata-runtime new-vcpus=0 old-vcpus=0 pid=2256117:48
clarkbsandbox-id=67cdc1f89636ef60a6e99aabade0105f213c12603ec176aef5ebde4c3bee1edd source=virtcontainers subsystem=container17:48
clarkbdevimc: seems to correspond to http://logs.openstack.org/74/74/8593bec79c873812b772d1de1d77ed63ebcb7c83/third-party-check/kata-runsh/44260b0/job-output.txt.gz#_2018-06-18_17_23_18_43306717:48
clarkbdevimc: other logs can be found at http://logs.openstack.org/74/74/8593bec79c873812b772d1de1d77ed63ebcb7c83/third-party-check/kata-runsh/44260b0/ and I think I held the node and shoul dhave access to it if we want to do more debugging17:49
clarkbhttps://github.com/kata-containers/runtime/blob/b3b0612fbeab7d89505d98beea6af609c0addbad/virtcontainers/container.go#L1160-L1165 produces that message17:50
clarkbthe value of 0 is special right? does this imply a configuration difference?17:50
clarkbmnaser ^ you may know17:50
devimcclarkb, I don't see agent logs17:52
devimcdid you enable it?17:52
clarkbdevimc: no, because setup.sh said it was enabling all debug flags in the configuration anyway (I guess it could be failing to do that for the proxy?)17:52
clarkbdevimc: but it seems the runtime is shortcircuiting due to the value being 017:52
clarkbhttp://logs.openstack.org/74/74/8593bec79c873812b772d1de1d77ed63ebcb7c83/third-party-check/kata-runsh/44260b0/job-output.txt.gz#_2018-06-18_17_15_58_033361 is why I didn't update the config17:53
clarkbI'm checking directly on the test node now17:54
clarkbkernel_params = " agent.log=debug" is set17:55
clarkbdefault_vcpus = 1 as well17:55
devimcclarkb, thta's weird17:56
devimclevel=debug msg="the actual number of vCPUs will not be modified" arch=amd64 container-id=67cdc1f89636ef60a6e99aabade0105f213c12603ec176aef5ebde4c3bee1edd name=kata-runtime new-vcpus=0 old-vcpus=017:56
devimcnew-vcpus=0 old-vcpus=017:56
devimcso, seems like you are trying to add 0 vcpus17:57
clarkbdevimc: ya and the old value is 0 as well (I would expect it to be 1)17:57
devimcno, that's ok17:57
devimc0 is because the container has not vcpus assigned17:58
devimcseems like docker is not giving the right number of vcpus to the runtime17:59
clarkbah17:59
* clarkb looks at docker log17:59
devimcprobably you are installing an old version of docker17:59
devimco_O ?17:59
clarkbmaybe? it is just using setup.sh for that. Let me find the log of that18:00
clarkbhttp://logs.openstack.org/74/74/8593bec79c873812b772d1de1d77ed63ebcb7c83/third-party-check/kata-runsh/44260b0/job-output.txt.gz#_2018-06-18_17_11_06_279339 17.12.1 ?18:00
*** dklyle has quit IRC18:00
clarkbDocker version 17.12.1-ce, build 7390fc6 says `docker --version`18:01
devimcclarkb, hehe yep18:01
devimcthat's the error18:01
devimcthat version of docker is broken18:01
clarkbok, that is what setup.sh provides...18:02
devimcI don't know18:02
devimcplease update it manually18:02
devimc> 1818:02
clarkbok let me see how to do that and then update .ci/setup.sh to do it18:03
devimcclarkb, http://jenkins.katacontainers.io/job/kata-containers-runtime-ubuntu-16-04-PR/37/consoleFull18:03
devimcAdd runtime as a new/default Docker runtime. Docker version "Docker version 18.03.1-ce, build 9ee9f40" could change according to updates.18:03
devimcI don't know what's going on18:04
devimcit's xenial but with docker >=1818:05
clarkbdevimc: ya mnaser mentioned earlier that the jenkins jobs install docker out of band. I think the proper fix here is to update .ci/setup.sh to do the thing that works then stop jenkins from overriding it at all18:05
clarkbdevimc: https://github.com/kata-containers/runtime/blob/master/versions.yaml#L130 is the problem18:13
devimcclarkb, you're right18:14
*** dklyle has joined #kata-dev18:26
clarkbdevimc: https://review.openstack.org/576178 is my current state. I will rerun that to confirm it fixes things, then we can figure out how to fix .ci/setup.sh so that jenkins (and anything else) can run it and test it18:41
devimcclarkb, cool :)18:51
*** davidgiluk has quit IRC19:19
*** annabelleB has quit IRC19:27
*** annabelleB has joined #kata-dev19:32
*** LinuxMe has quit IRC19:48
*** LinuxMe has joined #kata-dev19:49
*** devimc has quit IRC19:50
*** LinuxMe has quit IRC19:54
*** sameo has quit IRC20:01
*** LinuxMe_ has joined #kata-dev20:02
*** annabelleB has quit IRC20:42
*** annabelleB has joined #kata-dev20:43
*** annabelleB has quit IRC20:54
*** marst has joined #kata-dev21:17
*** fuentess has quit IRC21:26
*** LinuxMe_ has quit IRC21:27
*** LinuxMe has joined #kata-dev21:29
*** LinuxMe has quit IRC21:30
*** annabelleB has joined #kata-dev21:36
*** eernst has joined #kata-dev21:44
*** dklyle has quit IRC21:48
*** dklyle has joined #kata-dev21:50
*** devimc has joined #kata-dev22:05
*** eernst has quit IRC22:11
*** eernst has joined #kata-dev22:13
*** eernst has quit IRC22:18
*** eernst has joined #kata-dev22:18
*** dlw has joined #kata-dev22:21
*** dlw has quit IRC22:41
*** eernst has quit IRC22:47
*** dlw has joined #kata-dev22:50
*** lamego has left #kata-dev23:01
*** dklyle has quit IRC23:01
*** annabelleB has quit IRC23:05
*** dlw has quit IRC23:08

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