Monday, 2018-07-30

*** dlw has joined #kata-dev02:14
*** sjas_ has joined #kata-dev04:53
*** sjas has quit IRC04:56
*** dlw has quit IRC04:59
*** dlw has joined #kata-dev05:13
*** jodh has joined #kata-dev06:59
*** jodh has quit IRC06:59
*** jodh has joined #kata-dev06:59
*** lpetrut has joined #kata-dev07:20
*** sameo has joined #kata-dev07:23
*** simosx has joined #kata-dev07:45
*** davidgiluk has joined #kata-dev08:01
simosxAre there any ready-made images for use in Kata Containers? Preferably based on Ubuntu?08:07
*** gwhaley has joined #kata-dev08:08
*** sameo has quit IRC08:24
*** sameo has joined #kata-dev08:25
*** libregeekingkid has joined #kata-dev09:07
*** simosx has quit IRC09:15
*** sjas_ is now known as sjas10:02
*** libregeekingkid has quit IRC10:32
kata-irc-bot<ydjainopensource> @simosx I have a WIP PR. You may track it here https://github.com/kata-containers/osbuilder/pull/14410:56
*** gwhaley has quit IRC11:01
kata-irc-bot<zhangwei555> Where are our CI machines? I can't see the CI results11:07
*** dlw has quit IRC11:11
*** fuentess has joined #kata-dev11:41
*** fuentess has joined #kata-dev11:44
kata-irc-bot<salvador.fuentes> Hi, I talked to @mnaser yesterday to check why we are not able to launch new VMs, seems like there are many stale VMs in the vexxhost cloud that were not properly deleted. We'll need his help to remove all of them and after that we should be able to launch new machines11:49
*** devimc has joined #kata-dev11:52
*** sameo has quit IRC12:05
*** sameo has joined #kata-dev12:05
*** gwhaley has joined #kata-dev12:06
kata-irc-bot<zhangwei555> Get it, thanks! @salvador.fuentes12:08
*** mugsie has quit IRC12:49
*** mugsie has joined #kata-dev12:49
*** mugsie has quit IRC12:49
*** mugsie has joined #kata-dev12:49
*** lamego has joined #kata-dev13:16
* gwhaley wonders if both jodh and devimc are having sugar rush?14:04
jodhgwhaley: 12 spoons in a cuppa is the average right?14:05
jodhgwhaley: coz if so, I think I just broke a world record14:05
*** lamego has quit IRC14:12
*** fuentess has quit IRC14:13
devimc\o/14:13
*** fuentess has joined #kata-dev14:13
*** lamego has joined #kata-dev14:14
kata-irc-bot<salvador.fuentes> @channel hi, seems like we can start VMs on Jenkins again, but the jobs queued were lost, can you please re-push if you have a PR waiting for the CI14:23
*** dklyle has joined #kata-dev14:34
kata-irc-bot<james.o.hunt> Architecture Committee about to start: https://zoom.us/j/83713940515:00
*** eernst has joined #kata-dev15:18
kata-irc-bot<eric.ernst> @zhangwei555 ping?15:59
kata-irc-bot<zhangwei555> :)16:00
kata-irc-bot<eric.ernst> didn't dig through github yet.  you see the revert?16:01
kata-irc-bot<zhangwei555> yeah16:01
kata-irc-bot<zhangwei555> Debugging a bit during weekend, and pushed a new PR, now waiting for the CI16:02
kata-irc-bot<eric.ernst> ok, cool.16:02
kata-irc-bot<eric.ernst> we didn't get time to really bisect it on friday.16:02
kata-irc-bot<eric.ernst> i mean, beyond the merge commit.  Wanted to see which of your commits16:02
*** eernst has quit IRC16:03
kata-irc-bot<zhangwei555> Never mind. I guess it’s some problem caused by logic modification and some wrong K8S cleanup script. But still, I need the CI to verify my guess16:04
kata-irc-bot<niteshkonkar007> @james.o.hunt: Thanks for the reminder about the arch meeting. Can we `Set a reminder` on this kata channel for every arch/working committee meeting, so that ppl don't forget it?16:04
*** eernst_ has joined #kata-dev16:05
*** eernst_ has quit IRC16:06
*** eernst has joined #kata-dev16:06
*** sameo has quit IRC16:06
kata-irc-bot<james.o.hunt> @niteshkonkar007 - I'm not sure I've got privs to do that. But the best thing is probably to just add the Kata calendar to your own: https://katacontainers.io/16:06
*** unamed has joined #kata-dev16:07
*** unamed has quit IRC16:10
kata-irc-bot<salvador.fuentes> clarkb: hi, we have recently seen some `kata-runsh : NODE_FAILURE` from the zuul CI, is there a way to know what kind of failure did it occur? I ask because we also had some issues on jenkins launching new vms, and it seems that there were some stale VMs in the vexxhost cloud16:13
*** eernst has quit IRC16:16
*** eernst has joined #kata-dev16:16
*** eernst has quit IRC16:18
*** eernst has joined #kata-dev16:18
*** eernst has quit IRC16:18
*** eernst has joined #kata-dev16:18
clarkbsalvador.fuentes: the node failures are a failure to launch VMs since the vexxhost hypervisor is shared between jenkins and zuul that should go away when the stale VMs arw cleaned up16:20
*** jodh has quit IRC16:26
*** gwhaley has quit IRC17:00
kata-irc-bot<salvador.fuentes> clarkb: ok, thank you, so we can confirm we hit the same issue on both sides, also I was wondering why some VMs were not cleaned correctly :S17:05
*** eernst has quit IRC17:05
*** eernst has joined #kata-dev17:07
*** eernst has quit IRC17:07
*** eernst has joined #kata-dev17:07
*** lpetrut has quit IRC17:52
*** davidgiluk has quit IRC19:13
*** FL1SK has quit IRC20:27
*** devimc has quit IRC20:38
*** lpetrut has joined #kata-dev20:48
*** lpetrut has quit IRC20:52
*** fuentess has quit IRC20:59
*** lamego has left #kata-dev23:41

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