| *** sameo has quit IRC | 00:03 | |
| *** zerocoolback has quit IRC | 00:31 | |
| *** zerocoolback has joined #kata-dev | 00:43 | |
| *** zerocoolback has quit IRC | 00:50 | |
| *** annabelleB has joined #kata-dev | 00:59 | |
| *** annabelleB has quit IRC | 01:17 | |
| *** dlw has joined #kata-dev | 01:58 | |
| *** dlw has quit IRC | 02:15 | |
| *** dlw has joined #kata-dev | 02:15 | |
| *** fuentess has quit IRC | 02:20 | |
| *** psuriset has quit IRC | 02:42 | |
| *** zerocoolback has joined #kata-dev | 02:44 | |
| *** zerocoolback has quit IRC | 02:50 | |
| *** psuriset has joined #kata-dev | 02:55 | |
| *** eernst has joined #kata-dev | 02:57 | |
| *** zerocoolback has joined #kata-dev | 03:09 | |
| *** sjas_ has joined #kata-dev | 04:22 | |
| *** sjas has quit IRC | 04:25 | |
| *** eernst has quit IRC | 05:22 | |
| *** jodh has joined #kata-dev | 07:09 | |
| *** cdent has joined #kata-dev | 07:27 | |
| *** gwhaley has joined #kata-dev | 07:59 | |
| *** davidgiluk has joined #kata-dev | 08:00 | |
| *** sameo has joined #kata-dev | 08:04 | |
| *** cdent has quit IRC | 08:09 | |
| *** zerocoolback has quit IRC | 09:56 | |
| *** sameo has quit IRC | 10:25 | |
| *** cdent has joined #kata-dev | 10:44 | |
| *** gwhaley has quit IRC | 11:07 | |
| *** jodh has quit IRC | 11:26 | |
| *** jodh has joined #kata-dev | 11:26 | |
| *** dlw has quit IRC | 11:48 | |
| kata-irc-bot | <zhangwei555> All PRs are failing due to a "invalid URL" problem, can we merge the fix first to make our CI happy? https://github.com/kata-containers/runtime/pull/392 @sebastien.boeuf @bergwolf @eric.ernst | 11:53 |
|---|---|---|
| *** zerocoolback has joined #kata-dev | 11:58 | |
| *** zerocoolback has quit IRC | 11:58 | |
| *** zerocoolback has joined #kata-dev | 11:59 | |
| kata-irc-bot | <thierry> @mnaser @salvador.fuentes @eric.ernst @anne @sebastien.boeuf jenkins.katacontainers.io created, pointing to 199.204.45.34 as requested | 12:05 |
| kata-irc-bot | <zhangwei555> Wow, thanks! I'll create a new PR to test if the new domain name works! | 12:17 |
| *** isaagar has joined #kata-dev | 12:21 | |
| *** fuentess has joined #kata-dev | 12:24 | |
| kata-irc-bot | <james.o.hunt> @thierry - thanks *very* much! :) | 12:33 |
| kata-irc-bot | <zhangwei555> Hmmm, weird, http://199.204.45.34:8080/job/kata-containers-runtime-ubuntu-16-04-PR/ works, but neither http://jenkins.katacontainers.io/job/kata-containers-runtime-ubuntu-16-04-PR/ nor http://jenkins.katacontainers.io:8080/job/kata-containers-runtime-ubuntu-16-04-PR/ works . Maybe the domain name need some time to take effect? | 12:33 |
| *** gwhaley has joined #kata-dev | 12:35 | |
| kata-irc-bot | <salvador.fuentes> seem like it is being redirected to the main page on 199.204.45.34 | 12:37 |
| kata-irc-bot | <thierry> @zhangwei555: the name correctly resolves to the IP, so must be some higher layer redirection yes | 12:44 |
| kata-irc-bot | <thierry> (although you may also suffer from DNS cache since it was just added) | 12:44 |
| kata-irc-bot | <mnaser> @zhangwei555 please drop the 8080 in it if possible -- http://jenkins.katacontainers.io/job/kata-containers-runtime-ubuntu-16-04-PR/ -- works for me | 13:02 |
| kata-irc-bot | <mnaser> also thanks for adding it @thierry | 13:04 |
| kata-irc-bot | <mnaser> @zhangwei555 the job failed saying : http://jenkins.katacontainers.io/job/kata-containers-runtime-ubuntu-16-04-master/badge/icon is invalid | 13:06 |
| kata-irc-bot | <mnaser> i wonder why | 13:06 |
| kata-irc-bot | <thierry> Credits to @verytired1 for adding it, I'm just the messenger circling back. | 13:13 |
| *** devimc has joined #kata-dev | 13:18 | |
| kata-irc-bot | <salvador.fuentes> I have updated the Jenkins permissions, so anyone inside the kata-containers org can now run/rebuild jobs. Let me know if you have any other issue | 13:25 |
| gwhaley | @salvador.fuentes: the only other thing I noted is I think the new jenkins is triggering jobs on every PR comment, and not just commit updates. I think that is either a hook config at the github end or | 13:28 |
| gwhaley | a Jenkins plugin setting - I forget which! | 13:28 |
| kata-irc-bot | <salvador.fuentes> @graham.whaley ahh, thanks for the notice, taking a look | 13:30 |
| *** eernst has joined #kata-dev | 13:31 | |
| kata-irc-bot | <james.o.hunt> @graham.whaley - wow, that takes CI to a new level eh!? ;) | 13:36 |
| *** lamego has joined #kata-dev | 13:37 | |
| kata-irc-bot | Action: mnaser is sad we haven't gotten a full clean job run yet | 13:37 |
| kata-irc-bot | <salvador.fuentes> @graham.whaley webhooks fixed :slightly_smiling_face: | 13:42 |
| *** dlw has joined #kata-dev | 13:46 | |
| kata-irc-bot | <mnaser> looks like someone shutdown jenkins | 14:22 |
| kata-irc-bot | <salvador.fuentes> @mnaser, yes, that was me | 14:23 |
| kata-irc-bot | <mnaser> cool no worries | 14:23 |
| kata-irc-bot | <mnaser> as long as it's expected :P | 14:23 |
| kata-irc-bot | <zhangwei555> Yes, But I see the the URL is fixed :fireworks: | 14:23 |
| kata-irc-bot | <salvador.fuentes> @mnaser, although I can only access through 8080 now :( | 14:24 |
| kata-irc-bot | <mnaser> you reboot the machine? | 14:24 |
| kata-irc-bot | <mnaser> its an iptables rule i had but i forgot to save it | 14:24 |
| kata-irc-bot | <mnaser> `sudo iptables -A PREROUTING -t nat -p tcp --dport 80 -j REDIRECT --to-ports 8080` | 14:24 |
| kata-irc-bot | <mnaser> fixed | 14:24 |
| kata-irc-bot | <salvador.fuentes> @mnaser, yes I rebooted it, thanks | 14:24 |
| kata-irc-bot | <salvador.fuentes> I can access now :slightly_smiling_face: | 14:25 |
| *** mnaser has left #kata-dev | 14:25 | |
| *** dlw has quit IRC | 14:32 | |
| *** sameo has joined #kata-dev | 14:51 | |
| *** zerocoolback has quit IRC | 15:17 | |
| *** annabelleB has joined #kata-dev | 15:58 | |
| *** lamego1 has joined #kata-dev | 16:21 | |
| *** lamego has quit IRC | 16:24 | |
| *** gwhaley has quit IRC | 16:54 | |
| *** eernst has quit IRC | 16:59 | |
| *** eernst has joined #kata-dev | 16:59 | |
| *** jodh has quit IRC | 17:05 | |
| *** eernst has quit IRC | 17:32 | |
| *** annabelleB has quit IRC | 17:43 | |
| *** eernst has joined #kata-dev | 17:46 | |
| *** devimc has quit IRC | 17:59 | |
| kata-irc-bot | <jdandrea> @eric.ernst Hmm... almost 24 hours later: | 18:17 |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB71Z17A6/-.js / https://slack-files.com/T86U7NQTT-FB71Z17A6-b1372b0be0 | 18:17 |
| kata-irc-bot | <eric.ernst> still alive? | 18:17 |
| kata-irc-bot | <jdandrea> Yes (I left it running top). | 18:18 |
| kata-irc-bot | <jdandrea> But no label. | 18:18 |
| kata-irc-bot | Action: jdandrea forgets how to keep the ccloudvm instance from stopping once exiting... looking that up... | 18:18 |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB6FCTQ7K/-.pl / https://slack-files.com/T86U7NQTT-FB6FCTQ7K-08d24565fd | 18:19 |
| kata-irc-bot | <jdandrea> Just to be sure. | 18:19 |
| kata-irc-bot | <eric.ernst> Ah i see - are the pods running? kubectl get pods -n kube-system | 18:36 |
| kata-irc-bot | <jdandrea> @eric.ernst Yup. | 18:40 |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB7UP1BV4/-.txt / https://slack-files.com/T86U7NQTT-FB7UP1BV4-54398b227f | 18:40 |
| kata-irc-bot | <krsna1729> @jdandrea doesnt seem to be running the daemonset. did you untaint the master in case this is a single-node cluster? | 18:43 |
| kata-irc-bot | <jdandrea> I did indeed untaint the master node. | 18:47 |
| kata-irc-bot | <eric.ernst> can you describe the pod? | 18:47 |
| kata-irc-bot | <eric.ernst> in particular, the labeler one... | 18:48 |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB76RRXFX/-.pl / https://slack-files.com/T86U7NQTT-FB76RRXFX-39bfc70954 | 18:50 |
| kata-irc-bot | <jdandrea> Which pod is the labeler? | 18:51 |
| kata-irc-bot | <jdandrea> Or do you mean the daemonset "kubelet-runtime-labeler" ? | 18:52 |
| kata-irc-bot | <jdandrea> Interesting side note: "get ds" results in "No resources found." yet as you can see from earlier the three daemonset.apps entries were configured. | 18:54 |
| kata-irc-bot | <jdandrea> hmm | 18:54 |
| *** devimc has joined #kata-dev | 18:55 | |
| kata-irc-bot | <eric.ernst> Ah, I don't even see it running/scheduled. Not sure what's happening there. | 18:57 |
| kata-irc-bot | <krsna1729> you need to apply `kata-rbac.yaml` first | 19:00 |
| kata-irc-bot | <krsna1729> i think | 19:00 |
| kata-irc-bot | <jdandrea> Hmm. @eric.ernst our instructions didn't use kata-rbac.yaml, do I need a link for that too? | 19:00 |
| kata-irc-bot | <eric.ernst> Ah. We split this out last night. | 19:01 |
| kata-irc-bot | <jdandrea> I'm just applying https://raw.githubusercontent.com/egernst/kata-deploy/master/kata-deploy.yaml | 19:01 |
| kata-irc-bot | <eric.ernst> or, yester-afternoon. | 19:01 |
| kata-irc-bot | <jdandrea> ok | 19:01 |
| kata-irc-bot | <eric.ernst> Checkout the new readme | 19:01 |
| kata-irc-bot | <jdandrea> ok | 19:01 |
| *** annabelleB has joined #kata-dev | 19:01 | |
| kata-irc-bot | <eric.ernst> https://github.com/egernst/kata-deploy/blob/master/README.md | 19:01 |
| kata-irc-bot | <jdandrea> Ok, so I'd just prepend https://raw.githubusercontent.com/egernst/kata-deploy/master/ in front of that? | 19:02 |
| kata-irc-bot | <jdandrea> Or I can just use https://github.com/egernst/kata-deploy/blob/master/kata-deploy.yaml now if that's ok. | 19:03 |
| kata-irc-bot | <eric.ernst> yeah... you'll want https://raw.githubusercontent.com/egernst/kata-deploy/master/kata-rbac.yaml, for example | 19:03 |
| kata-irc-bot | <eric.ernst> unless you want to pull it all down local. | 19:03 |
| kata-irc-bot | <jdandrea> Got it. | 19:03 |
| *** annabelleB has quit IRC | 19:05 | |
| kata-irc-bot | <jdandrea> Ok, so applying that after kata-deploy might not work, hmm. (Still not seeing the label.) I can start over. | 19:05 |
| *** annabelleB has joined #kata-dev | 19:07 | |
| *** davidgiluk has quit IRC | 19:24 | |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB807PYB0/-.txt / https://slack-files.com/T86U7NQTT-FB807PYB0-9bcef734fe | 19:25 |
| kata-irc-bot | <jdandrea> Are *both* of those OK to see during kubeadm init? | 19:26 |
| *** cdent has quit IRC | 19:26 | |
| *** annabelleB has quit IRC | 19:39 | |
| *** jugs has quit IRC | 19:44 | |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB73X9VU2/-.m / https://slack-files.com/T86U7NQTT-FB73X9VU2-353716195a | 19:49 |
| kata-irc-bot | <jdandrea> It has been waiting for quite a while. Hmm… | 19:49 |
| *** jugs has joined #kata-dev | 19:49 | |
| kata-irc-bot | <jdandrea> Hoping that kubeadm init cmd is idempotent. Interrupting and trying it again. | 19:51 |
| *** eernst has quit IRC | 19:54 | |
| *** eernst has joined #kata-dev | 19:55 | |
| *** annabelleB has joined #kata-dev | 20:03 | |
| *** annabelleB has quit IRC | 20:04 | |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB6DNPLLQ/-.php / https://slack-files.com/T86U7NQTT-FB6DNPLLQ-bd2563a6a8 | 20:31 |
| kata-irc-bot | <jdandrea> Waiting for 30 mins to see if the kata label shows up. One other thing I noticed: The success of kubeadm init is intermittent. Sometimes it hangs on kubelet booting up the control plane, and sometimes it doesn’t. The HTTP proxy appears to be fine at that time. I am wondering if this is due to that aforementioned catch-22 from the other day (with kubelet and kubeadm in a tenuous, if not deadly, embrace for a bit). | 20:33 |
| kata-irc-bot | <jdandrea> File uploaded https://katacontainers.slack.com/files/UAYMNLRK6/FB78X6877/-.txt / https://slack-files.com/T86U7NQTT-FB78X6877-f845a494aa | 20:34 |
| kata-irc-bot | <jdandrea> Huzzah! There it is. :) The catch-22 question is still on my mind tho. | 20:35 |
| kata-irc-bot | <krsna1729> @jdandrea if you are using centos7 vm to test this out i was able to get kata-deploy setup without problems https://paste.fedoraproject.org/paste/2o-jkEo~eCWWsfUQpxf0TQ | 20:46 |
| kata-irc-bot | <krsna1729> what is the catch-22? | 20:46 |
| kata-irc-bot | <jdandrea> @krsna1729 So what I’m noticing is that kubelet doesn’t have the cert in place so startup initially fails. “kubeadm init,” meanwhile, sets up those very items kubelet wants, and at the same time it requires kubelet to be running. End result: kubeadm DOES eventually succeed, although it is not properly started for a while. That’s the “tenuous embrace” I’m referring to. … and what I’m left wondering is: “Is it goo | 20:57 |
| kata-irc-bot | kubelet knowing it won’t startup successfully, and then use kubeadm to finish the job? (I suppose that’s debatable, but it has me wondering.) | 20:57 |
| kata-irc-bot | <mnaser> is ci healthy now btW? | 21:02 |
| kata-irc-bot | <salvador.fuentes> some jobs are, some others don't. I am trying to take a look at some of them | 21:05 |
| *** fiddletwix has joined #kata-dev | 21:06 | |
| *** fuentess has quit IRC | 21:32 | |
| *** devimc has quit IRC | 22:19 | |
| *** manjeets has quit IRC | 22:49 | |
| *** eernst has quit IRC | 23:03 | |
| *** manjeets has joined #kata-dev | 23:04 | |
| *** lamego has joined #kata-dev | 23:06 | |
| *** lamego1 has quit IRC | 23:10 | |
| *** eernst has joined #kata-dev | 23:10 | |
| *** lamego has quit IRC | 23:11 | |
| clarkb | as a general heads up, I've got zuul running .ci/setup.sh && .ci/run.sh against the proxy repo. https://zuul.openstack.org/stream.html?uuid=bae09735e26f44ed985e53b7b792faea&logfile=console.log is an inprogress log and the longer term storage of that will be available when it is done. The test cases in there apepar to fail though, not sure why, but seemed like jobs were failing regardless of platform when I | 23:14 |
| clarkb | started this last week or so. Current job config can be found at https://review.openstack.org/#/c/573748/ | 23:14 |
| clarkb | I know you all are fighting other battles, but this seemed semi relevant :) | 23:15 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!