Tuesday, 2020-06-30

*** crobinso has quit IRC00:28
*** ericernst has quit IRC00:31
*** amorenoz has quit IRC01:13
*** amorenoz has joined #kata-dev01:33
*** bpradipt has joined #kata-dev03:55
*** bpradipt has quit IRC04:42
*** bpradipt has joined #kata-dev05:02
*** sameo has joined #kata-dev05:18
*** dklyle has quit IRC06:13
*** jodh has joined #kata-dev07:14
*** hashar has joined #kata-dev07:24
*** jodh has quit IRC07:35
*** jodh has joined #kata-dev07:36
*** davidgiluk has joined #kata-dev08:04
kata-irc-bot<fidencio> @bergwolf, about the shimv2 log levels, is there a specification that we follow for that? or at least for the supported command line options?08:16
kata-irc-bot<bergwolf> I don’t think there is any log level specification. what are you trying to solve?08:34
kata-irc-bot<fidencio> The pain of shimv2 logs becoming useless, as either I have too many of those, or don't have logs at all.08:36
kata-irc-bot<fidencio> What I'd like to see is info logs, for instance, without having to enable the debug log level08:37
kata-irc-bot<fidencio> Right now, we explicitly pass "-debug" to the binary. What I'd prefer is having something as "--log-level [info|debug|warn|...]"08:38
kata-irc-bot<fidencio> and, preferably, have that info de-coupled from crio/containerd08:39
kata-irc-bot<fidencio> Actually, let me file an issue for that08:49
kata-irc-bot<bergwolf> Does containerd log level affect kata? Looks like we need a way for containerd to pass the log level information down to kata08:49
kata-irc-bot<fidencio> First things we need is shimv2 being able to accept any log level, and not only "debug"08:50
kata-irc-bot<bergwolf> for `--debug` we can set to `debug` level and non `--debug` we set to `info` level by default?08:50
kata-irc-bot<bergwolf> maybe we can add a shimv2 config option to set loglevel08:51
kata-irc-bot<fidencio> currently CRI-O (not sure about containerd) will pass down "-debug" to shimv208:51
kata-irc-bot<bergwolf> then shimv2 can find out the log level via config options not command line options08:52
kata-irc-bot<fidencio> which config option?08:53
kata-irc-bot<fidencio> Let me open an issue, we keep the discussion there. :slightly_smiling_face:08:54
kata-irc-bot<bergwolf> shimv2 API CreateTaskRequest has a `Options` field08:56
kata-irc-bot<bergwolf> we use it to pass kata shimv2 options08:56
kata-irc-bot<fidencio> Aha, that could be an option, indeed!08:58
kata-irc-bot<fidencio> https://github.com/kata-containers/kata-containers/issues/36609:05
*** mugsie has quit IRC10:07
*** mugsie has joined #kata-dev10:10
*** hashar has quit IRC10:47
*** hashar has joined #kata-dev12:22
*** vgoyal has joined #kata-dev12:25
*** devimc has joined #kata-dev12:27
*** crobinso has joined #kata-dev13:26
*** devimc has quit IRC13:29
*** devimc has joined #kata-dev13:29
devimcfidencio: oi, boa tarde14:16
devimcfidencio: i'm trying to build a static qemu using an ubuntu 20 container on RHEL 8, but it's failing resolving *.ubuntu.com14:17
devimchttp://jenkins.katacontainers.io/job/kata-containers-runtime-rhel-8-q35-PR/45/console14:17
devimcany thoughts?14:17
devimcStep 7/19 : RUN apt-get update && apt-get upgrade -y14:17
devimc ---> Running in d28a0e2078ed14:17
devimcErr:1 http://security.ubuntu.com/ubuntu focal-security InRelease14:17
devimc  Temporary failure resolving 'security.ubuntu.com'14:17
kata-irc-bot<fidencio> Are you using a *local* el8 box or azure powered one?14:19
kata-irc-bot<fidencio> seems like DNS / network not working as expected14:20
kata-irc-bot<fidencio> Considering I can access security.ubuntu.com here without any issue14:20
fidenciodevimc: if you can allow me to jump in that machine, I can try to debug this issue14:25
devimcfidencio: it's failing on azure, let me setup a VM14:27
kata-irc-bot<bergwolf> @fidencio could you take another look ? https://github.com/kata-containers/kata-containers/pull/36214:40
fidencio@bergwolf, acked!14:42
*** dklyle has joined #kata-dev14:43
*** jodh has quit IRC15:00
*** bpradipt has quit IRC15:11
*** bpradipt has joined #kata-dev15:14
*** hashar is now known as hasharAway15:24
*** devimc has quit IRC15:51
*** devimc has joined #kata-dev15:53
*** hasharAway is now known as hashar15:58
*** Yarboa has quit IRC16:14
*** Yarboa has joined #kata-dev16:29
*** hashar is now known as hasharAway17:40
*** hasharAway is now known as hashar19:01
*** davidgiluk has quit IRC19:26
*** bpradipt has quit IRC19:33
fidenciodevimc: is 2.0-dev supposed to support the go agent?19:47
fidencioseems that not, but somehow it comes as a surprise to me19:47
kata-irc-bot<fidencio> @bergwolf ^^19:48
devimcfidencio: yeah it works, but we won't supported19:49
devimc*support it19:50
fidenciodevimc: does it actually work? I mean, was it ever tested before?19:50
devimcrust agent will be the new agent19:50
devimcfidencio: uhmm I haven't tested the latest changes19:51
fidenciodevimc: https://github.com/kata-containers/kata-containers/issues/336#issuecomment-65200372119:52
fidenciotake a look at case 3, the error sounds like there's no communication with the agent19:52
devimcfidencio: right19:53
devimcfidencio: did you build the image?19:53
devimcfidencio: could you run a quick test using the image from here http://jenkins.katacontainers.io/job/image-nightly-x86_64/lastSuccessfulBuild/artifact/artifacts/19:54
devimc?19:54
fidenciodevimc: I can, but I'm using Fedora kernel and my own initrd which just works for the cases 1 and 219:54
*** hashar is now known as hasharAway19:55
devimcuhmm19:55
fidenciodevimc: so, I'm not exactly sure how the image would make a difference19:55
devimcfidencio: kernel http://jenkins.katacontainers.io/job/kernel-nightly-x86_64/19:55
fidenciodevimc: still, why could it cause different results?19:56
fidenciowhat I'm trying to do is isolate as much variables as possibles right now19:56
fidenciousing the very same kernel / initrd / cri-o / crictl ... meaning that the only thing that changed was the shimv2 binary19:57
devimcright19:58
fidenciobtw the question is sincere and not pushing back on your suggestion, do you think the image / kernel could have some effect on this? why?19:59
devimcnop, I think you're right20:00
devimcwill be the same20:00
fidenciookay, just to be sure I'm not going crazy here.20:01
fidencioI'll stop for Today and will get back to 2.0-dev branch, bisecting it20:01
fidencioA problem I foresee is that not every commit in that branch may be buildable20:02
fidenciobut let's hope for the best :-)20:02
*** Yarboa has quit IRC20:12
*** Yarboa has joined #kata-dev20:25
*** hasharAway has quit IRC20:28
*** hashar has joined #kata-dev20:29
*** devimc has quit IRC20:55
*** sameo has quit IRC21:08
*** jbryce has quit IRC21:15
*** jbryce has joined #kata-dev21:15
*** sameo has joined #kata-dev21:30
*** david-lyle has joined #kata-dev21:34
*** dklyle has quit IRC21:35
*** david-lyle is now known as dklyle21:37
*** crobinso has quit IRC21:39
*** hashar has quit IRC22:07
*** sameo has quit IRC23:42
*** vgoyal has quit IRC23:43

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!