Wednesday, 2020-05-06

openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] ensure-tox use venv  https://review.opendev.org/72573700:19
*** rlandy has quit IRC00:20
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] ensure-tox use venv  https://review.opendev.org/72573700:26
*** rfolco has quit IRC00:35
*** jamesmcarthur has joined #zuul00:37
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip : fix Xenial exported virtualenv command  https://review.opendev.org/72574300:57
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip : fix Xenial exported virtualenv command  https://review.opendev.org/72574301:06
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip : fix Xenial exported virtualenv command  https://review.opendev.org/72574301:09
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-pip : fix Xenial exported virtualenv command  https://review.opendev.org/72574301:15
*** jamesmcarthur has quit IRC01:17
*** swest has quit IRC01:53
*** wxy has joined #zuul01:59
openstackgerritMerged zuul/zuul-jobs master: ensure-pip : fix Xenial exported virtualenv command  https://review.opendev.org/72574302:06
*** swest has joined #zuul02:09
*** jamesmcarthur has joined #zuul02:33
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Remove opensuse-15-plain testing  https://review.opendev.org/72575002:42
openstackgerritIan Wienand proposed zuul/zuul-jobs master: ensure-tox: use venv to install  https://review.opendev.org/72573703:01
*** jamesmcarthur has quit IRC03:06
*** jamesmcarthur has joined #zuul03:06
*** bhavikdbavishi has joined #zuul03:06
*** jamesmcarthur has quit IRC03:11
*** bhavikdbavishi1 has joined #zuul03:16
*** bhavikdbavishi has quit IRC03:17
*** bhavikdbavishi1 is now known as bhavikdbavishi03:17
*** jamesmcarthur has joined #zuul03:41
*** openstack has joined #zuul04:24
*** ChanServ sets mode: +o openstack04:24
*** evrardjp has quit IRC04:35
*** evrardjp has joined #zuul04:36
*** jamesmcarthur has quit IRC05:04
*** jamesmcarthur has joined #zuul05:05
*** jamesmcarthur has quit IRC05:11
*** jamesmcarthur has joined #zuul05:11
*** sanjayu__ has joined #zuul05:14
*** sanjayu_ has quit IRC05:17
*** sanjayu__ has quit IRC05:48
*** ysandeep|away is now known as ysandeep05:51
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Remove some temporary files  https://review.opendev.org/72565005:54
*** saneax has joined #zuul05:54
*** jamesmcarthur has quit IRC06:00
*** jamesmcarthur has joined #zuul06:01
*** dpawlik has joined #zuul06:03
*** jamesmcarthur has quit IRC06:06
*** ysandeep is now known as ysandeep|away06:12
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Move queue from pipeline to project  https://review.opendev.org/72018206:14
*** ysandeep|away has quit IRC06:29
*** jamesmcarthur has joined #zuul06:39
*** bhavikdbavishi has quit IRC06:56
AJaegertobiash: could you check https://review.opendev.org/#/c/723654/ , please?07:03
tobiashAJaeger, avass: why do you prefer failed_when?07:05
*** saneax has quit IRC07:06
tobiashinitially I used ignore_errors there intentionally to not mask errors in the log07:06
*** bhavikdbavishi has joined #zuul07:10
*** saneax has joined #zuul07:11
*** yolanda has joined #zuul07:14
*** sanjayu_ has joined #zuul07:17
*** jcapitao has joined #zuul07:18
*** saneax has quit IRC07:19
avasstobiash: I think your change just got caught up when a changes a lot of places where ignore_errors when failed_when was actually wanted07:20
avassi changed*07:20
tobiashah ok07:21
avasssince ignore_errors still show it as an error, but failed_when: false should be used when the task can't error, like checking if something is installed to know if it should be installed or not07:22
tobiashavass: I also looked at the rest of your topic and for the other changes failed_when really makes more sense07:22
AJaegerthanks, tobiash07:23
avasshow ready is the zuul-operator by the way? :)07:24
tobiashI think tristanC is using it07:24
*** bhavikdbavishi has quit IRC07:25
avassnice07:25
avasswhenever I have more time I think I'll see if we can start using that then07:25
AJaegerzuul-jobs maintainers, could you review https://review.opendev.org/725650 again, please?07:30
*** tosky has joined #zuul07:30
*** rpittau|afk is now known as rpittau07:31
openstackgerritAlbin Vass proposed zuul/zuul-operator master: Doc fix: s/developper/developer  https://review.opendev.org/72577207:32
avasszuul-maint: anyone wanna take a look at enabling callbacks? https://review.opendev.org/#/c/717260/07:39
tobiashavass: I'll have a look later today07:41
avasstobiash: thanks!07:44
*** openstackstatus has quit IRC07:46
*** openstack has joined #zuul07:50
*** ChanServ sets mode: +o openstack07:50
tobiashavass: were you the one who had a wip version of windows log streaming (I remember someone mentioned it)?07:56
*** jpena|off is now known as jpena07:58
*** dmellado has quit IRC07:58
*** bhavikdbavishi has joined #zuul07:58
*** mhu has joined #zuul08:00
*** dmellado has joined #zuul08:04
*** tumble has joined #zuul08:06
avasstobiash: yeah, but it's very coupled to our specific usecase at the moment08:08
tobiashok, so I guess it's not ready to push up a wip version so we can work together on finishing it?08:08
*** dpawlik has quit IRC08:09
avasstobiash: but the idea is almost the same as the linu one08:09
*** dpawlik has joined #zuul08:09
avasstobiash: not really, but I can see if I can make it ready enough and push it08:09
tobiashcool08:09
avassbut it's using windows services instead08:11
tobiashah, so you're using a windows service for the streaming component and probably a forked win_shell plugin as in linux?08:12
avassyeah :)08:13
avasstobiash: actually, we didn't fork win_shell since we're having win_shell call psexec to get an interactive session on the remote, so we're piping the output from that to a file that's read but the log streamer08:22
avassthat's the part that is a bit too coupled to our usecase :)08:23
*** jamesmcarthur has quit IRC08:41
*** sgw has quit IRC08:48
openstackgerritMerged zuul/zuul-jobs master: Remove some temporary files  https://review.opendev.org/72565009:00
*** jamesmcarthur has joined #zuul09:16
*** sugaar has quit IRC09:16
*** sugaar has joined #zuul09:17
*** bhavikdbavishi has quit IRC09:25
*** jamesmcarthur has quit IRC09:26
*** bhavikdbavishi has joined #zuul09:26
openstackgerritSimon Westphahl proposed zuul/nodepool master: Expose image build requests in web interface  https://review.opendev.org/72581009:42
openstackgerritSimon Westphahl proposed zuul/nodepool master: Expose image build requests in web interface  https://review.opendev.org/72581009:43
*** rpittau is now known as rpittau|bbl09:44
*** brendangalloway has joined #zuul09:49
brendangallowayIs there a method by which the zuul file filters could be used to setup arguments to a job, rather than triggering different jobs?09:53
*** jamesmcarthur has joined #zuul09:57
*** jamesmcarthur has quit IRC10:07
avassis it possible to put allowed-labels on project level instead of tenant level?10:36
avassI'm guessing it's not10:36
*** jcapitao is now known as jcapitao_lunch10:37
*** jamesmcarthur has joined #zuul10:43
*** jamesmcarthur has quit IRC10:43
*** jamesmcarthur has joined #zuul10:43
*** jamesmcarthur has quit IRC10:44
*** jamesmcarthur has joined #zuul10:44
*** jamesmcarthur has quit IRC10:51
avassbrendangalloway: don't think so10:53
tobiashbrendangalloway: what's the use case?10:56
tobiashavass: allowed-labels is currently only possible on tenant level10:57
*** jamesmcarthur has joined #zuul10:58
*** jamesmcarthur has quit IRC10:59
*** jamesmcarthur has joined #zuul10:59
*** jamesmcarthur has quit IRC11:01
brendangallowaytobiash: We have a build script that packages a number of tightly coupled components together (all live in the same repo but with separate build scripts) and then creates a single build artefact that can be tested at gate.  We're trying to reduce build times by only building the components that have changed, and using cached versions for the11:01
brendangallowayothers.  I'd like a way to inform the build script as to which components should be used from cache, and to be able to pass that info to a post-test job that will cache whichever components were freshly built if the tests passed11:01
*** jamesmcarthur has joined #zuul11:02
*** sanjayu__ has joined #zuul11:03
tobiashbrendangalloway: you could do this within the job by diffing against origin/<target branch>11:03
brendangallowayok - I was hoping to be able to do it at zuul level since the existing file filter syntax is nice and clear11:05
tobiashbrendangalloway: you could do e.g. this to get the changed files of the change: git diff --name-only origin/master HEAD11:05
*** sanjayu_ has quit IRC11:05
*** jamesmcarthur has quit IRC11:07
brendangallowaytobiash: we will tae that approach, thanks11:07
*** bhavikdbavishi has quit IRC11:25
*** rfolco has joined #zuul11:30
*** jcapitao_lunch is now known as jcapitao11:39
*** jpena is now known as jpena|lunch11:39
*** jamesmcarthur has joined #zuul11:40
*** rlandy has joined #zuul11:58
openstackgerritJan Kubovy proposed zuul/zuul master: Scheduler's pause/resume functionality  https://review.opendev.org/70973512:05
mordredbrendangalloway: you might be able also to do what you're looking for with requires/provides and zuul artifacts. while it's not exactly the same, the docker image jobs do a similar thing to what you're talking about12:06
mordredbrendangalloway: to do that I thnik what you'd wind up doing is having each component have it's own build job with file filters that triggers the specific script. then you can have them use zuul_return to return the build component. then have a job which soft-depends on all of them (so it's ok if some of them don't run) which pulls the artifacts returned by the jobs (it can find out which ones to pull by12:09
mordredreading zuul_return data) and then pull things from cache if nothing has built it12:09
*** hashar has joined #zuul12:11
brendangallowaymordred:  I was not aware of the soft dependency option, that might also be an option12:11
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Document the missing feature  https://review.opendev.org/71875512:11
mordredbrendangalloway: it's pretty useful - it says to depend on a job but only if it ran, so it's not an error if a file matchers causes it to not run12:12
brendangallowaymordred:  Yes, we've had issues with hard dependencies due to exactly that issue.  Is it a new feature, I don't recall seeing it before12:14
mordredbrendangalloway: it's also possible that full separate build jobs would introduce too much overhead - so another thing you might consider is to just make the per-component jobs be tiny nodeless jobs with file matchers that just do a zuul_return with the name of their component - then have your main build job read the zuul return to build the list of needed components12:14
mordredbrendangalloway: I don't think it's that new - we use it extensively in opendev12:14
brendangallowaymordred: that is also a good suggestion, thanks for the ideas12:16
*** rpittau|bbl is now known as rpittau12:18
mordredsure thing!12:19
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Retry buildx builds  https://review.opendev.org/72584312:23
mordredtobiash, avass: if you have a sec, super simple patch ^^12:23
avassmordred: done :)12:24
tristanCavass: installing the zuul-operator results in a working zuul, we are using it to validate base jobs, though some more work is needed to make it more production ready, see: https://review.opendev.org/71875512:24
*** jamesmcarthur has quit IRC12:25
avasstristanC: alright, we won't start using it anytime soon anyway12:26
*** Goneri has joined #zuul12:38
*** jpena|lunch is now known as jpena12:45
*** sanjayu_ has joined #zuul12:47
openstackgerritMerged zuul/zuul-jobs master: Retry buildx builds  https://review.opendev.org/72584312:47
*** bhavikdbavishi has joined #zuul12:49
*** sanjayu__ has quit IRC12:50
*** bhavikdbavishi1 has joined #zuul12:56
*** bhavikdbavishi has quit IRC12:58
*** bhavikdbavishi1 is now known as bhavikdbavishi12:58
*** jamesmcarthur has joined #zuul13:01
openstackgerritMonty Taylor proposed zuul/zuul master: Tie status filter text to pathname  https://review.opendev.org/72585013:02
*** sgw has joined #zuul13:06
*** cdearborn has joined #zuul13:11
mordredcorvus: when you're up - we're getting 500s from zuul-registry trying to buildx the nodepool-builder image - and they seem to be consistent13:12
mordredcorvus: I grabbed the logs from the current buildset registry (luckily the k8s test takes a while so the buildset registry is easy to hop on to without a hold)13:12
mordredand they do show a traceback13:12
*** rfolco is now known as rfolco|rover13:13
*** jamesmcarthur has quit IRC13:21
corvusmordred: got a link?13:31
mordredhttps://bb5882b725b63c90f428-d701f6a98461967df274f184d5a7d3cd.ssl.cf5.rackcdn.com/725611/1/check/nodepool-build-image/2dc0a25/13:31
mordredcorvus: that's the failed job logs13:31
mordredcorvus: the registry logs I grabbed are on the mttest-docker node in ~mordred/registry.logs13:32
mordredcorvus: although the node is still currently there: root@2001:470:e126:1:f816:3eff:fe41:f1fa13:32
mordred(the buildset registry node)13:33
corvusmordred: can you paste the logs?13:33
mordredyeah13:33
corvusokay, we're talking about this change: https://review.opendev.org/72561113:33
mordredcorvus: yeah - but it failed same way with the parent13:34
corvusand the job is nodepool-build-image13:34
mordredyes13:34
corvusthe previous build (before the current recheck) failed; was that the same error?13:35
mordredcorvus: it was the other thing we've seen: failed to solve: rpc error: code = Unknown desc = failed commit on ref "layer-sha256:3695e93b8b00a1d17e972a09de4338742c063b0b8242acb75d4c9250df1229de": unexpected size 0, expected 204193013:35
mordredso it's possible there are 2 different issues - one that happens sometimes and one that seems to happen consistently13:36
corvusit reported this traceback: https://zuul.opendev.org/t/zuul/build/259910ba7bf644299d532ca505fe51b9/log/docker/buildset_registry.txt#592-60613:36
mordredcorvus: http://paste.openstack.org/show/79319613:37
corvuslooks pretty similar13:38
mordredcorvus: there's the logs I captured from the buildset registry - although I now see you don't need those :)13:38
corvusi do need them :)13:38
mordredoh good!13:38
corvusmordred: i see the same two errors logged in both the previous and current runs of the job13:38
mordredcorvus: line 388 in the paste is a different traceback13:38
mordredoh - that sure did truncate13:39
corvusmordred: that's here: https://zuul.opendev.org/t/zuul/build/259910ba7bf644299d532ca505fe51b9/log/docker/buildset_registry.txt#49813:39
mordredcorvus: yeah - I think now that the job has reported - that log has what I was able to grab13:39
corvuswell, i was linking to the previous one13:40
mordredah. nod13:40
corvusi'm still working on "identify the bug mordred wants me to investigate" :)13:40
corvusmordred: so far, i'm seeing the same tracebacks in both logs13:40
corvusmordred: but i agree, buildx reported 2 different errors13:41
corvusmordred: there seem to be multiple puts going on; perhaps it's the same underlying issue but with a race13:41
corvusmordred: i'll try to tease out the sequence from the logs13:41
mordredcorvus: yeah. ah - yeah13:41
mordredcorvus: you saw https://zuul.opendev.org/t/zuul/build/17b1cc2f42634141b991aa8d33fa32f9 failed to solve: rpc error: code = Unknown desc = failed commit on ref "layer-sha256:c677d2dff43d9861d4bf54db3fa3a4431c1621e7f4f940e78d10ad37966b0c81": unexpected status: 500 Internal Server Error13:42
openstackgerritJames E. Blair proposed zuul/zuul master: Add some debug lines to help with the loading_errors bug  https://review.opendev.org/72573213:44
openstackgerritSimon Westphahl proposed zuul/nodepool master: Expose image build requests in web UI and cli  https://review.opendev.org/72581013:56
openstackgerritSimon Westphahl proposed zuul/nodepool master: Expose image build requests in web UI and cli  https://review.opendev.org/72581013:57
openstackgerritSimon Westphahl proposed zuul/nodepool master: Expose image build requests in web UI and cli  https://review.opendev.org/72581013:58
*** jamesmcarthur has joined #zuul14:01
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: WIP configure cache-to and cache-from for buildx  https://review.opendev.org/72586214:02
corvusmordred: wow, it really is uploading the same layer twice at the same time.  the registry is not safe in that case and it errors.  i can't say why buildkit reports 2 different errors here -- perhaps they represent each of the 2 different upload threads on the buildkit side.14:03
mordredcorvus: yeah - maybe so14:04
mordredcorvus: also - wow14:04
corvusmordred: we should probably make the registry more robust in this case.  but i also think it would be interesting to understand why buildkit uploads the same layer twice; maybe it's juts nuts, or maybe there's some subtle thing the registry isn't doing that it expects that triggers this.14:04
mordredcorvus: agree on both points14:05
mordredcorvus: maybe ... so - the way layers work on top of multi-arch base images is sort of interesting14:05
mordredin that, for instance, python-base and python-builder are on top of debian which _is_ multi-arch but didn't do any multi-arch things themselves so are still multi-arch14:06
mordredso - if there are steps in the nodepool dockerfile which are the same - then we have 2 builders potentially building the "same" layer14:06
corvusmordred: ooooh good idea14:07
mordredand the layers really will be the same for steps that don't do anything platform specific14:07
mordred(since these are hashed only by their content - not content+context like git)14:08
corvusi'm not aware of a way for us to figure out what these layers are14:08
corvus(at least from the build logs we have)14:08
corvusthe shas are different from the 2 different zuul job builds, so at least there's something that changed between the 2 runs.  but within a single run, perhaps the state is consistent enough to do what you suggest14:09
mordredme either - but I think it will actually be most of the layers in the nodepool image that aren't the apt-get install step14:09
mordredcorvus: yeah14:09
*** bhavikdbavishi has quit IRC14:09
corvusmordred: if that's the case, i'm not sure there's anything we can do.... unless we can stagger the multiarch builds a little?14:10
corvuslike, start the native one, wait 10 seconds, then start the next?14:10
mordredcorvus: I'm not sure that's a thing we can control14:10
corvusyeah, i was afraid of that14:10
corvus(bad idea: conditional sleep in dockerfile)14:11
*** y2kenny has joined #zuul14:11
mordredcorvus: yeah - although even that I'm not sure how to pass a different value to each since it's the same build from the docker pov14:12
avassmordred: random value14:14
avass:)14:14
mordredavass: "yay"14:14
y2kennyfor nodepool, what does "building" state do?  Is it possible to config a static node that skip "building"?  (I am trying to setup a baremetal node that basically have nothing and allow zuul to install everything from the OS and up using pxe and ipmi.)14:15
y2kennyOr do I need to have a custom driver for this type of nodes?14:16
y2kenny(custom nodepool driver)14:16
avassy2kenny, mordred: I guess you would need an ironic driver for that?14:20
corvusy2kenny: the nodepool static driver expects to be able to supply a host to zuul to put in the ansible inventory; so the first question to answer is probably how you want to use these nodes from ansible14:21
*** jamesmcarthur has quit IRC14:22
y2kennycorvus: I am hoping to use the executor to drive much of the setup for the nodes with ipmi first before adding the node to the inventory14:22
*** jhesketh has quit IRC14:22
y2kennysimilar to how k8s namespace type14:22
corvusy2kenny: makes sense.  the static driver doesn't have that functionality right now, so yeah, this would require a change to incorporate some of that behavior from the k8s driver14:24
y2kennyI mean, similar to how I use k8s/openshift namespace type.   (Nodepool provision namespace, I create pod with 'stuff' in zuul and then add to inventory for others to use.)14:24
y2kennycorvus: so to use custom driver, what do I need to do?  Do I need to build nodepool from source or is there somewhere in the nodepool image where I can "drop in" a custom driver?14:25
corvusy2kenny: no, we don't support out-of-tree drivers; but we'd welcome a change like that to the upstream static driver14:26
y2kennycorvus: ok... I am thinking of writing a cobbler driver or something like that so I was wondering how I should get started.14:29
mordredyeah. although you might find it easier to make an ironic driver14:29
*** sanjayu__ has joined #zuul14:30
mordredI'd _highly_ recommend using ironic instead of cobbler for this14:30
y2kennymordred: um... I am just worry about my mental capacity to take in more new things :).  How much of other pieces of OpenStack do I need to deploy in order to have ironic to work?14:32
y2kennylast I looked into ironic (which, admittedly more than 3 years ago) I had a hard time getting my head around bootstraping ironic.14:33
*** sanjayu_ has quit IRC14:33
y2kennyI think there was some Openstack on Openstack thing but I wasn't too clear on how to get things done.14:33
mordredy2kenny: none - ironic works standalone. there's a project called "bifrost" which is for installing a standalone ironic via ansible14:34
mordredhttps://opendev.org/openstack/bifrost14:34
y2kennymordred: ok.  I will look14:34
mordredkk. I mostly mention it because ironic uses cloud-style images to boot base os from - as opposed to the cobbler kickstart oriented approach14:35
mordredwhich is closer conceptually to how the vm stuff works and should be much quicker to power-on and get to minimal instal that you could hand to your jobs14:36
mordredthat said - there's no reason a cobbler driver wouldnt' be possible to write14:36
*** veecue1 has joined #zuul14:39
fungior that other popular one which starts with a t, i forget the name14:40
y2kennymordred: the cloud-style images is probably more efficient but I need to see how much of cobbler's function ironic can do.  Cobbler I understood because it's really just bunch of standard linux utils like bind, dhcpd, tftp, etc.  Ironic is comparitively opaque to me conceptually.14:44
fungiironic uses those standard things as well, though its focus is on maintaining a hardware inventory, performing image management, and providing a rest api for querying and (re)provisioning systems14:48
y2kennyfungi: ok I will dig into it14:50
*** jhesketh has joined #zuul14:51
fungiit started out as a backend for openstack nova, to make it possible for users to do on-demand allocation and deallocation of bare metal servers in a "cloud" environment like they would virtual resources14:52
fungibut as mordred says you can just use it by itself too14:52
fungiit's also the current hardware backend for the metal3 (metal cubed) subsystem for openshift/kubernetes too14:53
y2kennyI saw the metal3 intro back in december and it looks pretty cool.  I just need to figure out how things fit together14:54
corvusmordred: the *docker registry itself* fails at this.14:55
mordredcorvus: wow14:58
mordredcorvus: oh - I just had a weird idea ...14:59
mordredcorvus: (for how to do your earlier suggestion of staggering)14:59
mordredcorvus: what if we run the build without the push once14:59
mordredcorvus: then do an ansible loop for each of the arches running the build with --push for just that arch15:00
mordredcorvus: then run the build with push with the list of arches at the end15:00
mordredthe final push should have already pushed all of the segments so I'd expect it to just push a manifest15:00
avassmakes sense to me15:01
corvusmordred: ++ i'll try it out in my testing15:02
mordredcorvus: cool. I've got a patch for zuul-jobs ready if it works15:03
*** jcapitao is now known as jcapitao|afk15:06
*** hashar has quit IRC15:08
openstackgerritMerged zuul/zuul master: Add some debug lines to help with the loading_errors bug  https://review.opendev.org/72573215:12
*** bhavikdbavishi has joined #zuul15:30
*** jcapitao|afk is now known as jcapitao15:39
corvusmordred: that idea seems to work, and i think we should do it because even if we fix the registry to handle this race, that should mean less network traffic15:41
mordred++15:42
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Split the arch building and pushing separately  https://review.opendev.org/72590515:44
mordredcorvus: how's that look?15:44
mordredclarkb: ^^ second reivew on that would be good too15:45
corvusmordred: looks great15:46
avassmordred: lgtm15:47
corvusmordred: i didn't check that the final manifest looked like a correct multi-arch manifest15:47
corvusmordred: i only checked that the commands ran without error15:47
corvusbut i think i can do that easily by inspecting the filesystem15:48
clarkbdone15:50
mordredcorvus: cool. incidentally - it is neat that layers can be shared between different arch images15:50
corvusmordred: yep looks good15:50
*** cdearborn has quit IRC15:51
corvusmordred: incidentally, the top level manifest is this: {"application/vnd.docker.distribution.manifest.v2+json": "sha256:65ee2f0113bb121e974010143fc704270391bb5728b70bf160db10a86c1ff1fb", "application/vnd.docker.distribution.manifest.list.v2+json": "sha256:71d563ecfa8c24afdb8ae5a56ca54155a475106f1214fc4272cf1b8fa796d3c7"}15:51
corvusthe second one is the multi-arch manifest list, the first one appears to just be the amd64 (and indeed is also the first entry in the multiarch list)15:51
corvusi find it curious that's also listed there and it's not merely the list15:52
corvusbut that's the case whether i do the single push or multi push15:52
mordredhuh. that is interesting15:52
*** zxiiro has joined #zuul15:55
*** panda|pto has quit IRC16:03
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567816:06
*** panda has joined #zuul16:06
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567816:10
openstackgerritMerged zuul/zuul-jobs master: Split the arch building and pushing separately  https://review.opendev.org/72590516:14
*** jamesmcarthur has joined #zuul16:20
*** rpittau is now known as rpittau|afk16:24
openstackgerritJames E. Blair proposed zuul/zuul-registry master: Handle blob upload races  https://review.opendev.org/72592516:28
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567816:29
corvusmordred, avass, clarkb: ^ i think that should also make the registry more robust.  hopefully we don't hit the race because of mordred's change, but if we do hit it, it should no longer error16:29
mordredcorvus: watching one of the nodepool builds, it got past the previous place16:34
*** evrardjp has quit IRC16:36
*** evrardjp has joined #zuul16:36
*** sanjayu__ has quit IRC16:38
mordredcorvus: woot! job success16:40
*** stappa has joined #zuul16:40
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567816:40
avassmordred: nice :)16:40
mordredcorvus, clarkb: https://review.opendev.org/#/c/722483/ and https://review.opendev.org/#/c/725611/1 will come back green and are ready for review16:40
mordredavass: \o/16:40
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567816:50
clarkbcorvus: couple notes on the registry change. My biggest concern is swift's eventual consistency leaves us open to the race you try to protect against16:52
corvusclarkb: yeah, i thought about that, though i think that in most cases a PUT followed by a GET should actually return the thing.  but even if it does fail, that's falling back to the status quo, so probably the patch doesn't make it worse?16:53
clarkbcorvus: ya I was poking around and if we go by ancient data https://github.com/gaul/are-we-consistent-yet#observed-consistency says ~3 reads after overwrite have been observed against swift implementations in the wild to get the correct data16:55
clarkbhowever read after create is always ok16:55
clarkbI think that means we should generally have a winner (the creating writer?)16:55
*** jamesmcarthur has quit IRC16:55
corvusclarkb: yeah, though i guess if it's a tight race after the create, the readback of the uuid could be wrong, and they could both think they're the winner16:57
corvusit's not a foolproof algorithm, but it's probably better than nothing16:57
clarkband ya I agree its no worse than the current situation16:57
corvusbasically, we've reduced the race window from like 10 seconds to maybe <1 second?16:58
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567817:01
*** jcapitao has quit IRC17:04
clarkbcorvus: also are the client supplied uuids expected to be random and not determinstic for the data?17:05
clarkb(that was my other comment)17:05
mordredcorvus: hrm. I thought tailing the logs on the nodepool change had shown we had success - but I see failure :(17:05
mordredcorvus: https://zuul.opendev.org/t/zuul/build/17b1cc2f42634141b991aa8d33fa32f917:06
mordredcorvus: I've got to run for a little bit though17:06
mordredI'll look further when I Get back17:06
*** jpena is now known as jpena|off17:08
corvusclarkb: replied (uuids are unique)17:09
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567817:16
*** veecue has joined #zuul17:19
*** irclogbot_0 has quit IRC17:20
*** jamesmcarthur has joined #zuul17:21
*** veecue1 has quit IRC17:22
*** irclogbot_0 has joined #zuul17:24
*** sshnaidm is now known as sshnaidm|afk17:26
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567817:27
stappaHello. Sorry if this is a stupid question.                                                                                                                                                                                                                                                                                            There is a discuss in17:31
stappamailing lists about gzip in upload-logs role: http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-May/000416.html                                                                                                                                              There is a quote "I also agree, we'll likely want to improve documentation around web server17:31
stappaconfigure too."                                                                                                                                                                                                                                                                                            I wonder if this is the thing and there is a17:31
stappadocumentation about relevant Apache configuration. For now we have a logs server with both compressed and uncompressed logs (compression was disabled at some point). Because of incorrect Apache mimetypes configuration we have broken links to the compressed "jobs-output.*" files.17:31
stappaI am novice in Apache and looking to the right way to sort this out17:31
*** jamesmcarthur has quit IRC17:37
*** jamesmcarthur has joined #zuul17:38
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567817:38
*** bhavikdbavishi has quit IRC17:45
tristanCtobiash: after running an enqueue-ref, it seems like our scheduler gearman is now stuck... how did you use the repl to unlock your scheduler?17:45
*** veecue has quit IRC17:46
tristanCrunning `zuul-scheduler repl` doesn't seem to do anything17:47
*** veecue has joined #zuul17:49
fungistappa: it may not be an ideal example, but here's what we used to do on our logserver before we switched to serving build logs from swift: https://opendev.org/opendev/puppet-openstackci/src/branch/master/templates/logs.vhost.erb#L23-L6417:55
*** hashar has joined #zuul17:58
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567818:05
veecueHi. I would like to contribute to a Gitea driver. (Reference: https://github.com/go-gitea/gitea/issues/8851). Are there any offerings for a good code skeleton to build from? I would start without the fancy caching etc that the GitHub driver has and work my way up from there18:21
clarkbveecue: thr pagure driver was mentioned yesterday as a good framework to start from18:22
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567818:23
veecueclarkb: Thanks!18:25
tobiashtristanC: enable repl, connect via nc on port 300018:37
tobiashzuul-scheduler repl18:37
tobiashyou get the scheduler object via server.scheduler18:37
tristanCtobiash: thanks, unfortunately it seems like zuul was enable to start the repl service, we had to hard reset the service18:38
tristanCunable*18:38
tobiashlooking forward to scale out scheduler18:40
tobiashcorvus: do we have anything left for the last 3.x release we planned on that etherpad?18:41
y2kennySomeone just pushed a burst of 45 patches to my infrastructure and it seems to held up all the jobs (I have 5 executor).  What's worse is that the branch for these patches are noops from the infrastructure perspective.  So to make things better, should I, 1) simply increase the number of executor?  2) add additional merger? 3)  Filter out branches18:43
y2kennyfor that project (I am not sure if this is actually possible.)18:43
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567818:44
fungiveecue: tumble also mentioned an interest in working on a gitea source connection driver for zuul (or at least in using one if someone writes it), so may be useful to coordinate with them too18:45
clarkby2kenny: I expect your bottleneck is merging there because zuul needs to do merges to determine what jobs to run. Noops are handled directly in the scheduler iirc and never talk to an executor18:47
fungiy2kenny: can you elaborate on how it "held up" your jobs? was it effectively utilizing your available job nodes? if not, do you have resource monitoring on your executors so that you can see if system load, disk space or memory utilization was topping out? or was the scheduler waiting on all the merge requests to complete?18:47
fungioh, and yeah, you said mostly noop, so i agree with clarkb18:48
fungiyou could add some standalone mergers18:48
tumblefungi, that's true. And hi veecue!18:49
fungiy2kenny: if noop jobs are what you really meant by "noops from the infrastructure perspective"18:49
veecuefungi: Yep, he is how I even got to that IRC ;). Hi tumble!18:50
tumblethe propaganda worked18:50
fungiheh18:50
y2kennyfungi: it's held up in the sense that other queued items are stuck waiting.  So I have one project called 'linux' and the pipeline queue counter was like 45 and then I have another one queued from the project zuul-config and it was stuck in the queue until that 45 patches cleared.18:50
y2kennyfungi: yes, no op from the infrastructure perspective.  My job is configured for branch 'A' and those 45 patches are from branch 'B' that the infrastructure doesn't handle18:51
tumbleveecue, feel free to start. I have nothing done yet and wouldn't start before Friday anyway. My biggest problem is that I'm new to zuul and struggle with the basics yet, so that would significantly slow me down anyway.18:51
corvustobiash: i was hoping to test and restart opendev with the zk auth patch, but it's been several weeks and i don't really know if we're in a place to work on that yet18:52
y2kennyfungi: the infra is supposed to ignores them but I believe even those changes are tried by the merger from what I can tell.18:52
avassy2kenny: yeah, all changes needs to be merged for the scheduler to load the job configuration18:53
tobiashcorvus: hrm, ok, I think I'll try that in our environment then18:54
fungiy2kenny: how did you configure zuul to ignore those branches?18:54
veecuetumble: I'm starting right now, but I'm also new to Zuul18:54
y2kennyfungi: only by specifying specific branches for the jobs.  Did I miss an alternate method?18:55
tobiashhopefully I can contribute some useful insights to running with the zk auth patch :)18:55
y2kennyfungi: I was looking into the tenant config but I didn't see anything that applies... but I may have missed something.18:55
clarkbcorvus: will the restart without jemalloc friday pull that in?18:55
clarkbcorvus: or is that still unmerged?18:55
tumbleveecue, alright, I'll be around here and interested in your progress if you get anything working :)18:56
tobiashI thought is was merged already for quite some time and 'just' has to be configured18:56
corvusclarkb: changes to actually switch zk to tls are lined up behind 'run everything in containers'18:56
fungiy2kenny: no just curious if you had zuul configured to run noop jobs for changes targeting those branches, based on your earlier phrasing18:56
tobiashmakes sense to do that after containers18:57
y2kennyfungi: oh no, they shouldn't even run noop job.  I basically configured to have job.branches: 'A' (that's what I meant by ignoring the rest.)18:57
clarkbcorvus: gotcha and that last remaining piece for that is nodepool?18:57
corvusveecue: hi!  feel free to ping me for help; like tumble, i'll have more time to dive in myself after friday18:57
corvusclarkb: yeah, then dust off https://review.opendev.org/72030218:57
y2kennyavass: that's still true even when the projects are listed under untrusted-projects and has an empty include right?18:58
mordredcorvus: nevermind! the nodepool patch is green - I think I maybe clicked re3check too quickly18:58
tobiashcorvus: did I understand that patch correctly that I can do a step by step transition by adding the tls port to zk first, reconfigure zuul and nodepool and then disabling the unencrypted port?18:58
mordredcorvus: https://review.opendev.org/#/c/72248318:58
avassy2kenny: ooh, I don't know about that18:59
avassy2kenny: you mean zuul is tracking them but you don't load any items in those projects?18:59
AJaegercorvus, tobiash, do you want to merge tobiash's change for git tuning in again? https://review.opendev.org/72380018:59
y2kennyavass: that's correct18:59
fungiy2kenny: you ought to be able to look at the scheduler's logs to determine what actions it took for one of those changes18:59
y2kennyfungi: oh... let me see...19:00
tobiashAJaeger: we should change the pruneExpite from now to something slightly higher than now probably19:00
fungiy2kenny: that could help narrow down what it was doing with them which took so much time19:00
corvusAJaeger: has anything changed to make that less dangerous?19:00
AJaegertobiash: will you update the change?19:00
AJaegercorvus: my understanding from the discussions was that the change was not the culprit19:01
*** y2kenny has quit IRC19:01
AJaegercorvus: but your call19:01
corvusAJaeger: that's not what i got out of it19:01
tobiashAJaeger: sure, I can update it if we come to a conclusion19:01
*** y2kenny has joined #zuul19:02
y2kennyfungi: when you said scheduler log, you meant scheduler and not executors right?19:02
AJaegercorvus: not? Ok. let me check scrollback...19:02
corvusAJaeger, tobiash: i started looking at it, but could not come up with a reproduction; it's not high on my list, so if someone else has time to look at it that would be great.19:02
fungiAJaeger: last i saw, some snapshots were taken of some of the git repositories in question, but as of yet attempts to manually reproduce the problem were inconclusive, right?19:02
corvusi put some git repos in afs and linked them here earlier19:03
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567819:03
AJaegerseems I misunderstood the discussion19:03
avassy2kenny: yes19:03
fungiy2kenny: yes, scheduler. if zuul wasn't actually configured to run any jobs for those branches then in theory the executors shouldn't have been touched (but if the scheduler did ask executors to do something, it should log that in the scheduler logs)19:03
corvusAJaeger, tobiash: i think the short version is: before we merge that, we want someone to say "i understand the problem and think either this was unrelated or it has been fixed".  :)19:04
corvusAJaeger, tobiash: i am not saying that at this moment :)19:04
avassfungi, y2kenny: except if the executor merges the change19:04
AJaegercorvus: I see19:05
fungiavass: right, that's what i'm curious to find out. i suppose the change could in theory add a zuul configuration and then the scheduler needs the merger to feed that information back to find out what builds would be performed, but if the scheduler is configured not to consume configuration from that repository then it shouldn't need that information19:06
tobiashcorvus: was https://static.opendev.org/user/corvus/oo.tgz the correct link with the broken repo?19:07
y2kennyfungi: so there's a lot of log and I am not sure which items are significant so I am going to start at the beginning of the burst and highlight the log as I go19:07
avassfungi: yeah, if no items are included, that project should probably be treated as if it were not tracked. Except for being able to use required-project to test with that project I guess.19:07
corvustobiash: yep19:08
y2kennyfungi: so at the start of the burst, I see a bunch of INFO zuul.GerritConnection...  Updating <Change 0x7fdd05bbcca0 None 356552,1>19:09
y2kennybasically one per change of those 45 patch19:09
fungiy2kenny: if you search for xxxx,y where xxxx is the change number and y is the patch revision number then you should find the trigger event [e: zzzzzzzzzzz] where zzzzzzzzzzz is some long hex number19:09
fungithat zzzzzzzzzzz will be included in all log entries related to the event19:09
y2kennyAh ok yes19:09
y2kennyI was wondering what that e is19:10
fungiwhich makes filtering a very busy log much easier19:10
avassy2kenny, fungi: it's the buidset uuid isn't it?19:10
avassor is that different19:10
tobiashcorvus: in that repo FETCH_HEAD seems to be valid19:11
y2kennyfungi: um... tracking that zzzzz don't seems to be enough because seems like there are other events triggered by the same patchset19:12
AJaegercorvus: reread the summary from http://eavesdrop.openstack.org/irclogs/%23opendev/%23opendev.2020-04-25.log.html#t2020-04-25T23:22:27 - somehow I had later conclusion in mind. I understand your concerns.19:12
y2kennyfungi: I am seeing a lot of Adding change and Reporting enqueue19:12
avassy2kenny: I would guess that means the scheduler is queueing up a merge job :)19:12
y2kennyavass: looks that way.  Each pipeline I have logged "adding change"19:13
tobiashcorvus: I could reproduce it :)19:14
avassfungi: oh yes, you could still have a config project still targetting a project that is not including any items19:14
fungiavass: the [e: zzzzz is] the triggering event id, the buildset_uuid is different19:17
mordredcorvus: I believe we're far enough along with the container rollout that working on the zk tls rollout is reasonable. we've landed and have containerized (or ansiblized) all the pieces of the pie - we still need to remove the remaining puppet builders, but that's just iterating through them and I think we can get that done before we actually land the zk thing - the ground sholdn't be moving under the zk patch19:17
y2kennyfungi: is the event certain type of event or any kind of event?19:18
tobiashcorvus, AJaeger: those steps confirm that FETCH_HEAD is ignored as a ref when pruning: https://etherpad.opendev.org/p/lrJlt1vJ93Pt7bXmVAfo19:18
y2kennyfungi: or may be any event that the pipeline is configured?19:19
y2kennyfungi: oh... I think I might now what's going on.  So I have 45 patch... but my pipelines are configured to trigger on events like comment-added.  And there are other infrastructure that was commenting on the same change19:20
y2kennyfungi: so each event has to be handled by the merger right?19:21
fungiy2kenny: yes, the event id is a generic id applied to any event which is logged, so you can see all activities specific to a particular instance of an event19:21
fungievery event gets a new event id, regardless of its event type19:22
veecuetumble: Both of us were so optimistic about Gitea. It doesn't even support PR reviews :D19:22
fungiso two different patch uploaded or comment added events will get distinct ids19:22
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567819:22
y2kennyfungi: and each event would trigger an add to the pipeline and the pipeline is only emptied by merger?19:22
y2kennyfungi: by add to the pipeline I meant add to the ChangeQueue19:24
*** jamesmcarthur has quit IRC19:25
tumbleveecue, uhm, not sure what you mean by PR review, but I see a green "Review" button in PRs :o19:26
mordredveecue, tumble19:26
mordredveecue, tumble: also - the gitea humans are friendly, and we've landed several patches upstream as we've hit various things - so if the api is deficient, I'm sure it could be fixed :)19:27
corvustobiash: yeah, i wasn't able to make that happen without an explicit gc, but maybe it's enough to assume that it can happen, and for our testing just do explic gc's19:27
tobiashcorvus: yes, I think we can assume that, however it looks to be harder to do a gc that doesn't break fetch_head :/19:28
fungiy2kenny: the scheduler maintains an events queue, which all events it receives go into. as it pulls each event off the queue it checks to see whether it has any triggers configured matching that event, and if so it enqueues it into the relevant pipelines and asks for a merger to fetch the configuration for that change so that it knows what builds are needed (if any)19:30
*** jamesmcarthur has joined #zuul19:30
y2kennyfungi: ok.  And the pipelines are shared by all projects and first come first serve?19:31
fungiy2kenny: what i'm not clear on is whether that last step i mention happens when the project is configured to have nothing included19:31
y2kennyfungi: ok let me look for merger in the log19:31
*** yolanda has quit IRC19:33
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567819:34
y2kennyfungi: so after a mass of adding change to queue, I see some log from merger.  I see some merger:merge unique: 1dc1e6a2583b44849d5508dd2da11586> complete, merged: True, updated: False19:35
y2kennyI also see some "<change> did not merge because it did not have any jobs configured"19:36
y2kennyand some "Resetting builds for change because the item ahead failed to merge"19:37
y2kennyand also Dequeuing change because it can no longer merge19:37
fungiy2kenny: so yes, it looks like it is at least did ask mergers for configuration from each change19:44
fungido you have any standalone mergers, or just the ones embedded in the executors?19:44
y2kennyjust embedded.  I guess I should add some mergers19:44
fungiyeah, we strongly recommend extra mergers so that such activity doesn't monopolize the ones the executors rely on. though it sounds like there might also be some opportunity here for improving performance if we can work out situations where the scheduler can know it doesn't need to request a merge of certain changes19:45
jamesmcarthurclarkb: fungi: corvus: mordred: If y'all get a chance, could you check out the email entitled "Zuul Update for OSF Press Conference"19:46
mordredjamesmcarthur: ohai - what's the timeframe on that?19:47
y2kennyfungi: about the changequeue/pipeline, are they shared by all projects that uses that pipeline?  Does the merger take from that pipeline one after the other?  Is it possible to have per project queue within each pipeline or does that mess things up?19:48
jamesmcarthurmordred: :) hi! May 11 is the date of the press conference19:48
jamesmcarthurSo ideally sometime before EOW19:49
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567819:50
mordredjamesmcarthur: cool - I keep thinking about it - and then I keep forgetting19:50
jamesmcarthurmordred: that's pretty much just life at the moment, so I understand19:52
fungiy2kenny: as zuul pulls events off its event queue, if it decides it needs to act on one it puts a merger:merge request into gearman and then the next available merger grabs that and processes it, returning the result. until that happens, zuul can't be sure what pipelines to enqueue into because a change could be introducing new criteria for a project-pipeline19:53
y2kennyfungi: ok19:53
fungiy2kenny: the pipelines themselves can be prioritized so that the resources consumed by builds running for them get filled in priority order, but that happens after zuul knows what pipelines will be involved19:54
tobiashcorvus, AJaeger: I found a mailing thread about this behavior on the git mailing list: https://public-inbox.org/git/20160708025948.GA3226@x/19:57
tobiashbut no real solution there19:57
fungiyeesh, almost 4 years ago19:59
corvustobiash: will setting the delay to >0 work for us?19:59
tobiashcorvus: nope, that removed that object as well20:00
corvusoh drat; well, we could go back to making zuul refs, but that's a mess20:00
tobiashcorvus: I need to see if we can fetch differently so that there is a real ref20:00
corvustobiash: i guess we could have a sinfle refs/zuul/fetch ref and just keep reusing that20:01
tobiashI think that would be possible20:01
corvusbasically just needs to stay around long enough to merge it into a real ref20:01
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567820:02
*** tumble has quit IRC20:04
y2kennyAnother observation  I am getting a build that report both success and failure at the same time...20:05
*** tumble has joined #zuul20:05
y2kennyfrom Gerrit, it Verified +1 but immediately after it, it removed the verified +1  (the pipeline is set to remove verified if fail)20:06
y2kennylooking at the scheduler log, I see "Build complete, result FAILURE"20:07
y2kenny... I am so confused...20:08
fungiy2kenny: are you triggering two different pipelines on the same event with similar reporting settings?20:08
avassy2kenny: are multiple pipelines being triggered?20:08
y2kennyfungi, avass: let me check...  I didn't think I configured multiple but may be I did that unintentionally20:10
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567820:10
stappafungi: This is useful, thanks!20:12
y2kennyfungi, avass: ok I guess this is why... "Reported change" did not merge because it did not have any jobs configured" this is reporting from a different pipeline20:14
y2kennyI guess I have a pipeline that has too much of a wild card in it20:15
fungiy2kenny: that would do it20:15
fungiy2kenny: er, actually "did not merge because it did not have any jobs configured" doesn't seem to result in a verified vote on our system20:18
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567820:18
fungiy2kenny: so that could be benign20:18
fungiy2kenny: look for log entries which say "Reporting item" and look at what tenant/pipeline is associated with them (it'll be in the facility name at the beginning of the log entry, like zuul.Pipeline.<tenant>.<pipeline>)20:21
y2kennyfungi: I had a project configured to match any project but has no job associated with the pipeline.  Looks like that caused the problem20:22
y2kennyfungi, avass: thanks for the tip.20:22
avassy2kenny: np20:23
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Revert "Revert "Tune automatic garbage collection of git repos""  https://review.opendev.org/72380020:23
y2kennyand just another observation... if the zuul user that is responsible to submit a change on gerrit does not have permission to submit, it will keep retrying without fail.  May be it will time out eventually but I didn't wait for that after it commented on a change like 10 times trying to merge :)20:24
y2kennyzuul stopped  trying after I manually submitted the change20:24
clarkby2kenny: what HTTP return code does gerrit return in that case?20:27
clarkby2kenny: I did just add handling for HTTP 409 which happens if you try to vote on a closed change20:27
clarkband ya it should retry 3 times I think20:27
clarkb(but not retrying when we have no hope of success is a good thing)20:27
y2kennyclarkb: the voting is done by the executor or the scheduler?20:27
clarkby2kenny: the scheduler20:27
y2kenny(just so I know where to check the log)20:28
y2kennyok... let me dig into the log...20:28
clarkby2kenny: if you can share a traceback for those errors it would be great. I don't mind writing another fix similar to the http 409 case20:28
tobiashy2kenny: it can be that the comment triggers another enqueue into the gate which will try to merge again and then comment again...20:30
tobiashy2kenny: we call this behavior a gate loop20:30
y2kennytobiash: oh it has a name.... :D20:30
y2kennyyea, I think that's what that was20:30
tobiashwell that's how me and my team calls it ;)20:30
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567820:32
y2kennyclarkb: sorry...  I forgot my setup is not using the http... I am using ssh20:33
y2kennywe have some weird policy that makes me not able to use http interaction with gerrit20:34
clarkbgotcha I don't know if we retry failed requests over ssh so probably is what tobiash describes20:34
y2kennyfor "reason" we disallow git clone over http20:34
y2kennyand I believe, if I configure zuul to interact with gerrit via http, it will try to clone via http as well... and that causes failure20:35
tobiashy2kenny: interesting, for 'reason' our gerrit has (officially) disabled ssh20:35
avasstobiash: we've had that as well :)20:35
y2kennyso I am forced to use ssh only (while missing the oh so nice inline comment feature... :'(  )20:36
y2kennytobiash: I would prefer to be in your shoes20:37
y2kennytobiash: although, what are you guys using to replace stream-events?20:37
tobiashy2kenny: well, we had to get an exception for our gerrit back then because zuul was ssh only for gerrit for a long time20:37
tobiashso actually our zuul uses ssh, but that's not available to most users20:38
fungiit sounds like gerrit wants to use their checks api to replace the need to watch event streams for code review events20:39
clarkbfungi: there was discussion on that and I think lastI saw they will keep the event stream20:39
fungiahh20:39
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567820:43
y2kennyI thought they added some webhook thing to replace stream event but I am not sure how it work exactly20:43
y2kennythe nice thing about stream event is that the connection is opened from the remote side20:43
fungiy2kenny: yeah, the checks api is supposed to incorporate some sort of web trigger, but sounds like they've decided the ssh event stream also still has uses20:44
y2kennyso any one can subscribe to the boardcast as they see fit20:44
clarkby2kenny: its still zuul -> gerrit connection. Basically the CI system registers thing sthey care about then polls for events on that20:44
clarkbthere are currently a few limitations with it that means the ssh event stream still does things it can't (like non change events)20:44
fungibut is lightweight enough i guess that rapid polling isn't a problem20:45
y2kennyclarkb: I see.  If only I can get my gerrit team to upgrade gerrit....20:45
fungiand has an up side that events are no longer missed if the consumer stops watching the event stream for a few minutes20:45
avassanyone wanna take a look at: https://review.opendev.org/#/c/724967/ before I have to rebase that again? :)20:48
*** hashar has quit IRC20:49
*** brendangalloway has quit IRC20:50
*** jamesmcarthur has quit IRC20:50
*** jamesmcarthur has joined #zuul20:51
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add upload-artifactory role  https://review.opendev.org/72567820:53
*** Goneri has quit IRC21:05
*** stappa has quit IRC21:09
*** jamesmcarthur has quit IRC21:10
*** jamesmcarthur has joined #zuul21:16
mordredcorvus: look - it's a new issue -- https://zuul.opendev.org/t/zuul/build/622f858a89174725bb121fd098c849de21:40
mordredcorvus: I think I know what it is21:41
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Tag the images pulled back into docker for changes  https://review.opendev.org/72600721:47
mordredcorvus: ^^21:47
corvusmordred: agree with solution but typo ^21:50
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Tag the images pulled back into docker for changes  https://review.opendev.org/72600721:54
mordredcorvus: good point21:54
*** jamesmcarthur has quit IRC21:55
mordredclarkb, fungi, tristanC: anybody want to +A that ^^ so I can re-check the nodepool images again?21:57
tristanCmordred: done22:01
mordredtristanC: thank you!22:01
*** threestrands has joined #zuul22:20
openstackgerritMerged zuul/zuul-jobs master: Tag the images pulled back into docker for changes  https://review.opendev.org/72600722:25
*** tosky has quit IRC22:56
*** y2kenny has quit IRC23:02
openstackgerritMerged zuul/nodepool master: Build multi-arch images for x86 and arm  https://review.opendev.org/72248323:07
*** tumble has quit IRC23:08
openstackgerritMerged zuul/nodepool master: Build nodepool with python3.8  https://review.opendev.org/72561123:09
mordredcorvus, ianw, tristanC: ^^ BOOM!23:09
ianwvery cool!23:16
*** Shrews has joined #zuul23:22
tristanCwell done!23:24

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!