Tuesday, 2020-02-25

kata-irc-bot<xwlpt> @james.o.hunt I am trying kata-journald-host-redirect service to be installed at the guset VM. kata-journald-host-redirect02:27
kata-irc-bot<xwlpt> Is there any other service I need to be actived at the guest VM like journald?02:27
*** sameo has quit IRC03:00
*** kata-irc-bot4 has joined #kata-dev03:48
*** kata-irc-bot has quit IRC03:52
*** pcaruana has joined #kata-dev07:11
*** jodh has joined #kata-dev08:23
*** sgarzare has joined #kata-dev08:50
kata-irc-bot4<james.o.hunt> @xwlpt - yes, you would also need the journald service to be running (meaning you cannot trace in a standard initrd image). All this setup will go away when https://github.com/kata-containers/kata-containers/issues/60 lands along with the new agent of course :)08:59
*** gwhaley has joined #kata-dev09:02
*** sameo has joined #kata-dev09:02
kata-irc-bot4<xwlpt> @james.o.hunt Thanks for it. I am now working for how to export agent log to the host. 1. I don’t want agent log to sent to host by tty that means I can’t login to the VM by console because it will be occupied.  2.  In our env, we don’t want to install jager currently. So  I am trying this way, which means the host can get the agent’s log by vsock.09:03
kata-irc-bot4<xwlpt> I tried to enabled systemd-journald at my VM, but I still can’t see the stdout when I at the host by vsock-to-text-server.sh script.09:04
kata-irc-bot4<xwlpt> Still checking.09:04
kata-irc-bot4<james.o.hunt> @xwlpt - I am afraid the current tracing setup is very "delicate". You should be able to login using a debug console, but yes, you may end up with agent output on that console too. If all else fails, you could consider creating a "normal" qemu VM and running the golang agent first manually ("./kata-agent") and then as a systemd service on that VM. Obviously, this isn't a standard Kata environment but might help you debug what is09:50
kata-irc-bot4happening.09:50
*** gwhaley has quit IRC12:01
*** Finnix has joined #kata-dev12:08
Finnixhi2all12:08
Finnixi tried to install kata containers using this example: https://github.com/kata-containers/documentation/blob/master/install/centos-installation-guide.md, but seems repo have unmet deps, so installation failed. is there a workaround to given issue?12:09
Finnixinstallation process output: https://0x0.st/iqGy.txt12:09
Finnixwill use 1.10 branch, seems master is broken12:14
*** Finnix has left #kata-dev12:15
*** gwhaley has joined #kata-dev13:10
*** fuentess has joined #kata-dev13:15
kata-irc-bot4<graham.whaley> heh, @xu - I think the candidates were/are ordered alphabetically by default - which makes you last in the list no matter which name we sorted on! ;)13:42
kata-irc-bot4<xu> @graham.whaley aha, I know that :,) . Just kidding13:43
*** devimc has joined #kata-dev13:45
*** canyounot has joined #kata-dev13:46
*** crobinso has joined #kata-dev14:09
kata-irc-bot4<xu> @raravena80 looks some guys haven't got the voting mail, such as @weizhang555 , any ideas?15:00
kata-irc-bot4<graham.whaley> @xu - if you/they can supply the email addresses you think the mails should have gone to (maybe pm rico), that will help check against the auto-generated list - it tries to extract the emails from the github history/commits etc., but is probably not perfect (particularly if somebody has used more than one email address etc.). And, of course, check the spam filters ;)15:03
*** devimc has quit IRC15:20
*** devimc has joined #kata-dev15:21
kata-irc-bot4<raravena80> @xu send me their emails and I can check.15:25
*** irclogbot_2 has quit IRC15:27
*** irclogbot_0 has joined #kata-dev15:27
kata-irc-bot4<xu> Thanks @raravena80, I will confirm with them and sent the emails to you.15:47
*** jodh has quit IRC16:00
kata-irc-bot4<eric.g.ernst> :wave:16:23
kata-irc-bot4<eric.g.ernst> still alive16:23
kata-irc-bot4<eric.g.ernst> though i need to get my calendar fixed so I don't miss AC call :(16:23
kata-irc-bot4<xu> I think what you need is alarm on your phone :,)16:27
fidencio resets the error, which is not what we want here -16:44
fidenciooops, wrong paste, sorry :-)16:45
kata-irc-bot4<xu> no problem (though I didn't notice that.... sorry)16:45
*** crobinso has quit IRC16:59
*** pcaruana has quit IRC17:50
*** pcaruana has joined #kata-dev18:00
*** pcaruana has quit IRC18:06
*** igordc has joined #kata-dev18:10
*** amorenoz has quit IRC18:21
*** amorenoz has joined #kata-dev18:38
*** sgarzare has quit IRC18:51
*** amorenoz has quit IRC19:04
*** igordc has quit IRC19:17
*** sgarzare has joined #kata-dev19:48
*** igordc has joined #kata-dev19:49
kata-irc-bot4<crobinso> forgive me if this is a dumb question but I'm pretty new to the modern github workflow: what processes PR comments like '/test' and where can I see the results?20:00
kata-irc-bot4<crobinso> For example, looking at this PR which has a similar '/test-ubuntu' comment: https://github.com/kata-containers/osbuilder/pull/41020:01
kata-irc-bot4<fidencio> @archana.m.shinde hey / ping. Mrunal told me you could help us running the kubernetes tests using kata. What's the easiest way to: • Change the runtime to use kata, in all possible tests; • Set pod overhead, • The list of the tests that are expected to no pass (is there some way to tweak that when running the E2E kubernetes tests?)20:17
kata-irc-bot4<fidencio> @crobinso, it's usually done using a bot. I'm not sure where you could check the available commands, tho.20:17
kata-irc-bot4<graham.whaley> hi @crobinso - kata has tried to document the triggers we have for the CI on a wiki page at https://github.com/kata-containers/community/wiki/Controlling-the-CI  (the jumpoff to that wiki page is on the home page README of the ci repo).20:31
kata-irc-bot4<graham.whaley> the triggers are handled by a number of CIs we have - Jenkins, Zuul, github Actions, maybe Azure. Yeah, there is a mix20:31
kata-irc-bot4<graham.whaley> and.... you may not be able to trigger them (all) if you are not a member of the kata github org - just in case you fire some and they don't...20:32
kata-irc-bot4<graham.whaley> oh, and the results of the CI runs are usually found from the hot-links of the CI status reported at the end of the PR - the github 'status' section...20:33
kata-irc-bot4Action: graham.whaley going to sign off in a minute, so I'll witter on a little then....20:34
kata-irc-bot4<graham.whaley> so, the phrases like `/test-ubuntu`, in that specific case, are coded into the jenkins github integration module, via the Jenkins UI. You can find those triggers is you know where to look in the Jenkins xml that is backed up in the ci repo - but that is a pain, which is why we created that wiki page, for when we forget what they are ;)20:35
*** gwhaley has quit IRC20:37
*** crobinso has joined #kata-dev20:56
*** sgarzare has quit IRC21:00
kata-irc-bot4<crobinso> @graham.whaley @fidencio thanks for the info21:01
*** igordc has quit IRC21:08
*** igordc has joined #kata-dev21:16
*** igordc has quit IRC21:18
*** igordc has joined #kata-dev21:18
*** crobinso has quit IRC21:24
*** igordc has quit IRC21:26
*** canyounot has quit IRC22:00
*** fuentess has quit IRC22:08
kata-irc-bot4<archana.m.shinde> @fidencio This is the script that we use to run e2e tests: https://github.com/kata-containers/tests/blob/c67e0c88a46a3b20fecc91a8450f8af6d4b92246/integration/kubernetes/e2e_conformance/run.sh22:24
kata-irc-bot4<fidencio> What's sonobuoy? Seems to be needed to run the tests.22:27
kata-irc-bot4<fidencio> And i kind of missed where we force kata as the runtime used in the tests22:28
kata-irc-bot4<fidencio> Hmm. I see. For each of the supported tests, you have your own yaml, which has kata as the runtime22:31
kata-irc-bot4<fidencio> (looking at: https://github.com/kata-containers/tests/tree/c67e0c88a46a3b20fecc91a8450f8af6d4b92246/integration/kubernetes/runtimeclass_workloads)22:31
kata-irc-bot4<archana.m.shinde> @fidencio that script calls into this webhook : https://github.com/kata-containers/tests/tree/c67e0c88a46a3b20fecc91a8450f8af6d4b92246/kata-webhook22:32
kata-irc-bot4<archana.m.shinde> it is basically an admission controller that makes sure the workload runs with kata22:32
kata-irc-bot4<fidencio> Cool, I'll dig into those Tomorrow. Thanks for the pointers!22:34
kata-irc-bot4<archana.m.shinde> as for the pod overhead, you can take a look at this PR that we merged recently : https://github.com/kata-containers/tests/pull/224322:34
kata-irc-bot4<fidencio> Aha, perfect!22:34
kata-irc-bot4<archana.m.shinde> sure, let us know if you run into any issues22:35
*** devimc has quit IRC23:42

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