Tuesday, 2019-10-15

*** jamesmcarthur has quit IRC00:16
*** jamesmcarthur has joined #zuul00:21
*** jamesmcarthur has quit IRC00:58
*** jamesmcarthur has joined #zuul01:03
*** jamesmcarthur has quit IRC01:34
*** jamesmcarthur has joined #zuul01:41
*** jamesmcarthur has quit IRC02:02
*** jamesmcarthur has joined #zuul02:05
*** ianychoi has quit IRC02:19
*** ianychoi has joined #zuul02:21
*** jamesmcarthur has quit IRC03:26
*** bhavikdbavishi has joined #zuul03:52
*** bhavikdbavishi1 has joined #zuul03:54
*** bhavikdbavishi has quit IRC03:56
*** bhavikdbavishi1 is now known as bhavikdbavishi03:56
*** bolg has joined #zuul04:06
openstackgerritIan Wienand proposed zuul/nodepool master: Validate openstack provider pool labels have top-level labels  https://review.opendev.org/68651404:32
*** bhavikdbavishi has quit IRC04:41
*** raukadah is now known as chandankumar04:47
*** wznoinsk has joined #zuul04:51
*** bhavikdbavishi has joined #zuul04:55
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: make separate template directories for each platform  https://review.opendev.org/68861605:06
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] configure-mirrors: add CentOS 8  https://review.opendev.org/68861705:06
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: make separate template directories for each platform  https://review.opendev.org/68861605:11
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] configure-mirrors: add CentOS 8  https://review.opendev.org/68861705:11
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] configure-mirrors: add CentOS 8  https://review.opendev.org/68861705:14
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: make separate template directories for each platform  https://review.opendev.org/68861605:22
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] configure-mirrors: add CentOS 8  https://review.opendev.org/68861705:22
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: make separate template directories for each platform  https://review.opendev.org/68861605:31
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] configure-mirrors: add CentOS 8  https://review.opendev.org/68861705:31
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: make separate template directories for each platform  https://review.opendev.org/68861605:38
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] configure-mirrors: add CentOS 8  https://review.opendev.org/68861705:38
*** sshnaidm_ has joined #zuul05:59
*** sshnaidm|pto has quit IRC06:00
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: add CentOS 8  https://review.opendev.org/68861706:02
*** sshnaidm has joined #zuul06:03
*** sshnaidm_ has quit IRC06:04
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: make separate template directories for each platform  https://review.opendev.org/68861606:05
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: add CentOS 8  https://review.opendev.org/68861706:05
*** sshnaidm_ has joined #zuul06:07
*** sshnaidm has quit IRC06:10
*** igordc has quit IRC06:10
*** yolanda__ has quit IRC06:20
*** yolanda has joined #zuul06:20
*** pcaruana has joined #zuul06:30
openstackgerritIan Wienand proposed zuul/zuul-jobs master: configure-mirrors: add CentOS 8  https://review.opendev.org/68861706:34
*** saneax has joined #zuul06:42
*** jpena|off is now known as jpena07:00
*** avass has joined #zuul07:04
*** jangutter_ has joined #zuul07:05
*** jangutter has quit IRC07:08
avasstobiash: I saw your comment on my change about doing case insensitive matching for labels. I'm guessing there's no case sensitive check when setting labels becuase it just tries to set it and checks the response from gerrit?07:13
*** tosky has joined #zuul07:19
tobiashavass: correct07:19
*** jangutter has joined #zuul07:22
avasstobiash: this part also looked strange to me 'change.missing_labels < set(allow_needs)', is there a reason why it's a prober subset?07:23
avasshttps://review.opendev.org/gitweb?p=zuul/zuul.git;a=blob;f=zuul/driver/gerrit/gerritconnection.py;h=03e948a61147aa559f524cd4523f51984802c5be;hb=b768ece2c0ecd235c418fe910b84ff88f69860d6#l88507:23
tobiashAllow_needs is thenset of labels the gate would set itself07:25
*** jangutter_ has quit IRC07:25
tobiashIf the set of missing labels (required to merge) is a subset it will be possible to merge after the gate07:26
avasstobiash: what's the content of allow_needs then? the labels we will set in the pipeline?07:27
tobiashYes07:28
avasstobiash: maybe I'm misunderstanding something then because that looks to me like if missing_labels == allow_needs then it should be able to merge07:30
*** hashar has joined #zuul07:31
tobiashyes, but missing labels on the change can also be less which is ok07:31
tobiashHence the set operation07:32
avasstobiash: yeah that's what I mean, shouldn't it be a '<=' operator and not a '<'?07:32
tobiashah now I get what you mean07:36
*** gtema has joined #zuul07:37
tobiashI guess you're right07:37
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: config-mirrors: Consolidate dnf/yum handler  https://review.opendev.org/68847907:38
tobiashBut I'm wondering how on earth that worked for years as missing_labels == allow_needs sound to me like the most common case07:39
avasstobiash: yep, that's what confuses me07:42
avasstobiash: I'll push a change to gerrit for it07:42
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: configure-mirrors: fix mirror_fqdn variable  https://review.opendev.org/68846807:49
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: configure-mirrors: Consolidate dnf/yum handler  https://review.opendev.org/68847907:50
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: configure-mirrors: Consolidate dnf/yum handler  https://review.opendev.org/68847907:51
AJaegerzbr: did you see ianw's changes https://review.opendev.org/#/c/688616/ ?07:53
openstackgerritAlbin Vass proposed zuul/zuul master: Missing labels is a subset of allow_needs  https://review.opendev.org/68864507:53
zbrAJaeger: nope.07:54
openstackgerritFabien Boucher proposed zuul/zuul master: A Zuul reporter for Elasticsearch  https://review.opendev.org/64492707:58
zbrAJaeger: but I am ok with it, I can easily redo my other changes to fit that one. lets merge it.07:59
AJaegerzbr: sure, will review later if nobody beats me to it ;)08:04
zbrsure, sadly i can only do a +1 and ping others to look at it.08:10
*** themroc has joined #zuul08:20
*** brendangalloway has joined #zuul08:22
zbrclarkb: corvus : please r/w ian's two changes for configure-mirrors: https://review.opendev.org/#/c/688616/ (centos8) thanks.08:25
*** jamesmcarthur has joined #zuul08:30
*** jamesmcarthur has quit IRC08:34
*** themr0c has joined #zuul08:48
*** themroc has quit IRC08:50
*** bolg has quit IRC09:11
openstackgerritTobias Henkel proposed zuul/zuul master: Add nodesets API route  https://review.opendev.org/60587709:11
*** brendangalloway has quit IRC09:15
*** brendangalloway has joined #zuul09:17
*** sshnaidm_ is now known as sshnaidm|pto09:27
*** themr0c has quit IRC09:31
*** themroc has joined #zuul09:32
avasstobiash: For consistency with case sensitivity, would it make sense to check labels before setting them?10:30
*** bhavikdbavishi has quit IRC10:31
*** gtema has quit IRC10:32
*** themroc has quit IRC10:33
*** themroc has joined #zuul10:34
tobiashavass: that would be a runtime overhead10:36
avassyeah that's what my thought was.10:38
*** recheck has quit IRC11:00
*** recheck has joined #zuul11:00
*** recheck has quit IRC11:03
*** recheck has joined #zuul11:04
*** recheck has quit IRC11:05
*** recheck has joined #zuul11:05
*** recheck has quit IRC11:06
*** recheck has joined #zuul11:06
*** recheck has quit IRC11:06
*** recheck has joined #zuul11:07
*** recheck has quit IRC11:08
*** recheck has joined #zuul11:08
*** recheck has quit IRC11:11
*** recheck has joined #zuul11:11
*** saneax has quit IRC11:24
*** bolg has joined #zuul11:38
*** jpena is now known as jpena|lunch11:42
*** avass has quit IRC12:00
*** avass has joined #zuul12:03
*** saneax has joined #zuul12:09
*** brendangalloway has quit IRC12:17
*** paladox has quit IRC12:23
*** paladox has joined #zuul12:24
*** themr0c has joined #zuul12:34
*** themroc has quit IRC12:34
*** saneax has quit IRC12:38
*** jpena|lunch is now known as jpena12:41
recheck[so-zuul] I want to set spring.profile.active before the zuulServlet is registered → https://stackoverflow.com/questions/58394973/i-want-to-set-spring-profile-active-before-the-zuulservlet-is-registered12:54
Shrewsrecheck: this is the channel for Zuul the CI/CD project, not the Netflix zuul12:55
Shrewswhy that question is labeled with openstack-zuul is beyond me12:56
*** panda|off is now known as panda13:01
*** brendangalloway has joined #zuul13:05
openstackgerritMerged zuul/nodepool master: Validate openstack provider pool labels have top-level labels  https://review.opendev.org/68651413:16
ShrewsCan someone review/approve https://review.opendev.org/687965 please?13:23
*** jangutter_ has joined #zuul13:24
*** jangutter_ has quit IRC13:24
*** jangutter has quit IRC13:27
openstackgerritTobias Henkel proposed zuul/zuul master: Add the process environment to zuul.conf parser  https://review.opendev.org/61282413:28
*** pcaruana has quit IRC13:32
openstackgerritTobias Henkel proposed zuul/zuul master: Add the process environment to zuul.conf parser  https://review.opendev.org/61282413:35
*** spsurya has joined #zuul13:42
tobiashzuul-maint: interesting, I got three merge failed messages for one recheck of https://review.opendev.org/659991 which is in merge conflict13:43
tristanCcould it be because zuul/zuul is registered in both openstack and zuul tenant?13:45
fungizbr: is "recheck" an irc bot you're running? if so, might be nice to make that clear before folks start getting into conversations with it. (also adding a vocal bot to a channel without agreement of the other channel regulars could be considered rude)13:48
zbrfungi: yeah, is a bot i am running. do you want me to disable it?13:52
zbri guess the stackoverflow feed is too prone to low quality posts13:52
fungizbr: i don't feel strongly about it, but will let others weigh in on how useful they do/don't find it13:52
fungitristanC: that's an interesting theory, but then why three merge failure messages and not two13:53
zbrfungi: is based on rss-feeds, see config at https://github.com/ssbarnea/harem/blob/master/apps/rss-bot/config.yaml#L74-L7813:54
tristanCfungi: i missed the opendev tenant that also include zuul/zuul13:54
*** jamesmcarthur has joined #zuul13:55
zbrfungi: can you help with https://review.opendev.org/#/c/688616/ ? (and its child)13:56
fungitristanC: oh, yep, zuul/zuul(:|$) finds three entries in main.yaml13:56
fungii was initially just searching for zuul/zuul$13:57
fungiso that seems increasingly likely13:57
fungizbr: looking13:57
*** pcaruana has joined #zuul14:04
*** michael-beaver has joined #zuul14:04
*** jamesmcarthur has quit IRC14:09
bolgtobiash: avass: there has been actually a change not so long ago, the sub-set was checked using a fast failing loop which should be interpretted as "<=" (see https://review.opendev.org/#/c/681936/6/zuul/driver/gerrit/gerritconnection.py)14:14
*** avass has quit IRC14:16
Shrewsoh, recheck is a bot? i feel silly now14:17
*** bolg_ has joined #zuul14:18
*** bolg has quit IRC14:19
Shrewsi wonder if fungi is a bot, too14:19
*** recheck has quit IRC14:20
*** recheck has joined #zuul14:20
*** recheck has quit IRC14:20
*** recheck has joined #zuul14:21
*** recheck has quit IRC14:21
*** recheck has joined #zuul14:21
*** brendangalloway has quit IRC14:21
*** jangutter has joined #zuul14:25
*** electrofelix has joined #zuul14:25
Shrewszbr: If we're voting, I prefer not having the bot. I'm sure there are likely less intrusive ways for folks to monitor stackoverflow if they so choose.14:25
*** jamesmcarthur has joined #zuul14:27
*** recheck has quit IRC14:27
zbrShrews: done, removed.14:30
Shrewszbr: well, i was just voicing *my* preference. might want to check with others, too.14:30
zbrShrews: two reports were enough, it started as an experiment, proved usedful in some cases but detrimental in others.14:31
Shrews*nod*14:31
zbrmain issue is that stackoverflow feed does not have an option to filter only questions with votes, so a lot of very-low-quality questions can flood a channel.14:32
zbryou can only imagine what happened when I activated "pip" tag for pypa channel ;)14:32
Shrewsi don't think many (if any) of us want to include stackoverflow in our normal support path. i could be mistaken though14:33
*** bhavikdbavishi has joined #zuul14:33
fungiweb forums like stackoverflow could be viewed as social networking and outreach opportunities, but yeah, i hope nobody considers that an official means of getting support for free software14:36
Shrewsthough i could see some benefit to it, since that site is usually the top hit from search engines in tech-related questions14:36
openstackgerritMerged zuul/zuul-jobs master: configure-mirrors: make separate template directories for each platform  https://review.opendev.org/68861614:48
ShrewstristanC: do we need to add some sort of "wait" period in the k8s job? hit the "pod status is Pending" timeout again: https://zuul.opendev.org/t/zuul/build/7ca81f62f8ad488e824ae83e559154c1/log/job-output.txt#115214:49
Shrewsnot sure if that was also related to the ipv6 issues14:51
clarkbShrews: that ran in ovh bhs1 which does not have ipv6 at all14:52
clarkbI doubt this is the problem we saw in fortnebula14:52
Shrewsclarkb: oh? a public_ipv6 value is listed for the node14:54
Shrewshttps://d1a899ea13e66d0e8401-c80779e78a1a20b721125eb9333742c5.ssl.cf5.rackcdn.com/687965/2/gate/nodepool-functional-k8s/7ca81f6/zuul-info/inventory.yaml14:54
Shrewsnot sure what that is then14:54
clarkbShrews: that is an ovh oddity, basically their neutron says "hey you can use this address" but then config drive doesn't include any of that info so we never configure it14:55
clarkbShrews: this is why we force ipv4 in our clouds.yaml for ovh clouds14:55
Shrewsah, i see14:55
clarkbin theory we could have the zuul job statically configure that address if we wanted14:56
clarkbbut I don't think it has come up as being a need so has mostly just been ignored14:56
tristanCShrews: kubernetes driver is waiting 300 seconds for pod to become running14:57
tristanCand it seems like we don't collect k8s api logs, thus i don't know why the pod didn't transition to running14:59
Shrewswe should probably collect those then15:01
openstackgerritFabien Boucher proposed zuul/zuul master: A Zuul reporter for Elasticsearch  https://review.opendev.org/64492715:03
zbrclarkb: fungi: https://review.opendev.org/#/c/688617/9 (centos8) is also ready.15:07
fungizbr: yep, i was still working my way through reviewing that one15:08
* fungi is a slow, distracted, reader15:08
clarkbShrews: I'd like to restart nodepool launchers after my morning meeting. This should pick up the DELETED status handling for nova instances. Anything else I should keep in mind?15:09
zbrfungi: thanks.15:09
openstackgerritMerged zuul/nodepool master: Fix builder shutdown race in tests  https://review.opendev.org/68796515:24
*** bhavikdbavishi has quit IRC15:31
*** bolg_ has quit IRC15:32
*** igordc has joined #zuul15:37
*** mattw4 has joined #zuul15:38
*** jpena is now known as jpena|brb15:45
openstackgerritMerged zuul/zuul-jobs master: configure-mirrors: add CentOS 8  https://review.opendev.org/68861715:46
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857815:51
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857815:57
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add support for selecting the kubernetes version  https://review.opendev.org/68874315:57
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857815:58
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add support for selecting the kubernetes version  https://review.opendev.org/68874315:58
*** themr0c has quit IRC16:02
*** jpena|brb is now known as jpena16:18
*** igordc has quit IRC16:31
*** hashar has quit IRC16:38
tristanCcorvus: the namespace and buildset test stack for zuul-registry, should i +3 the first change?16:39
corvustristanC: yes, i think it's ready16:40
corvusweird -- minikube with cri-o still wants a "docker" executable for something?16:41
corvushttps://zuul.opendev.org/t/zuul/build/acd2f48e57f349829c1fffb95ef8b1c3/console#1/0/16/ubuntu-bionic16:42
corvusmy test vm did have docker installed, so i haven't seen that before16:42
corvus"Using this driver requires Docker and a Linux environment but not a hypervisor"16:44
corvusapparently if you use vm driver==none it uses docker for something16:44
corvuswell, i think the 2 can coexist :)16:45
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857816:46
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: Add support for selecting the kubernetes version  https://review.opendev.org/68874316:46
openstackgerritGabor Lekeny proposed zuul/zuul master: Fix github auth token authentication  https://review.opendev.org/68635516:47
tristanCcorvus: perhaps the kube-apiserver is also started in a container and minikube rely on docker for that?16:48
corvustristanC: yeah, i think that's the case.16:49
corvusit looks like it runs most of the stuff in docker containers except for kubelet16:50
tristanCcorvus: hum, perhaps there is also an issue with the code according to: https://github.com/kubernetes/minikube/issues/554916:51
corvustristanC: wow you're better at googling than i am :)16:52
tristanCcorvus: to be sure we need to check that kubelet is started with "--container-runtime=remote" and "--container-runtime-endpoint unix://...crio.sock"16:53
tristanCcorvus: also "crictl version" is a simple test to verify cri-o is started correctly16:54
corvusi'm not having trouble with k8s using crio :)16:54
Shrewsclarkb: i'm not aware of anything16:54
openstackgerritJan Kubovy proposed zuul/zuul master: WIP: Mandatory SQL connection  https://review.opendev.org/68875516:59
*** jpena is now known as jpena|off17:01
openstackgerritJan Kubovy proposed zuul/zuul master: WIP: Mandatory SQL connection  https://review.opendev.org/68875517:04
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: configure-mirrors: fix mirror_fqdn variable  https://review.opendev.org/68846817:19
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: configure-mirrors: Consolidate dnf/yum handler  https://review.opendev.org/68847917:22
mordredcorvus: podman has a docker compat shim ...17:26
mordredso that you can type docker and it'll run podman17:26
mordreddon't know if that's helpful for minikube or not17:26
clarkbyou get that by default on rhel8 if you install docker too17:27
clarkb(this has apparently surprised some people)17:27
mordredyeah. I think from the ppa it's a separate package17:27
mordredhrm. doesn't look like it. I think it's actually just a symlink anyway17:28
*** electrofelix has quit IRC17:32
*** spsurya has quit IRC17:33
corvusmordred: oh cool -- well maybe we can try that later -- but now i'm hitting "Failed to enable container runtime: running command: sudo systemctl restart crio: exit status 1"17:34
corvusso i think i'm going to have to hold a node17:34
tristanCcorvus: i spent quite sometime doing crio configuration, i may be able to help with that17:36
corvustristanC: cool, thanks :)17:36
corvus(i do have this working on a test vm -- so now that this is running on a clean vm, i'm probably just missing some small step i either forgot i did, or accidentally did and didn't realize it)17:37
corvusat least, that's what i'm hoping17:37
mordredcorvus: I'm going to blame systemd17:38
corvusit's not not involved17:38
corvusi think we should probably get some journal logs too17:38
*** armstrongs has joined #zuul17:43
*** armstrongs has quit IRC17:53
*** hashar has joined #zuul18:01
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877518:05
*** openstackgerrit has quit IRC18:07
*** jangutter has quit IRC18:08
*** jamesmcarthur has quit IRC18:12
corvusShrews: oh that's nice, i didn't know about that :)18:14
corvusShrews: can you just run "/tmp/minikube logs > ~/logs/minikube.txt" ?18:15
corvusShrews: i think that the base job will pull that automatically18:15
Shrewscorvus: i didn't know about it either until just now when i went a' googlin'.   maybe? i guess that would have to be using the shell module18:16
corvusya18:16
corvusprobably more efficient than storing it all in ansible's memory too18:16
Shrewscorvus: i'll try that after the k8s job runs. just want to verify this will work first18:17
corvusya18:17
corvustristanC: ah yep, it was something i fixed on my test node and forgot about: http://paste.openstack.org/show/784003/18:20
corvustristanC: it looks like a bug in the debian packaging -- the config file is set up for /usr/libexec/crio/conmon but the installed path is /usr/bin/conmon and it doesn't create a link18:20
corvustristanC: do you think they want bugs here? https://bugs.launchpad.net/~projectatomic18:21
corvusmeanwhile, we can either sed the conf file or make a symlink...18:22
*** chandankumar is now known as raukadah18:24
corvusShrews: i'll incorporate that into my next ps18:24
mordredcorvus: I imagine they want bugs on their github18:24
corvusShrews: (of the minikube crio test)18:24
corvusmordred: is there a github repo for the ppa?18:24
mordredcorvus: https://github.com/containers/libpod/issues18:25
*** openstackgerrit has joined #zuul18:25
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877518:25
mordredcorvus: well - last time I talked with them about the ppa, I believe I did it on the libpod repo18:25
corvusoh, ok18:26
Shrewscorvus: there is also a ~/.minikube/logs directory, but there is nothing in it when i test locally. not sure what that's about18:27
mordredcorvus: oh - although that's the cri-o package, yeah?18:27
mordredcorvus: so it might be in https://github.com/cri-o/cri-o18:27
corvusmordred: yeah18:27
mordredcorvus: I'm honestly not 100% sure how that all hangs together18:27
corvusmordred: well, actually the 'conmon' package18:27
mordredcorvus: probably libpod18:28
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857818:30
Shrewscorvus: looks like we need to not use ~ there because of the 'become' part. just failed in my change18:34
corvusoh right18:34
corvusansible_remote_user i guess?18:35
corvusand i guess we need become to get journal logs, etc?18:35
*** igordc has joined #zuul18:36
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877518:36
Shrewscorvus: ^^18:37
Shrewsansible_user_dir18:37
corvuskk, i'll update my copy after the next failure :)18:37
Shrewscorvus: we use 'become' when starting minikube which creates a permission issue. locally i got this error:18:39
Shrews$ ./minikube logs18:39
Shrews💣  Error getting config: open /home/shrews/.minikube/profiles/minikube/config.json: permission denied18:39
* Shrews wonders if the 'bomb' emoji came across18:39
mordredShrews: I see the bomb18:40
Shrewsmordred: YOU'RE the bomb18:40
corvusyeah... there's like... multiple issues on github about how to configure your system to correctly see the error emojis...18:40
* mordred headdesks18:40
clarkbI think it largely comes down to font glyphs18:40
corvusi feel like... maybe that is a misdirection of energy....18:40
clarkbI don't see that one but see others18:41
Shrewscorvus: you NEED emojis18:41
corvusShrews: if i can't type "sad-emoji" i can't ever really be sad18:41
*** michael-beaver has quit IRC18:44
Shrewscorvus: other than the sans-docker part, what is the advantage of cri-o?18:48
Shrewsoh, integration with our registry i guess18:49
corvusShrews: the zuul-registry will be able to hold speculative images for more than one upstream registry (dockerhub, quay.io, gcr, etc) but that will only work with non-docker runtimes.  so if we want to use non-dockerhub speculitave images with k8s, we'll need this.18:49
AJaegerShrews: sans-docker is enough advantage for me ;)18:59
*** jamesmcarthur has joined #zuul19:00
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877519:07
*** hashar has quit IRC19:28
*** hashar has joined #zuul19:36
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877519:37
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877519:39
mnaserhmm19:42
mnaserso when moving gear to the opendev tenant19:42
mnaseri guess we missed the fact that we didnt actaully run any jobs here - https://review.opendev.org/#/c/688455/19:42
mnaserim not sure why we didn't run any jobs there19:43
mnaserand the actual thing is broken now because bindep.txt in opendev is empty afaik19:43
mnaserso its needing something with ffi19:43
clarkbwe ran jobs there...19:44
mnaserah gah19:44
mnaseri got tricked by the promote jobs overriding that section again19:44
clarkband the ffi problem should be fixed by cffi publishing wheels19:44
Shrewsmnaser: that gets me all the time, too19:44
mnaseri wonder if i can fix that19:45
mnaseris the source code somewhere for it19:45
mnaseroh hmm19:46
mnaserhttps://review.opendev.org/#/c/688683/ -- doesnt seem to be broken in this for example19:46
clarkbwe don't annotate the pipeline names outside of the openstack tenant maybe?19:47
clarkbwe can update that if that is the problem19:47
mordredchecks plugin will make all of that happy :)19:47
fungii've also been wondering whether we should report the tenant name as well as the pipeline, now that we potentially have multiple tenants reporting separate buildsets with the same pipeline names19:48
corvusthat should never happen19:48
mnaseri wonder if its because success-message is not defined for opendev19:49
mnaserand maybe that thing makes introspection to find out which pipeline it ran in>19:49
mnaserthing = the piece of js code we have in gerrit19:49
corvusie, a project should only be configured for reporting pipelines in one tenant19:49
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877519:50
mnaserhttps://review.opendev.org/static/hideci.js?e=054a8d9d1a4a2e49b7411eb93fd173a7 --- var pipelineNameRegex = /Build \w+ \(([-\w]+) pipeline\)/;19:50
mnaseri can push up a quick patch to change that (unless the checks plugin is going live next week, mordred :p)19:51
clarkbmnaser: it won't be you should push up the pipeline update19:51
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857819:51
fungicorvus: on a related note, did you see the example earlier today where the opendev zuul triple-reported a merge failure? (tristanC's theory is that's because it's included in three tenants)19:52
mordredyeah. checks plugin is still in dev - mostly just saying it'll be so nice when there's a non-scraping way of doing this properly19:52
* mnaser looks at that javascript19:52
mnaserCopyright (c) 2014 Hewlett-Packard Development Company, L.P.19:52
corvusfungi: nope, someone should look into that :)19:53
fungicorvus: tobiash mentioned it at 13:43z... https://review.opendev.org/65999119:53
mordredmnaser: is a real big hack that we're very unpleased about the existence of - thus the excitement about checks :)19:53
corvusfungi: it should only do that for pipelines it's part of.  note, however, that the openstack tenant in openstack adds *every* project to the check pipeline.19:55
mnaserbtw -- looks like i got the gear image to build on the first try -- but no functional tests .. so i dont know how we want to proceed with reviewing something like this: https://review.opendev.org/#/c/688446/19:57
Shrewscorvus: fyi, i'm uncertain if all of the environment vars in https://review.opendev.org/#/c/688775/7/playbooks/nodepool-functional-k8s/post.yaml are needed, but you'll need at least the MINIKUBE_HOME one on your change I'm guessing. I planned to try just that one after a successful log pull.19:58
Shrewswhich looks like just happened19:58
mordredmnaser, corvus: we _could_ get fancy and make the zuul-quickstart run gear as a separate container using that image instead of the internal one - just so we have a good functional cross-test for the image19:58
Shrewscorvus: https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_194/688775/7/check/nodepool-functional-k8s/194d14d/ubuntu-xenial/minikube.txt19:58
mordredwe don't _need_ that to be split out in the quickstart though - so it might be counterproductive19:58
mnasermordred: yeah, i mean it probably doesnt hurt that much more for quickstart to having it externalized19:59
mnaser"what's one more container":20:00
mordredmnaser: yah - my main concern would be making it seem more complex for a user learing - but maybe having an explicit server helps see how the system hangs together?20:00
ShrewstristanC: does https://storage.bhs1.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_194/688775/7/check/nodepool-functional-k8s/194d14d/ubuntu-xenial/minikube.txt look like it would have the logging info you would need to diagnose the k8s failure?20:00
corvusmnaser, mordred: i'd say let's not.  quickstart is supposed to be mostly educational... and running geard separately isn't how we recommend doing it20:01
ianwcorvus: when is the next zuul release likely?20:01
mnaseri mean i'm happy to do my own testing and iterate on it, yes this might mean we release broken images but..20:01
corvusmnaser: should be easy to throw a "run a job" test at it at least20:02
corvusianw: i guess now or tomorrow?  :)20:03
corvusShrews: is nodepool releasable?20:03
mnaserok i guess i can try and use that image to spin up a container with geard and then use the container to try and enqueue a job or something20:03
corvusmnaser: i'm also personally okay with publishing that image as-is.  at least until the first patch comes in that says "fix issue with docker image..." :)20:04
tristanCShrews: seems like it yes20:04
Shrewscorvus: i believe so, though we only just restarted the launchers with the latest changes today20:04
fungiif there are zuul/nodepool releases today i'll link to the corresponding release announcements in the zuul section of the osf newsletter20:05
mordredmnaser: same here20:05
corvusShrews, ianw: i think we should release zuul+nodepool together because of the auto python version thingy20:05
ShrewstristanC: awesome20:05
tristanCShrews: though i don't know how minikube works, perhaps we also needs the output of the kube-system pods.20:05
ianwcorvus: yeah, that was my thought -- but the nodepool side isn't in.  we were going to wait for a zuul release, then reference it in the nodepool change which would go into next nodepool release20:05
ShrewstristanC: do you know how to get that? i don't think any of us know minikube20:05
corvusianw: oh ha, ok20:05
tristanCShrews: well it seems like they are dumped too20:06
ianwi mean that was why i was asking, to see where that chnage was.  was going to mention it wrt centos8 (python3 only)20:06
mnasermordred, corvus: i can try to consume it once we publish it.. i'm going to be honest, i find it a little harder for me to get tests up cause im not sure if i can say.. run a "gearman tempest" against it or something :-P20:06
corvusianw: it seems that we did the opposite: https://zuul-ci.org/docs/zuul/releasenotes.html20:06
ianwhrm, yeah that probably shouldn't have been a releasenote in hindsight20:07
clarkbI status logged the launcher version we started on seems to be working no objection to tagging that from me20:09
*** jamesmcarthur has quit IRC20:09
mordredI have no objections to tagging anything20:09
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877520:10
corvusianw: okay after reviewing the discussions, i think "zuul then nodepool" makes sense.  do you want to release zuul with that release note, or alter or remove it first?20:10
ianwcorvus: just working on a removal, to avoid confusion20:10
corvus(we could leave it as is,  or alter it to say "in an upcoming nodepool release...", or remove it)20:10
corvusianw: cool, then the plan is to wait for the release note change, then release zuul, then merge the nodepool change and release it (probably 1 day later?)20:11
openstackgerritIan Wienand proposed zuul/zuul master: Remove python-path auto release note  https://review.opendev.org/68880920:12
ianwcorvus: right, no urgent rush.  can update the nodepool change to say "this relies on zuul <release>"20:13
*** jamesmcarthur has joined #zuul20:19
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877520:21
Shrewscorvus: fyi, MINIKUBE_HOME: "{{ ansible_user_dir }}" is all you need20:22
corvusShrews: cool, thanks!20:24
*** pcaruana has quit IRC20:25
*** pcaruana has joined #zuul20:34
mnaserso uh20:36
mnaserworking with some of the rdo folks on debugging an issue with the tripleo-reproducer stuff (cc nhicher !) and i noticed the following20:36
mnaserhttps://opendev.org/zuul/zuul/src/branch/master/zuul/ansible/base/callback/zuul_stream.py#L140-L14420:36
mnaserhttps://bugs.launchpad.net/tripleo/+bug/1833465 -- seems like they run int othis often, and the generic exception handler there kinda masks possible issue20:36
openstackLaunchpad bug 1833465 in tripleo "tripleo reproducer fails w/ "waiting on logger"" [Critical,Triaged]20:36
mnaserdoes anyone recall a historical reason why we dont log the actual exception for example or how we I rewrite that to help uncover the actual issues20:37
mnaserinterestingly enough it always happens after iptables-save and then never recovers20:38
corvusmnaser: the job content probably blocked port 1988520:38
*** jamesmcarthur has quit IRC20:38
mnasercorvus: that was my guess but also this is a thing that doesnt consistently fail20:39
mnaserso its an intermittant once-in-a-while-but-sometimes-kinda-consistent20:39
corvusmnaser: i don't think having the actual exception is going to help -- it's just going to say "connection refused" or similar.  either way, the error is "can not open network connection to port 19885" on node20:39
mnaseriptables shows that it's happily accepted packets for a while too, i was trying to see if i can find the log of zuul_console without luck20:40
corvusmnaser: by "log of zuul_console" what do you mean?20:41
mnasercorvus: the actual thing that listens on port 1988520:42
corvusmnaser: it doesn't have its own log files; it may (in rare cases) return an error to ansible20:43
corvusmnaser: i think the way to track that down is to hold a node and inspect connectivity to 1988520:44
mordredooh - maybe I can nerd-snipe mnaser into finishing my half-done patches to rework log streaming ...20:46
mordredalthough maybe I shouldn't say that out loud like that ...20:46
mnasercorvus: in this case, inspecting the held node, i dont see any issues. nothing is running at that port anymore, but i can start up SimpleHTTPServer at that port and it responds..20:47
corvusmnaser: did the node reboot?20:47
mnasermordred: dont threaten me with a good time :p20:47
mnasercorvus: it did not, this would happen after persisting iptables (and i have the journal logs here showing that ansible actually continued to run with no problems)20:48
mnaserbut the logs died20:48
*** jamesmcarthur has joined #zuul20:48
corvusmnaser: anything in syslog/journal about it?  oom?20:48
corvussystemd may have recorded reaping the process20:48
mnasernothing sticks out in journal, no ooms, though i'm trying to grep for 'stream' or 'console' and not seeing much about it there (does it use ansible to start it up?)20:49
corvusmnaser: yes, it's an ansible module that daemonizes20:49
mnaserthat's what i remember too, but maybe because it daemonizes then ansible never logs it in journal like it usually does20:50
*** pcaruana has quit IRC20:51
mnaserearliest record of ansible doing things is clearly a bunch of the ssh setup20:52
mnaserinterstingly enough20:53
mnaserzuul_console.json has all the right things20:53
mnaserwhich means it didnt die20:54
corvusmnaser: that's logged by the callback handler and doesn't rely on the log streamer20:54
Shrewsfolks, let's merge https://review.opendev.org/688775 today if we can, please. random fails keep biting us21:00
mordredmnaser: https://review.opendev.org/#/q/topic:zuul-stream-rework if you find yourself with time and feel like getting nerd-sniped. it's still on my TDL - but it's buried a bit below other things21:00
mnasermordred: oou interesting and doesnt even seem that complex.. initially :L21:01
mordredmnaser: yeah - the first 80% of that one is TOTALLY straightforward21:02
corvusShrews: are you sure we can't skip the synchronize step if we put it in zuul-output/logs ?21:02
mordredcorvus: I was going to ask the same question - but the rest of the playbook is also not using zuul-output ...21:02
Shrewscorvus: we could, but that differs from how we do the other logs21:03
corvushave to start somewhere21:03
mordredcorvus: so maybe we should do a patch wich updates it to change the whole playbook21:03
corvusthe other logs are doing something else21:03
Shrewswhy do our docs recommend ~/work/logs then?21:03
corvusShrews: the difference is between whether it happens on the executor or the remote host21:03
corvusthis case is "run a command on the remote host to get a log file" that's exactly the use-case that zuul-output is designed for21:04
corvusi think the best way to update the other logfiles would be to have nodepool write them directly into ~zuul/zuul-output/logs21:04
corvusthat's why i say it's a different thing21:04
corvusthe zuul-output thing is *supposed* to make this simple :)21:05
corvusbut we have to actually start using it at some point if we want that to happen21:05
corvusShrews: if you just want to merge that, i'm fine -- i'll do it the way i'm suggesting in the kubernetes role21:05
corvusi just think i was misunderstood in my review of the change, and i think it's important to straigten this out21:06
Shrewsi wasn't even aware of that being an option (or, at least, i forgot it was?)21:06
Shrewscorvus: let's merge as is, then i'll change all of the logging in one chunk in another review21:07
corvusShrews: the idea is to move everything in zuul-jobs to use this system21:07
corvusbut it's still only half-implemented and sparsely documented :/21:08
Shrewsis it implemented in a base job?21:08
corvusseveral folks have worked on it piecemeal21:08
mordredShrews: yes21:08
Shrewswell, i missed that. my fault, i guess21:08
tristanCbtw there is topic:zuul-jobs-with-kubectl that is waiting for review to fix the fetch-* roles to use the zuul-output21:08
corvusShrews: https://zuul-ci.org/docs/zuul-jobs/log-roles.html#role-fetch-output  is the main thing21:08
mordredhttps://opendev.org/zuul/zuul-jobs/src/branch/master/roles/fetch-output21:09
mordredcorvus link is better than mine21:09
tristanC(without topic:zuul-jobs-with-kubectl, most zuul-jobs doesn't work on kubernetes)21:10
* mordred has that on his queue now21:10
corvustristanC: should we document that as a site var and name it "zuul_site_use_fetch_output" (eg like https://zuul-ci.org/docs/zuul-jobs/mirror.html )?21:11
corvustristanC: alternatively -- we could just let folks know that zuul-jobs is going to rely on fetch-output and not make it an option21:12
mordredwe should add a zuul_site_use_fetch_output to opendev's site vars, since we have fetch-output21:12
openstackgerritDavid Shrewsbury proposed zuul/nodepool master: Pull minikube log data  https://review.opendev.org/68877521:12
mordredcorvus: could we use zuul_return in fetch-output to set zuul_use_fetch_output to true?21:12
Shrewsok ^^. i'll fix up the nodepool portion tomorrow21:12
mordredcorvus: wait- that's the dumbest thing I've said21:13
corvusmordred: no, only affects later playbooks21:13
mordredI blame jetlag21:13
tristanCcorvus: iiuc, site vars are not tenant scoped, and that makes it difficult to use them base job that may be different accross tenants21:13
corvus(well, we could try some set_fact or something)21:13
Shrewsfwiw, i read "Zuul executor creates a directory to hold all of the content related to the job" in the docs as "on the node". maybe i can clarify that tomorrow too21:13
corvustristanC: you can define them in base jobs21:13
tristanCfor* base job21:13
corvusShrews: fwiw, the zuul executor does *nothing* on any node21:14
corvustristanC: so if you have a situation where one tenant uses fetch-output and one doesn't, you could just set the variable there21:14
corvustristanC, mordred: but i really like the idea of saying "zuul-jobs depends on fetch-output"21:15
mordredcorvus: I thnik I like te variable approach like tristanC has in these patches - it's already implemented and it removes a potential downstream breaking point...21:15
mordredTHAT SAID ...21:15
mordredI also want to say zuul-jobs depends on fetch-output21:15
corvusevery role/job in zuul-jobs is going to need that kind of branching logic21:15
corvusthat's too much to ask21:15
mordredindeed. maybe we should go ahead and send out the warning email to the mailing list "please make sure your base jobs have fetch-output in them"21:17
tristanCmordred: corvus: either way works for me, though the toggle makes it backward compatible for existing user21:17
tristanCi'd be happy to rework the stack to remove non zuul-output support if you prefer that21:17
mordredbut go ahead and land the ones tristan has here to keep moving the needle forward (and fix those roles for k8s) while we wait for the appropriate time to pass for breaking changes21:17
mordredthen remove the branching as a cleanup?21:18
mordredtristanC: software factory is using fetch-output already yeah?21:19
corvusif it's not urgent, i'd prefer to avoid landing the branching at all...  because the cleanup will be a lot of work...21:19
mordredSpamapS: about about your zuul? do you use fetch-output in your base job?21:19
mordredpabelanger: ^^ ?21:19
corvusbut if tristanC is motivated enough to not only land this series, but also write and get the cleanups landed, i won't object...21:19
*** hashar has quit IRC21:20
corvus(i'm mostly trying to reduce everyone's workload :)21:20
mordred++21:20
* mordred is happy to go either route21:20
mordredI suppose either route involves another set of patches for those roles from tristanC :)21:20
tristanCmordred: not yet, we are waiting for that stack to land.21:20
mordredtristanC: gotcha21:20
tristanCaa/clear21:37
tristanCoops21:37
*** jamesmcarthur has quit IRC21:45
SpamapSmordred: maybe? What's fetch-output exactly?21:47
SpamapSdoesn't look like it actually21:48
mordredSpamapS: role to be used in base jobs that fetches stuff back from the node(s) to the executor21:48
mordredSpamapS: https://zuul-ci.org/docs/zuul-jobs/log-roles.html#role-fetch-output21:49
mordredSpamapS: the general goal has been to get everyone using fetch-output so that indivual jobs don't need to know how to handle differences between k8s and vms for instance21:49
SpamapSOh, I use zuul-base-jobs so it probably calls that21:49
corvusyep21:50
corvuszuul-base-jobs has both ensure-output-dirs and fetch-output21:50
mordredwoot21:51
SpamapSas much grief as using that has caused me, I suspect it has saved me a lot of work to just use it via the git driver. :)21:51
fungiSpamapS: yep, https://opendev.org/zuul/zuul-base-jobs/src/branch/master/playbooks/base/post.yaml#L321:54
clarkbmnaser: fwiw the last time I debugged similar issues in tripleo jobs I discovered the test VM was crashing due to use of nested virt. Sounds like you've already ruled out the possibility of a reboot, but I wanted to call it out because no one had noticed it happenign until I looked at their syslog logs22:00
mnaserclarkb: yeah it doesnt even get that far, its in the prep phase, but still kinda trying to grok whats going on22:01
mordredShrews: you're missing a logs dir in there22:03
mordredShrews: and in saying that - I realize that the docs for fetch-output do not actually document the subdirs22:04
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857822:05
*** jamesmcarthur has joined #zuul22:13
*** jamesmcarthur has quit IRC22:31
corvusShrews: working code in https://review.opendev.org/688578 produces https://zuul.opendev.org/t/zuul/build/9f700416bd00475db3be1110d0f5ca20/log/minikube.txt22:32
corvustristanC: crio and minikube seem to disagree on which cgroup driver to use -- crio.conf has 'systemd' and minikube configured kubelet with --cgroup-driver=cgroupfs.  do you have an opinion on which we should use?22:36
corvus(presumably we can either sed crio.conf or add another argument to minikube)22:36
corvus(i believe in my testing i changed crio to use cgroupfs)22:37
tristanCcorvus: you can find my handmade crio.conf conf here: https://github.com/podenv/silverkube/blob/master/silverkube.py#L21622:41
corvustristanC: cool, i'll edit the conf then :)22:41
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857822:43
tristanCcorvus: on fedora, systemd was also missing some accounting options, you might need to add that too: https://github.com/podenv/silverkube/blob/master/silverkube.py#L68322:44
*** mattw4 has quit IRC22:45
*** jamesmcarthur has joined #zuul23:35
*** tosky has quit IRC23:38
*** jamesmcarthur has quit IRC23:59
openstackgerritJames E. Blair proposed zuul/zuul-jobs master: install-kubernetes: add support for cri-o runtime  https://review.opendev.org/68857823:59

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