Tuesday, 2019-03-05

*** stackedsax has joined #kata-dev00:47
*** sameo has joined #kata-dev05:04
kata-irc-bot<eric.ernst> @xu @bergwolf @zhangwei555 anything for agenda tomorrow?05:15
kata-irc-bot<zhangwei555> Nothing from me05:16
kata-irc-bot<eric.ernst> If not, we may be able to just do offline -- there isn't anything on etherpad agenda at this pointn.05:17
kata-irc-bot<eric.ernst> @xu you want to make a call and send email to distro if you think we can/should skip?05:17
kata-irc-bot<eric.ernst> And, if any ya'll have ideas, it05:18
kata-irc-bot<eric.ernst> 'd be good to get items on https://etherpad.openstack.org/p/Kata_Denver_Forum_Topics05:18
kata-irc-bot<xu> Just an info --- China community is preparing to organize a second hackthon with kata included, I’d like to ask if any member have chance to travel to Shenzhen, China in April. More info may come later this week.06:12
kata-irc-bot<xu> And I don’t have any other serious thing to go through in the meeting06:13
kata-irc-bot<bergwolf> nothing in my head either. feel free to skip it if you guys all agree.06:24
*** dims has quit IRC06:24
*** dims has joined #kata-dev06:26
*** sameo has quit IRC06:28
*** dims has quit IRC06:36
eguanarchana.m.shinde: thanks for the reply! Yes, exec hook works, I can see it work with curl command too, but http hook doesn't work for me06:44
eguani.e. this works06:44
eguan      postStart:06:44
eguan        exec:06:44
eguan          command: ["/bin/sh", "-c", "curl http://172.16.3.112:8080/echo?msg=poststart"]06:44
eguanbut this doesn't06:44
eguan        httpGet:06:44
eguan          host: 172.16.3.11206:44
eguan          path: "echo?msg=poststart"06:44
eguan          port: 808006:44
*** sameo has joined #kata-dev06:59
*** tmhoang has joined #kata-dev07:44
*** sameo has quit IRC08:02
*** sgarzare has joined #kata-dev08:11
*** jodh has joined #kata-dev08:34
*** davidgiluk has joined #kata-dev09:00
*** gwhaley has joined #kata-dev09:00
*** sameo has joined #kata-dev09:16
kata-irc-bot<xwlpt> I use attach a scsi device to the VM manually. But I found that there is no device file under dir `/dev/`. Is there anything need to be configured?  This behavior is used to support `-v device : device` running parameter, but If there is no device file under `/dev`, it should not work.09:19
kata-irc-bot<xwlpt> @archana.m.shinde09:25
kata-irc-bot<afrosi> hi, we saw an issue with the installation scripts of Kata on s390x. Kata is set as default runtime with docker. However, the testsuite builds the `vish/stress`. However, it is using kata as default runtime for building and it hangs. I was wondering if some of us experience the same behavior? @niteshkonkar007 ?09:50
kata-irc-bot<graham.whaley> @xwlpt - I think @archana.m.shinde might be the best person to answer. I suspect what needs to happen is the agent 'spots' the new device being plugged in, the (guest) kernel should probably have made the device nodes, and the agent then would do the mount.... maybe have a look in the guest `dmesg` to see if you can see your disk turning up in the kernel??10:25
kata-irc-bot<graham.whaley> @afrosi - I know there are some docker images that will not build when kata is the default runtime iirc, but what I don't understand for the vish/stress case is how/why that would work on x86 and not other arch's :slightly_smiling_face: I don't think we special case x86 iyswim10:26
kata-irc-bot<afrosi> My guess is that is related to this PR https://github.com/kata-containers/tests/pull/111410:28
kata-irc-bot<afrosi> but I still need to dig into it. It could just helped if you had already the same issue10:29
kata-irc-bot<xwlpt> @graham.whaley thanks. I checked the log. It seems udev has issues.10:49
kata-irc-bot<xwlpt>10:49
kata-irc-bot<xwlpt> cc @archana.m.shinde10:49
kata-irc-bot<xwlpt> Actually the device file had been created in `/dev`, but then it gone.'10:49
kata-irc-bot<xwlpt> Logs of `udevadm monitor`10:51
kata-irc-bot<xwlpt>10:51
*** sameo has quit IRC10:56
*** dims has joined #kata-dev11:01
kata-irc-bot<niteshkonkar007> @afrosi: Did that PR link help?11:50
kata-irc-bot<afrosi> My point is if we set kata as default, then it is sued also for building. I don't think it's what we want. So I wanted to know if you had the same issue. In order to build the `virsh/stress` image we need runc as default. Your PR is prefectly fine. The problem is on the flow. If we install kata as defaul runtime, then we cannot use it for building. At least that is my understanding11:54
*** sameo has joined #kata-dev11:55
*** gwhaley has quit IRC11:59
kata-irc-bot<niteshkonkar007> Yes. I remember facing the same issue..12:02
*** sameo has quit IRC12:07
kata-irc-bot<afrosi> Probably the best approach would be to leave runc as default runtime and set kata with "--runtime"?13:06
*** gwhaley has joined #kata-dev13:08
*** fuentess has joined #kata-dev13:16
*** devimc has joined #kata-dev13:19
kata-irc-bot<niteshkonkar007> @afrosi: Although I remember facing that issue but 1. I ran the test locally on ppc64le and docker build worked just fine 2. Kata CI on Power could also build the stress image fine. Logs here: http://jenkins.katacontainers.io/job/kata-containers-proxy-Power8-16.04-PR-initrd/85/consoleFull (grep for stress image) 3. This is arch neutral issue. So if it worked on x86, should work on other archs as well.13:25
*** devimc has quit IRC13:34
*** devimc has joined #kata-dev13:39
kata-irc-bot<xu> @heNo agenda items here, so we skip the AC meeting this week But please submit forum proposal for Denver Summit if you have any topic by March 8. See the agenda of last week13:45
kata-irc-bot<xu> No agenda items here, so we skip the AC meeting this week But please submit forum proposal for Denver Summit if you have any topic by March 8. See the agenda of last week13:46
*** dklyle has joined #kata-dev14:13
*** devimc_ has joined #kata-dev14:28
*** devimc has quit IRC14:32
*** jugs has quit IRC15:07
*** jugs has joined #kata-dev15:07
*** devimc_ has quit IRC15:10
kata-irc-bot<eric.ernst> I usually don't set Kata as default to avoid docker build issues in particular.15:48
gwhaley@eric.ernst: indeed - but I think this discussion is about the CI systems, where I think kata is installed as the default (sorry, slack being slow here, replying via irc..)15:53
*** jodh has quit IRC16:03
*** jugs1 has joined #kata-dev16:03
*** devimc has joined #kata-dev16:03
*** jugs has quit IRC16:04
*** devimc has quit IRC16:10
*** tmhoang has quit IRC16:25
*** devimc has joined #kata-dev16:27
*** devimc has quit IRC17:02
*** devimc has joined #kata-dev17:04
kata-irc-bot<graham.whaley> Hi @salvador.fuentes - I just threw a set of patches into our Zuul tennant gerrit to enable a QA CI job, so I can then base metrics and maybe some version/CVE/nagbot checking off it as well. So, fyi https://review.openstack.org/#/c/641086 - would appreciate if you want to cast your eyes over it. /cc @thierry for good measure as well ;-017:07
*** sgarzare has quit IRC17:10
*** sameo has joined #kata-dev17:12
kata-irc-bot<salvador.fuentes> hi @graham.whaley, sure, let me take a look17:12
kata-irc-bot<graham.whaley> np - no real rush, I gotta fix a syntax error in it to start with ;)17:13
kata-irc-bot<salvador.fuentes> although I got a 503 error17:13
kata-irc-bot<graham.whaley> ah, hmm, maybe you have to log into gerrit with the ubuntu id etc.17:13
kata-irc-bot<graham.whaley> I would not have thought so though. ah, hold on, you are not suffering the same network issues @julio.montes is seeing are you btw??17:14
kata-irc-bot<salvador.fuentes> mmm, I dont think so, I'm clicking on my windows machine17:14
kata-irc-bot<salvador.fuentes> now it is working17:15
kata-irc-bot<graham.whaley> heh - <blip>17:15
*** devimc has quit IRC17:52
kata-irc-bot<archana.m.shinde> @xwlpt Since you are manually attaching the device, the device will not appear in the mount namespace of the container. if you do a lsblk, you will likely see the device. The agent needs to be explicitly sent a request by the runtime to add the device. See this: https://github.com/kata-containers/agent/blob/173bb55625d059b6d3270826c76fde4eb6d28615/device.go#L42317:57
kata-irc-bot<archana.m.shinde> Today if you want to pass a qcow image, the way to do that would be to mount the qcow on saw a loop device and then you can pass the device as --device device:device or `-v  device:device`18:00
*** devimc has joined #kata-dev18:40
*** devimc has quit IRC19:31
*** devimc has joined #kata-dev19:33
*** davidgiluk has quit IRC20:14
*** igordc has joined #kata-dev20:28
*** gwhaley has quit IRC20:36
*** sameo has quit IRC20:36
*** eernst has joined #kata-dev21:25
*** eernst has quit IRC21:40
*** eernst_ has joined #kata-dev21:40
*** eernst_ has quit IRC21:46
*** eernst has joined #kata-dev21:56
*** eernst has quit IRC21:58
*** fuentess has quit IRC22:28
*** devimc has quit IRC22:33
*** igordc has quit IRC23:10

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