Thursday, 2020-01-23

*** rfolco has quit IRC00:17
*** paladox is now known as paladox_UK_IN_EU00:20
*** rfolco has joined #zuul00:23
*** rf0lc0 has joined #zuul00:25
*** rfolco has quit IRC00:27
*** rf0lc0 has quit IRC00:29
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Revert "Make ara-report role to zuul_return an artifact"  https://review.opendev.org/70390200:30
pabelangerAJaeger: ianw: fbo: can we revert^? We are seeing an error in zuul.ansible.com: https://object-storage-ca-ymq-1.vexxhost.net/v1/a0b4156a37f9453eb4ec7db5422272df/ansible_18/18/addd84d133eddfb9966e633686d6346d49fa0ef1/check/ansible-test-network-integration-iosxr-netconf-python36/123ceb7/job-output.html#l457700:31
pabelangerthat looks to have been merged today00:31
pabelangerthis is because, we don't compress ARA html00:32
pabelangerso ara_generated is undefined00:32
*** rf0lc0 has joined #zuul00:32
clarkbpabelanger: that particular error is probably bceause you ansible 2.9 though right? it should be not foo is skipped00:34
clarkbor foo is not skipped? something like that00:34
clarkbsince ansible decided that you can no longer use the | filter syntax on conditionals00:34
pabelangermaybe, I haven't looked too much00:35
pabelangerjust noticed the error, and proposed revert00:35
pabelangeri don't think our jobs are breaking, but looking to confirm00:35
clarkbpretty sure that would fix it00:35
clarkbmaybe you can test locally and confirm?00:35
ianwthe same thing is in the line above, how come it doesn't cause an error there?00:36
pabelangerclarkb: I can tomorrow, just wrapping up for night. Hence the revert, otherwise would push up patch00:36
clarkbianw: oh interesting00:36
pabelangerianw: ara_compress_html | bool00:37
pabelangeris false00:37
pabelangerand defined00:37
pabelangerara_generate isn't defined00:37
pabelangerwe can add to default vars00:37
pabelangerbut is registered on line5600:37
ianwyeah, i guess it never gets evaluated in this context, but if it's a syntax error it's still an issue?00:38
clarkb| bool is also no longer valid iirc00:38
clarkboh wait I bet | bool actually is a filter not a conditional00:38
clarkbbecause it converts the input to a bool00:38
*** rf0lc0 has quit IRC00:38
ianwi'd agree on a quick revert while we think about that, mind if i just trim the commit message?00:38
clarkbwhat makes this confusing is that conditionals and filters were used the same before and three isn't a super clear "this is a conditional vs this is a filter" determination00:38
clarkbso when you are writing the yaml you have to think on it a bit00:39
pabelangerianw: go for it00:39
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Make ara-report role to zuul_return an artifact"  https://review.opendev.org/70390200:39
pabelangerk, have to drop now00:40
pabelangerthanks!00:40
clarkbI'm 99% sure that changing it to is skipped will fix it (but have to fix the other ones that ianw points out too00:41
*** jamesmcarthur has joined #zuul00:57
*** wxy-xiyuan has joined #zuul01:20
*** paladox_UK_IN_EU is now known as paladox01:24
*** jamesmcarthur has quit IRC01:36
*** jamesmcarthur has joined #zuul01:36
*** jamesmcarthur has quit IRC01:42
*** jamesmcarthur has joined #zuul01:42
*** jamesmcarthur has quit IRC01:55
*** jamesmcarthur has joined #zuul01:55
*** jamesmcarthur has quit IRC02:01
*** yolanda has quit IRC02:12
*** jamesmcarthur has joined #zuul02:14
*** yolanda has joined #zuul02:17
*** yolanda has quit IRC02:27
*** yolanda has joined #zuul02:34
*** jamesmcarthur has quit IRC02:38
*** jamesmcarthur has joined #zuul02:42
*** jamesmcarthur has quit IRC02:47
*** jamesmcarthur has joined #zuul02:50
*** sgw has quit IRC02:50
*** jamesmcarthur has quit IRC02:54
*** jamesmcarthur has joined #zuul02:59
*** bhavikdbavishi has joined #zuul03:04
*** bhavikdbavishi1 has joined #zuul03:06
*** jamesmcarthur has quit IRC03:07
*** jamesmcarthur has joined #zuul03:07
*** bhavikdbavishi has quit IRC03:08
*** bhavikdbavishi1 is now known as bhavikdbavishi03:08
*** rlandy|bbl is now known as rlandy03:17
*** sgw has joined #zuul03:29
*** jamesmcarthur has quit IRC03:53
*** jamesmcarthur has joined #zuul03:54
*** zxiiro has quit IRC03:56
*** jamesmcarthur has quit IRC04:15
*** jamesmcarthur has joined #zuul04:16
*** jamesmcarthur has quit IRC04:21
*** jamesmcarthur has joined #zuul04:46
*** mattw4 has joined #zuul04:48
*** mattw4 has quit IRC04:53
*** jhesketh has quit IRC04:54
*** jamesmcarthur has quit IRC04:54
*** jhesketh has joined #zuul04:55
*** stevthedev has quit IRC05:28
*** stevthedev has joined #zuul05:28
*** evrardjp has quit IRC05:34
*** evrardjp has joined #zuul05:34
*** reiterative has quit IRC05:41
*** wxy-xiyuan has quit IRC05:49
*** jamesmcarthur has joined #zuul05:50
*** jamesmcarthur has quit IRC05:55
*** swest has joined #zuul05:56
*** jamesmcarthur has joined #zuul05:58
*** jamesmcarthur has quit IRC06:03
*** raukadah is now known as chkumar|rover06:09
openstackgerritMerged zuul/zuul master: bindep: fixed wrong dep names on rpm platform  https://review.opendev.org/70340306:27
openstackgerritMerged zuul/zuul-jobs master: Revert "Make ara-report role to zuul_return an artifact"  https://review.opendev.org/70390206:45
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Fix ansible-2.9 skipped problem  https://review.opendev.org/70392206:48
AJaegerpabelanger, ianw, one more skipped problem - wonder why you did not hit that before, pabelanger ? ^06:48
AJaegerreading backscroll, clarkb, anything else needed? ^06:53
*** themroc has joined #zuul07:44
*** themr0c has joined #zuul07:48
*** themroc has quit IRC07:50
*** swest has quit IRC07:58
*** fungi has quit IRC07:59
*** gouthamr has quit IRC07:59
*** frickler has quit IRC07:59
*** Diabelko has quit IRC07:59
*** ssbarnea has quit IRC08:01
*** irclogbot_1 has quit IRC08:04
*** jpena|off is now known as jpena08:05
*** irclogbot_3 has joined #zuul08:06
*** tosky has joined #zuul08:13
*** avass has joined #zuul08:18
*** swest has joined #zuul08:45
*** fungi has joined #zuul08:45
*** gouthamr has joined #zuul08:45
*** frickler has joined #zuul08:45
*** Diabelko has joined #zuul08:45
*** openstackstatus has quit IRC08:48
*** saneax has joined #zuul09:04
*** coldtom has joined #zuul09:14
openstackgerritClément Mondion proposed zuul/nodepool master: add tags support for aws provider  https://review.opendev.org/70365109:25
*** pcaruana has joined #zuul09:30
openstackgerritClément Mondion proposed zuul/nodepool master: add tags support for aws provider  https://review.opendev.org/70365109:32
*** bhavikdbavishi has quit IRC09:59
*** sshnaidm|afk is now known as sshnaidm10:16
*** reiterative has joined #zuul10:38
reiterativeQuassel occasionally fails to auto-identify for me on freenode before trying to rejoin a channel that requires it. Is there any way to finesse this or is it just something I'll have to live with?10:43
reiterativeOops wrong channel! (But I guess someone here may know...)10:44
*** reiterative has quit IRC10:53
*** reiterative has joined #zuul10:53
*** hashar has joined #zuul11:32
*** bhavikdbavishi has joined #zuul11:51
*** jpena is now known as jpena|lunch12:00
*** ssbarnea has joined #zuul12:00
*** rf0lc0 has joined #zuul12:01
*** electrofelix has joined #zuul12:02
*** avass has quit IRC12:08
AJaegerwe have a couple of legacy maven build and upload jobs - has anybody worked on Zuul v3 ones so that we can replace the legacy ones?12:10
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Fix mqtt log url reporting when report-status-page is active  https://review.opendev.org/70398312:27
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Fix mqtt log url reporting when report-build-page is active  https://review.opendev.org/70398312:30
hasharAJaeger: hi, those maven jobs are just for the jenkins plugins arent they?12:38
hasharx/gearman-plugin comes to mind12:38
hasharand you archived x/zmq-event-publisher already great ;)12:40
AJaegerhashar: and for monasca12:52
AJaegerhashar: search in openstack-zuul-jobs for mvn12:53
*** bhavikdbavishi1 has joined #zuul13:00
*** bhavikdbavishi has quit IRC13:02
*** bhavikdbavishi1 is now known as bhavikdbavishi13:02
*** bhavikdbavishi has quit IRC13:08
*** bhavikdbavishi has joined #zuul13:10
*** jpena|lunch is now known as jpena13:16
pabelangerAJaeger: will test this morning13:32
pabelangerAJaeger: ah, won't be able to test, trusted job. I think we also want to add a test job to help validate13:41
* AJaeger won't have time for writing one the next days, happy to take one nevertheless13:44
*** jpena is now known as jpena|off14:12
*** jpena|off is now known as jpena14:20
openstackgerritwes hayutin proposed zuul/zuul-jobs master: bindep: Add missing virtualenv and fixed repo install  https://review.opendev.org/69363714:31
*** saneax has quit IRC14:36
*** ffloreth__ has joined #zuul14:48
*** themr0c has quit IRC14:48
*** hashar has quit IRC14:50
*** jamesmcarthur has joined #zuul14:53
*** ffloreth__ has quit IRC14:54
*** jamesmcarthur has quit IRC14:57
*** jamesmcarthur has joined #zuul15:00
*** pcaruana has quit IRC15:04
corvusreminder: call about zuul-operator in ~2 hours (1700 utc)15:08
openstackgerritMerged zuul/zuul-jobs master: Fix ansible-2.9 skipped problem  https://review.opendev.org/70392215:17
Shrewsswest: with your annotated logger changes, should we consider removing duplicate info from annotated log entries? for example: "[node_request: 100-0000000000] Locking request 100-0000000000"  Probably don't need the request ID in there twice now15:18
*** Goneri has joined #zuul15:18
Shrewstobiash: maybe you have thoughts on that too ^^15:18
corvusi think it would be fine to change tha to "[node_request: 100-0000000000] Locking request"15:20
corvusthat reads fine in the text logs; i'm assuming it would be fine in something that reads structured logs.  but that's where input from swest and tobiash would be helpful15:22
corvus(ie, if it were in something like logstash, would you have to make sure the right columns were enabled to get the full picture?)15:22
Shrewsyeah, it's mostly structured log parsing that i'm worried about15:24
*** plaurin has joined #zuul15:30
plaurinHello people!15:30
plaurinclarkb: Hey sorry I left quite unexpectedly yesterday after fixing the nodepool-kubernetes issue15:31
*** ffloreth__ has joined #zuul15:31
plaurinNot sure what you guys talked about later in the conversation. I don't use IRC a lot so not sure how I can go back to see what was talked about15:32
Shrewsplaurin: we have channel logs: http://eavesdrop.openstack.org/irclogs/%23zuul/15:33
tobiashcorvus, Shrews: I agree, we also still have the full text (minus logger, timestamp and log level) as one message and have additonally those fields as extra labels15:33
plaurinalso changed nickname, not sure why but I cannot login with plaurin34 anymore..15:33
plaurinoh great thx Shrews15:33
pabelangerplaurin: re nick, https://freenode.net/kb/answer/registration will allow you to register the nick to yourself15:34
pabelangerthen, if somebody is using it, ghost it back15:35
tobiashso it will work just fine for us if we remove that duplicated info15:35
Shrewstobiash: great. less bytes in the log15:35
plaurinI might just use this one right now "plaurin" I just needed to reset my password. I guess we can get rid of plaurin3415:35
corvustobiash: so whatever you're using to show the logs, shows the extra labels conveniently?15:35
tobiashcorvus: currently we parse those eytra labels but don't remove from the message15:36
plaurinpabelanger, corvus, tristanC: Thanks for your help yesterday. So basically I got passed the Gathering Fact issue in the job. But now the "prepare workspace" step cannot work because it uses "synchronise" module because it doesn't work with kubectl connection15:37
tobiashSo we see them just as text log but still can filter them efficiently by label15:37
tobiashand if we wanted we could filter them from.the message as well and have them just as label15:38
tobiashthat's just a matter of logstash config :)15:38
corvustobiash: ok, i wasn't sure how convenient that was for you15:38
pabelangerplaurin: I believe we still need to create prepare-workspace-k8s in zuul-jobs15:39
pabelangerso far, I have found https://review.opendev.org/631402/ for prepare-workspace-openshift15:39
plaurinyeah I am creating one for myself right now called prepare-workspace-kubernetes15:40
pabelanger++15:40
plaurinthx I'll take a look15:40
corvustristanC, plaurin, pabelanger: would https://review.opendev.org/631402 work on k8s too?15:40
pabelangerwould have to defer to tristanC15:41
plaurincorvus: I guess maybe with some modifications yes (probably remplace the 'oc' in rsync.yaml command, from a first quick look15:41
corvusi can't remember if oc works against plain k8s15:42
corvusplaurin: at the very least, that's a role you can copy/replace :)15:42
corvusif oc does work against plain k8s, maybe it will run as-is15:42
corvustobiash, pabelanger: ^ should we merge 631402?15:43
plaurin'oc' have rsync, kubectl doesn't. kubectl has 'cp' that might come in handy15:43
tobiashcorvus: I'll look in a bit15:44
tristanCcorvus: i assume oc rsync only uses vanilla k8s api15:44
plaurinI'm a bit surprised I tought zuul had kubernetes natively working for a long time.15:45
corvusme too15:45
plaurinI guess we'll make it so :P15:45
plaurinI never contributed directly to opendev but if I can help :)15:45
*** ffloreth__ has quit IRC15:46
tristanCtobiash: corvus: well, 631402 works, but to support both openstack and k8s from a single base job, here is what i wrote: https://softwarefactory-project.io/cgit/third-party-ci-config/tree/playbooks/upstream-base-pod/pre.yaml  (as documented and demonstrated in https://review.opendev.org/687435 )15:46
tristanCtobiash: corvus: thus we may want to make prepare-workspace works in both situation instead, but there is also the issue of the build-ssh-key which doesn't work on k8s...15:47
tristanCtobiash: corvus: and more generally, as explained on http://lists.zuul-ci.org/pipermail/zuul-discuss/2019-September/001015.html , to use zuul-jobs with kubectl we really need https://review.opendev.org/#/q/topic:zuul-jobs-with-kubectl too15:48
tobiashcorvus: according to docs oc is kompatible with kubectl as long no openshift only feature is used15:48
tristanCwhich makes me wonder if it wouldn't be easier to have a zuul/zuul-jobs-containers repository ...15:49
*** chkumar|rover is now known as raukadah15:49
corvustristanC: what would zuul-jobs-containers do?15:50
tobiashI think I'd prefer adding k8s support to the eyisting roles15:50
tobiashin case build-ssh-key that probably would be just a ignore15:51
pabelangerAs a person doing network and linux testing in same base playbooks, it is hard sometimes to deal with edge cases using 'all'. I've ended up creating a new group called 'appliance' to run specific playbooks against it for roles.15:51
corvusyeah, that sounds pretty straightforward.15:51
tristanCtobiash: me too, but it is already four month since the issue is documented and the fixes are up for reviews15:51
corvustristanC: if i may make a polite suggestion -- tell us what you want to have happen15:52
corvustristanC: getting big changes done isn't just pushing up changes and waiting for folks to review them15:52
corvustristanC: we need you to drive the plan from start to finish15:52
corvustristanC: so, tell us right now what's the next thing you need to have happen to make k8s better15:52
tristanCcorvus: well, we have been waiting for follow-up on http://lists.zuul-ci.org/pipermail/zuul-discuss/2019-September/001015.html15:52
corvustristanC: http://lists.zuul-ci.org/pipermail/zuul-discuss/2019-September/001020.html i think mordred agreed with your fetch-output plan15:54
corvusplaurin: based on what tobiash says about oc probably working against k8s, are you interested in trying out 631402 as written and testing that?15:55
plaurinsure thing15:57
corvustristanC: so i guess the next step is review topic:zuul-jobs-with-kubectl ?15:57
plaurin"as written" however not sure how this can work, I don't use openshift / oc15:59
tristanCcorvus: yes please, that's the biggest issue15:59
plaurinbasically I don'T have the oc cli15:59
tristanCcorvus: as asked http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2020-01-13.log.html#t2020-01-13T21:16:17 , is the zuul_use_fetch_output toggle still needed?16:00
corvusplaurin: iiuc, if you have "oc" installed on the executor, that job should work, so you'd need to install the oc client16:00
plaurinI see, yes I can test it however I don't think the end result should depend on oc for vanilla k8s16:01
plaurinI understand this patch is specifically for openshift16:01
tristanCtobiash: corvus: also, since we are introducing behavior such as mitogen, we could also make https://review.opendev.org/#/c/681553/ opt-in, then we wouldn't have to change the zuul-jobs16:01
corvusplaurin: well, if it works for both, we can use it for both16:01
corvuswho's adding mitogen?16:01
tristanCcorvus: https://review.opendev.org/#/c/657024/16:02
plaurinimho we cannot assume everyone want to depend on oc cli16:02
corvusplaurin: is there a particular reason why not?16:03
plaurinwell for my part I wasn't aware of the existence of this oc cli before today actually16:03
corvuswe can document why its used and how to install it16:03
tristanCplaurin: afaik, oc is the only cli that support a compatible interface for the synchronize feature we need16:03
plaurinI think kubectl cp can work too for people like me not using os/openshift16:04
plaurin' oc16:04
tobiashif it's documented it shouldn't matter if one installs kubectl or oc, as it's basically the same16:04
corvustristanC: i would not say we have committed to doing anything with mitogen at this point16:05
plaurinI use k3s from rancher. it depends on vanialla kubectl. I understand oc is juste a cli but I might not want to depend on it16:05
tristanCcorvus: alright, then i think the cleanest thing to do is ensure the zuul-jobs do not use synchronize16:06
*** jpena is now known as jpena|off16:06
tristanCplaurin: i'm not sure kubectl cp is really designed to upload potentienlla big directory with lots of files, but there could be a 'prepare-k8s-workspace' role that use it16:07
plaurinyes, that's what I think would be the best16:07
plaurinhuh I need a red hat account to get the oc cli??16:08
tristanCplaurin: nop, you can download it from https://www.okd.io/download.html#oc-platforms16:08
plauringot it16:09
tristanCplaurin: it is 100% free software, and you can rebuild it from source too if you prefer16:09
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Update roles/prepare-workspace-openshift/README.rst  https://review.opendev.org/70401716:09
corvustristanC: yeah.  separate from mitogen, i think 681553 is clever, and we certainly have modified other modules (the command module!).  i think the thing is that every time we do that we make upgrading ansible harder, so it's a big ongoing cost for us, and it's hidden.16:09
tristanCcorvus: though, i also with clarkb initial concern, a zuul-jobs playbook may not run with a vanilla ansible if we land 681553. while the command module modification shouldn't affect re-use16:11
plaurinseems oc does pretty much the same thing as kubectl what is it for?16:11
tristanCagree* with clarkb16:11
plaurin / diff16:11
tristanCplaurin: the rsync sub-command takes care of managing rsync or tar subprocess on the container16:11
tobiashplaurin: oc is essantially kubectl but supports additional features that openshift provides on top of kubernetes16:12
tristanCenabling efficient synchronization of files between the executor and the pod16:12
plaurinso it's a wrapper around kubectl to add more features?16:12
tobiashI'm not sure if it's a wrapper or a fork16:13
plaurinokay16:13
tristanCplaurin: yes, but it's not a wrapper, nor a fork, it just integrate the kubernetes client code and adds more functions to it16:13
plaurinlet me load that into my zuul server16:13
corvusthat's apparently how things work with go :)  vendor and enhance...16:14
plaurinI guess I just need to put the oc bin into my /usr/bin16:14
tristanCplaurin: yes16:14
corvustristanC: yeah, that's a good additional point for 55316:14
corvustristanC: regarding the question about whether the flag is needed -- iiuc, the plan is to add the flag to all the jobs, ask people to add fetch-output to their base jobs, switch the default, remove the flag.  does that sound right?16:15
plaurintristanC: okay done now I will get the openshift workspace patch and test that out16:15
tobiashcorvus, tristanC: I'm not sure I'd vote for 553 instead of adapting synchronize-workspace after reading the comments on the upstream pr16:17
tristanCcorvus: that works for me, then let me know when i should rebase the rest of the changes. Let's start with https://review.opendev.org/#/c/681882/16:17
plaurinI wonder what would be the difference between the kubernetes and openshift drivers for nodepool16:19
openstackgerritMerged zuul/zuul-jobs master: Add prepare-workspace-openshift role  https://review.opendev.org/63140216:19
*** mattw4 has joined #zuul16:20
tobiashtristanC: I have a question about this ^16:21
tobiashis this intended to the  'get k8s workspace' or 'get k8s pod' use case?16:21
corvusplaurin: they're almost the same16:23
tristanCtobiash: the 'get k8s workspace' needs a very different base job, where you may manage the container build outside of the pod. this is for the 'get k8s pod' use case16:24
tristanCtobiash: e.g. here is our openshift native job: https://softwarefactory-project.io/cgit/config/tree/zuul.d/_jobs-openshift.yaml#n416:25
tobiashtristanC: don't we have in the 'get k8s pod' use case an ansible post per pod?16:25
tobiash402 takes a list of pods while we could just get the pod from the hostvars instead16:26
corvusi thought 402 did get the list of pods from the hostvars16:27
plaurincorvus, tristanC: hey that works https://review.opendev.org/#/c/631402/16:27
corvusdoesn't the default of zuul.resources do that?16:27
corvusplaurin: \o/16:27
*** mattw4 has quit IRC16:27
plaurinI have other issues but that would probably my job really failing because of bad configuration,, but did get though the run start process16:27
*** mattw4 has joined #zuul16:28
*** tosky has quit IRC16:28
tristanCtobiash: from the hostvars may works indeed, don't remember why i used the zuul.resource instead.16:28
tobiashcorvus: if all pods are in the inventory (I'm not sure about that part, tristanC do you have a link at hand to an inventory of a k8s job?) then we can avoid the loop and just run against the host like regular tasks16:29
plaurinhttps://gist.github.com/plaurin84/bb4502361897d8177b2de5663894dbb116:29
tristanCtobiash: yes, please see the test-openshift-tox-py36-fedora-30 job result posted by 'Software Factory CI'16:30
tristanCplaurin: glad 402 works for you!16:31
tristanCtobiash: on https://review.opendev.org/#/c/682049/16:32
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: fetch-output-openshift: initial role  https://review.opendev.org/68204416:33
tristanCplaurin: next you'll need https://review.opendev.org/682044 to fetch the job logs from the pod16:33
plaurinlogs works for me16:34
plaurinwell I have my job-output.txt16:34
plaurinand my zuul-info/inventory16:35
tristanCplaurin: i mean build artifacts, like html report generated on the pod16:35
plaurinI might need that at some point yea16:35
plaurinchecking16:35
tobiashtristanC: so ansible_host is at least the pod name and I guess the namespace and context will be available after gathering facts automatically16:36
tristanCtobiash: perhaps?16:36
tristanCtobiash: but since zuul.resources got what we need, it seems safer to use that16:42
tobiashtristanC: yes, it works, just feels a little bit odd to treat the pods as data in this role and using them as regular hosts in other roles16:44
tobiashtristanC: I'm also thinking about modifying the standard synchronize-workspace role. Doing this should work with hosts instead of looping.16:46
tobiashbut as a separate role I guess it's ok16:47
tobiashsame for 682044, if we want to integrate this into the default fetch role, it also needs to be done with hosts16:48
plaurintristanC: I won'T be able to test 682044 now because I have some changes to make in my jobs to make this work. But I'll definitely need it16:48
tristanCplaurin: fwiw, here is our base pre job https://softwarefactory-project.io/cgit/config/tree/playbooks/base/pre.yaml  (not ideal, but that works for both openstack and openshift jobs)16:50
tristanCand here is how we do base post: https://softwarefactory-project.io/cgit/config/tree/playbooks/base/post.yaml16:50
plaurin👍️16:51
corvustristanC: q on 68174816:54
plaurinI realise I wasn't using the fetch output at all, we synchronised some logs files directly in the jobs.. I have some improvemenents to do!16:55
*** jamesmcarthur has quit IRC16:55
*** jamesmcarthur has joined #zuul16:55
*** jamesmcarthur has quit IRC16:57
tristanCcorvus: i suggest we look at fetch-javascript-output at the end, it was the most difficult because it has multiple strategy with regards to symlinks16:57
corvustristanC: okay.  i left +2s on the other first 3 changes in that topic16:59
* plaurin lunchtime16:59
AJaegertristanC: you better rebase and resolve merge conflicts...17:01
corvusmnaser, pabelanger, Shrews, fungi: operator call starting now if you want to join17:01
Shrewsnod17:02
pabelangerjoining17:02
mnaserdialing17:04
pabelangerconnected17:04
tristanCi'm in as well ( sip:6001@pbx.openstack.org )17:04
mnasersorry -- i'm having issues with my phone dialing in, please start and i'll do my best to dial in17:07
*** zxiiro has joined #zuul17:07
fungii'm on17:07
*** jamesmcarthur has joined #zuul17:08
corvusmnaser: there's a sip option if the pstn isn't working for you17:08
mnaseryeah i'm not equipped with a softphone but trying to setup one..17:09
openstackgerritMerged zuul/nodepool master: Cleanup exception logging in static provider  https://review.opendev.org/70282817:13
* tristanC raises hand17:16
*** jpena|off is now known as jpena17:27
*** jamesmcarthur has quit IRC17:29
openstackgerritFabien Boucher proposed zuul/zuul-jobs master: Make ara-report role to zuul_return an artifact  https://review.opendev.org/70404517:33
*** evrardjp has quit IRC17:34
*** evrardjp has joined #zuul17:34
tristanCpabelanger: one big advantage of gobased operator is that you can use the kubernetes-client object directly, which give you type safety17:38
mnaser^^17:38
tristanCbut it's also more complicated, you have to manage many details such as resources ownership, which are taken care of by ansible based operator17:39
tristanCand, you have to integrate with the whole kubernetes go library system, which is quite brutal to start learning go imo17:39
AJaegerpabelanger: want to review https://review.opendev.org/704045 ?17:41
*** mattw4 has quit IRC17:51
*** armstrongs has joined #zuul17:53
*** themroc has joined #zuul17:57
armstrongsI see there is a gitlab driver under active development is there any estimates on when it will be ready to use and how much work is remaining?18:00
*** armstrongs has quit IRC18:00
*** electrofelix has quit IRC18:06
tristanCarmstrongs already left, but here is the gitlab driver: https://review.opendev.org/#/q/status:open+project:zuul/zuul+branch:master+topic:gitlab18:08
tobiashfbo: did you see my comment on the first one of this? ^18:08
tobiashthe other changes lgtm18:09
tristanCtobiash: fbo is at a conf for https://devconfcz2020a.sched.com/event/YOtV/cicd-for-fedora-packaging-with-zuul18:10
tobiashah cool18:11
tobiashtristanC: do you know if there will be a video recording of this talk available? Sounds interesting18:13
tristanCtobiash: usualy they are published on youtube afterward yes18:16
tobiashcool18:16
pabelangertristanC: what has been feedback in fedora project about zuul in general for CI? Is this the first exposure to zuul for them?18:19
tristanCpabelanger: the recent feedback is onboarding issue where they don't want to add project to the tenant configuration, and when comparing with gitlab, they would just click 'gitlab ci' to get it running18:21
tristanCpabelanger: and the second difficulty is enforcing pr (which we don't) because power packager can't afford an extra step to click or approve the hundreds of change they do when maintaining their packages18:23
clarkbwikimedia also called out the explicit addition step as a problem with zuul in their evaluation. I know there was discussion on how to address this yesterday though18:24
clarkbit occured to me that another option might be to automate the change through the api? then peopel could have a web dashboard hit it?18:24
fungitristanC: what is "enforcing pr"?18:24
clarkbthat might make the ordering problem more explicit18:24
corvusyesterday we discussed supporting adding all projects.  that is a change that makes sense in zuul18:24
tristanCfungi: fedora packaging workflow usualy results in 'git push'18:25
*** jamesmcarthur has joined #zuul18:25
tobiashtristanC: so they do post-merge-ci?18:25
clarkbtristanC: zuul can operate on git push events...18:25
pabelangertristanC: yah, we try to encorce that with branch protections in github, but have seen push back18:25
tobiash(which is also possible with zuul)18:25
pabelangerlong term, I think solution for us is to drop merge commit access18:25
fungiclarkb: yeah, i was imagining some webui where a checkbox pushed a change proposal for the tenant config and then a special zuul pipeline configured to trigger on that push event to deploy the config and reload the scheduler18:26
pabelangerbut, giving up root is hard :)18:26
clarkbzuul's own release tooling operates on pushes18:26
tristanCtobiash: yes, fedora has an extra system to build package and propose promotion (called bodhi). Once a package has enough karma, then it gets pushed to cdn18:26
corvusbut regarding explicit addition -- there's no reason that "user edits yaml file" should be the only way a project gets added; zuul supports a pluggable system for getting the tenant config yaml, so it's possible to create any kind of integration to programatically generate the tenant yaml.18:26
tristanCclarkb: yes, that's how we are using it, on push events, but then it's no longer gating, which we would like to do with PR18:27
fungibasically folks want a ci system which tests things for them when they have time to look at test results, but lets them "move quickly and break things" when management puts them under a deadline18:27
pabelangerclarkb: I've really wanted to refactor some of the openstack releases project, into something more generic, but haven't had time18:27
clarkbtristanC: ok that sounds to me like less of a zuul problem and more of a workflwo problem? maybe I've misunderstood the concern18:27
clarkbI guess users might conflate the two18:27
fungicorvus: oh, great point, i forgot there was the option of the scheduler running something to generate the tenant config18:27
pabelangerfungi: yes, that is exact issue we deal with some time talking to ansible folks18:27
tobiashI guess it would be easy to write a small service that receives project webhooks and services the tenant config to zuul18:28
tobiashit could even be done incrementally by using smart-reconfig18:28
pabelangerfungi: so far, having stable tests really helps change peoples minds18:28
tobiashbut easier for the user would be to have this builtin18:28
tristanCclarkb: exactly, that's a workflow problem, resulting in zuul benefit less interesting over the other system that are being evaluated18:28
fungitobiash: or the scheduler's tenant config hook could just query your code review system for all repositories which have the checkbox ticked, and then you just need an api call to trigger it to reload18:28
tristanCclarkb: and it's also because fedora project content is not made to be used from the merge change, but from the package built out of them18:29
tobiashat least smart reconfig already works incrementally so the only thing to think through is how and where to get the projects into the tenant config18:30
fungitristanC: but couldn't building and installing the package and running validation tests on that be a job?18:30
fungii think that's how obs works18:30
corvustobiash: i'm not sure "one size fits all" for an automatically generated tenant config, which is why it's currently a hook for a script.  maybe there are ways to generalize it, but i think there would still be a lot of site specific configuration.18:30
fungiit's also what debian's source-only uploads do18:30
fungi(and ubuntu's since ages, i gather)18:30
fungiso it could be done pre-merge rather than post-merge18:31
tobiashcorvus: yes, with the hook script it's already now possible with say half a day of scripting18:31
tristanCfungi: yes, that is what fbo is going to demonstrate tomorrow, here you can zuul building a nodepool rpm, running integration test and voting on the PR: https://src.fedoraproject.org/rpms/nodepool/pull-request/718:31
fungitristanC: awesome. hopefully that sways some package maintainers into the pre-merge testing camp!18:32
tobiashif we want to build it into zuul we could maybe add a regex matching into the tenant config or a catch-all entry18:32
tobiashregex would be awesome to easily get all projects of a github org into the tenant18:33
tristanCfungi: yes, especially since it's compatible with the in-package testing (that uses ansible roles). But some package owner are managing hundreds of repos, and those are not interested in having a PR workflow18:33
fungizuul can certainly also just do post-merge testing for them, or periodic even18:33
corvustobiash: i agree, that would work; tristanC and i discussed that a bit yesterday; should be in eavesdrop18:34
clarkbfungi: tristanC and with artifact promotion you can build the package in the gate, test it, merge the changes, then push the rpm into $repo after merging18:34
clarkbits actualy very similar to how the container job setup works I think18:35
clarkbcontainers are just another type of package18:35
fungiyep, that's a great point18:35
corvustobiash: starts here http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2020-01-22.log.html#t2020-01-22T16:12:4118:35
pabelangerit would be also cool, if we have buildset-yum-repo too18:35
tristanCclarkb: that is what we are doing indeed, here are the templates: https://pagure.io/fedora-zuul-jobs/blob/master/f/zuul.d/templates.yaml18:35
clarkbtristanC: exciting!18:35
pabelangerwhich reminds me, really need to push up builset-galaxy job18:36
tristanCand the job using artifacts requirements: https://pagure.io/fedora-zuul-jobs/blob/master/f/zuul.d/jobs.yaml18:36
tobiashcorvus: thanks, I think if we expand the list of projects when parsing the tenant config we could just reuse smart-reconfig instead of adding a further method for reconfiguration18:37
corvustobiash: yeah now that you mention that, i agree.  not sure why i didn't think of that yesterday.  (cc tristanC)18:37
*** jamesmcarthur has quit IRC18:37
pabelangersince we have a lot of humans online, I'd love to get some reviews / feedback on https://review.opendev.org/703892/ UI change. zuul-build-dashboard job should give working demo, if you hover over status bar for a job now18:38
tobiashbut the use case is also solvable with the tenant config script hook. If that builds the project list outside of zuul the only think to do when a new project is added would be to trigger a smart-reconfig (because this already reloads the tenant config)18:39
tobiashthat would require zero changes to zuul18:40
clarkbpabelanger: on quick test of it I notice that when jobs are starting and before they have an executor assigned (when you get the spinny blue bar) it says a few seconds left which isn't accurate18:40
corvuscool, so tristanC and friends could try smart-reconfig with the fedora pagure now to see how that works, and we can later add regex support to the configloader to make that easier18:41
clarkbthen when the job starts it has an accurate estimate I think18:41
pabelangerclarkb: yah, open to idea how to fix. I think that is just the data we get back from estimated_time18:43
clarkbcorvus: tobiash meaning smart reconfig when you get a "project was added" event?18:43
tobiashclarkb: yes18:43
clarkbmakes sense, though you'd have to get the list somehow on next startup right?18:43
clarkb(maybe explicit listing covers that)18:43
tobiashsmart reconfig re-parses the tenant config -> config script fetches all projects -> smart reconfig reconfigures that tenant18:44
clarkbgot it18:44
plaurintristanC: I'm back. I might have a chance to try the fetch-output-openshift somewhere in the next hour or so18:44
plaurin04418:44
clarkbpabelanger: ya that might be a bug fix in the api18:44
corvusclarkb: this would also go hand-in-hand with the suggested change to support adding a regex to the tenant config; so if/when that is in place, the middle step can change from 'script' to 'zuul connection'18:44
clarkbpabelanger: have it return None or NaN or something when in that state18:45
tobiashcorvus: I was wrong, smart-reconfig works per tenant that has changed, not incrementally within a tenant, so we'd still need a further reconfig method, that works quite similar to the smart reconfig18:45
pabelangerclarkb: k, I'll poke at it shortly18:45
fungialternative workaround in the ui is to not report an estimate if "a few seconds" is what the api returns18:45
corvustobiash: ah.  (cc tristanC nevermind earlier cc :)18:46
tobiashbut it would be just a slight variant of the existing smart reconfig. Actually a hybrid of tenant reconfig and smart reconfig18:46
fungiincremental-reconfig or differential-reconfig (maybe shortened to inc-reconfig or diff-reconfig)>18:46
*** themroc has quit IRC18:47
*** jpena is now known as jpena|off18:48
*** openstackgerrit has quit IRC18:51
tobiashor I might be wrong again and smart reconfig doesn't delete the unparsed branch config18:54
tobiashin this case it really works incrementally already18:54
tobiashso after looking at the code I'm confident that smart reconfig works totally incrementally (aka, reloads only changed tenants and also re-uses cached config within tenants)19:02
tobiashcc tristanC double nevermind ;)19:03
tobiashzuul-maint: I'd have a couple of tiny fixes that would need a second review: https://review.opendev.org/#/q/status:open+project:zuul/zuul+branch:master+topic:small-fixes19:10
*** bhavikdbavishi has quit IRC19:10
clarkbI'll take a look19:11
clarkbtobiash: if you have a moment too curious what you think about the test change at https://review.opendev.org/#/c/703688/19:11
clarkbI think the testing results show it is about a minute faster according to stestr on similar hardware comparisons19:12
clarkbfor the whole suite19:12
clarkbnot a huge chunk but is measurable19:12
tobiashclarkb: It might or might not make much difference for the whole test suite, but I can imagine that even then it is *very* useful in local debugging e.g. when adding a new ansible version19:14
clarkbthat is a good point since you'll be focused on running that ansible verion's tests19:15
tobiashyes19:15
tobiashwhen debugging a single test case it really matters if the test runs in 30s or 2minutes19:15
tobiashI have the same issue with test_playbook actually19:15
tobiashI don't like running that locally as a single test case as it takes so long ;)19:16
clarkbya thats the next slowest test after these ones19:16
clarkbmuch harder to make faster though19:16
clarkbcould possibly split it up, but not sure that helps19:16
tobiashpabelanger: you might be interested in https://review.opendev.org/702378. This fixes occasional wrong change urls with github.19:24
pabelangertobiash: I am, we see that in gate pipeline often, and returns just api url19:26
pabelangerwill review soon19:26
tobiashthx19:26
*** gmann is now known as gmann_lunch19:26
tobiashclarkb: I think I addressed your comment on 684414 (fix canceling builds in starting phase)19:27
clarkbanyone know why nodepool would delete an unused node after 22 seconds?19:28
tobiashclarkb: I guess there was no config change?19:28
clarkbhttp://paste.openstack.org/show/788727/19:28
clarkbno config change19:28
clarkbmaybe zuul decided it didn't need the node afterall? but you should keep the unused ready node until the timeout right?19:29
clarkbthat is a min ready request too19:30
clarkbdid we break that somehow?19:30
tobiashnodepool should delete the node only if it's marked as used or in-use19:30
tobiashclarkb: could it be that zuul used it for a job and then aborted the job (maybe because of a gate reset)?19:31
clarkbtobiash: it is possible19:31
clarkbexcept it did it to the next node too19:31
clarkbI think we may have broken min-ready somehow19:31
Shrewswell, nodepool will delete the oldest unused node if it needs to free up capacity for another node, but what's curious is that node should be assigned to a request (or have been marked USED at least)19:32
clarkbShrews: it is from min ready19:32
clarkbwhich is why it doesn't19:33
Shrewsah19:33
clarkbso the conflict here is between min-ready and deleting the oldest unused node19:34
clarkbthat kinda makes me wonder if we should just stop using min ready19:34
clarkbopendev at least since we spend a lot of time at capacity19:34
Shrewsclarkb: the theory is, if the pool thread must pause request handling (b/c capacity), deleting the oldest, unused node would help (hopefully) get it unpaused faster19:34
fungii don't think opendev gets a bunch of benefit from min-ready these days, but other environments with much higher node setup costs and less frequency of quota exhaustion still might19:34
tobiashclarkb: that could make sense, we stopped using min-ready a year ago19:34
clarkbShrews: ya the problem is we are just spinning with the min ready19:35
tobiashhowever we stopped using it because we have many different images19:35
clarkbShrews: so we delete it, then boot it again then delete it and never make progress on the nodes that jobs demand19:35
clarkbor at least not the intended progress19:35
fungiin opendev our boot times are low enough that the additional quota can be put to better use in the available pool, i agree19:36
pabelangerfungi: agree, I've aways wanted to remove that logic for opendev, since moving to zuulv319:36
fungibut it still sounds like a legitimate bug which should be fixed (or at least optional behavior which should be considered mutually-exclusive)19:36
fungilike if you're going to use the unused node cannibalization feature then don't set a min-ready on your nodes or they'll get into a fight19:37
fungior add some intelligence to pause min-ready booting when quota utilization crosses a certain threshold19:38
tobiashhrm, min-ready booting is decoupled from the providers afaik19:38
pabelangerso, we don't set min-ready in nodepool for zuul.a.c, but sometime get leaks. So, node is online and ready, for us we set max-read-age: 600, so help make sure they get cleaned up19:39
tobiashbut maybe it works if the provider ignores min-ready requests if it got paused in the last 10 minutes19:39
fungithat could be a solution19:39
tobiashShrews: what do you think?19:39
fungiso your min-ready nodes accumulate in your less-active providers when possible, though more likely your providers see proportional usage so min-ready requests would just get refused globally anyway19:40
fungithe timeframe there could lead to a hysteresis though i suppose19:41
fungiat the right quota sizes and constant utilization around the threshold19:41
fungiyou could see min-ready nodes bounce unhelpfully back and forth between providers as they put them under or at quota19:42
fungibut maybe in practice that's not an issue or it's infrequent enough behavior to ignore19:43
clarkbtobiash: the race fix in 684414 lgtm. One thing I notice on rereview is line 484 of https://review.opendev.org/#/c/684414/6/zuul/executor/client.py the old get was for data['worker_name'] but now refer to build.worker.name. Does worker_name get translated into just name by updateFromData?19:43
* clarkb is double checking this now too19:43
Shrewswell, we could build in some sort of buffer for declining min-ready requests (either timeframe since pause, or how close we are to capacity). i'm not sure what other impact that might have19:43
clarkbaha it is. ok +219:43
tobiashclarkb: awesome, thanks19:44
Shrewsclarkb: is the current situation hurting anything? or are we just interested in avoiding unnecessary node churn?19:45
corvusmin ready only helps opendev on weekends :)19:45
clarkbShrews: my concern would be the goal is to ensure we get nodes for jobs but are not and that is creating unnecessary churn19:45
Shrews++19:45
clarkbShrews: if we were managing to get nodes for jobs then the churn would be fine19:46
clarkbbut as is it is just a waste19:46
fungiShrews: yep, though again min-ready nodes count toward quota, making it a feedback loop so mixing in a delay once again means likely hysteresis19:46
clarkbcould we have a provider that just transitioned from at capacity to under, ignore min-ready requests unless those are the only requests available?19:46
tobiashwhat priority do the min-ready have?19:47
clarkb10019:47
clarkbmaybe lower their priority?19:47
clarkb(I think that I read my log paste above properly to get the priority)_19:47
fungiShrews: we could maybe do like hvac compressors do to avoid short-cycling and force an over/under on the quota too19:47
tobiashclarkb: correct, so essentially min-ready have the same prio as the first item in the gate19:48
Shrewsyeah, we could totally lower their priority19:48
fungias long as nodes aren't cannibalized at or near the same quota threshold where we consider it safe to build min-ready nodes we avoid short-cycles19:48
tobiashI think lowering the prio would solve this mostly already19:49
clarkbzuul maintainers I think https://review.opendev.org/#/c/684414/6 is ready now if you want to be second reviewr. Its a bit more involved than the simple fixes from tobiash earlier but should help address a fun bug19:49
fungitobiash: clarkb: oh, yep, the reprioritization seems like that could also be a much easier fix19:49
*** gmann_lunch is now known as gmann19:52
*** openstackgerrit has joined #zuul19:54
openstackgerritClark Boylan proposed zuul/nodepool master: Lower min-ready request priority  https://review.opendev.org/70405819:54
clarkbis it as simple as ^19:54
tobiashclarkb: you were faster ;)19:55
corvusclarkb, tobiash: i will reviwe 414 after lunch19:55
clarkbI had to figure out which direction things were sorted in :)19:55
tobiashclarkb: but I'd suggest to use a different prio as the priority is sorted alphabetically19:56
clarkboh19:56
clarkbright its string not numberic19:56
tobiashmy too slow patch used 90019:56
clarkbk19:56
tobiashbut you can use anything you like >=40019:57
corvusyou could also change 'getNodeRequests' to map to int first :)19:57
openstackgerritClark Boylan proposed zuul/nodepool master: Lower min-ready request priority  https://review.opendev.org/70405819:58
clarkbcorvus: I worry that might have unexpected behavior differences19:58
clarkbbut that could be a good followup if we can dobule check it?19:58
tobiashcorvus: thanks :)19:59
corvusoh wait, getNoteRequests isn't relevant19:59
clarkb_assignHandlers20:00
clarkbI think20:00
corvusor maybe it is, via nodeRequestIterator20:00
corvusclarkb: ah yep, it's resorted in assignhandler20:01
tobiashoh, actually it's a little bit more complicated: https://opendev.org/zuul/nodepool/src/branch/master/nodepool/launcher.py#L17920:01
corvusbut still by string20:01
corvusyeah, that's the key line20:01
corvusso stick an int on [0] and [2] in that tuple20:02
tobiashyes, then it would be int sorted20:02
fungiis there any chance someone might have used non-numeric priorities there?20:02
corvusnope20:02
fungiokay, so don't have to worry about that being a non-backward-compat change20:03
corvuszuul sets the priority and uses only 100, 200, and 300 (plus or minus 1)20:03
corvusi think zuul can set a priority of 99; i'm unsure if that's 099 or not20:03
fungicool, yeah as long as those aren't user-configurable strings somewhere it should be safe20:03
corvuswhich means we may already have a latent bug... trying to confirm20:03
tobiashI found tests/unit/test_v3.py:        self.assertEqual(reqs[0]['_oid'], '099-0000000001')20:04
fungioh, though you make a good point, we'd still be altering the sort order if different orders of magnitude are in use20:04
tobiashso we have a test to rule out that latent bug :)20:04
corvustobiash: whew :)20:04
funginice!20:04
fungiit's like someone thought of everything20:04
corvusShrews: 704058 lgtm if you want to +W20:05
* corvus lunches20:05
tobiash099 is btw the 'there is already a paused job taking resources so use highest prio for child' priority20:05
openstackgerritClark Boylan proposed zuul/nodepool master: Sort requests by numeric provider value  https://review.opendev.org/70406020:05
Shrewsyeah, i'm just looking for any unit tests that might need changing20:06
clarkbthat may want a try except just in case the zk data is manually edited poorly20:06
clarkbbut I need to eat lunch then see the optometrist so feel free to edit if necesary20:06
clarkbhopefully they won't dilate my eyes and I'll be useful after20:07
tobiashShrews: I ran a local test run on 704058 and it's green20:08
*** openstackstatus has joined #zuul20:09
*** ChanServ sets mode: +v openstackstatus20:09
*** sshnaidm is now known as sshnaidm|afk20:09
*** jamesmcarthur has joined #zuul20:11
Shrewsi think the change to sort by numeric value might need more thought. it's currently inconsistent with storing a request with a string priority20:16
openstackgerritTobias Henkel proposed zuul/zuul master: Support emitting warnings via zuul_return  https://review.opendev.org/65152620:21
openstackgerritMerged zuul/zuul master: Fix bogus error message on reconfigure event  https://review.opendev.org/70322920:23
openstackgerritMerged zuul/zuul master: Add job.override-checkout to rest api  https://review.opendev.org/70323920:23
openstackgerritTobias Henkel proposed zuul/zuul master: Use implied branch matcher for implied branches  https://review.opendev.org/64027220:23
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Use mirror infrastructure during zuul-quick-start  https://review.opendev.org/64944820:33
openstackgerritMerged zuul/zuul master: Change links on projects page to canonical name  https://review.opendev.org/70324020:38
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Use mirror infrastructure during zuul-quick-start  https://review.opendev.org/64944820:53
openstackgerritMerged zuul/zuul master: Correctly handle noop on job page  https://review.opendev.org/70324220:59
*** johanssone_ has joined #zuul21:05
*** openstackgerrit has quit IRC21:18
*** irclogbot_3 has quit IRC21:18
*** jhesketh has quit IRC21:18
*** yolanda has quit IRC21:18
*** panda has quit IRC21:18
*** adam_g has quit IRC21:19
*** johanssone has quit IRC21:19
*** mgoddard has quit IRC21:19
*** jpena|off has quit IRC21:19
*** aluria has quit IRC21:19
*** openstackstatus has quit IRC21:20
*** notnone is now known as at_work21:22
*** irclogbot_0 has joined #zuul21:26
*** plaurin has quit IRC21:28
corvusremote:   https://review.opendev.org/704068 Change default Gerrit HTTP auth method21:54
corvus(gerritbot seems to be split)21:54
*** openstackgerrit has joined #zuul22:01
*** jhesketh has joined #zuul22:01
*** yolanda has joined #zuul22:01
*** panda has joined #zuul22:01
*** adam_g has joined #zuul22:01
*** mgoddard has joined #zuul22:01
*** jpena|off has joined #zuul22:01
*** aluria has joined #zuul22:01
*** jamesmcarthur has quit IRC22:02
openstackgerritTobias Henkel proposed zuul/zuul master: Use apt mirror infrastructure during zuul-quick-start  https://review.opendev.org/64944822:04
*** tosky has joined #zuul22:16
*** armstrongs has joined #zuul22:34
*** Goneri has quit IRC22:37
*** armstrongs has quit IRC22:42
clarkbcorvus: for https://review.opendev.org/#/c/704068/1 does opendev need a change to hardset digest?23:13

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