Friday, 2020-05-01

*** Goneri has quit IRC00:06
mordredtristanC: but - there is a username/password yes? if so - I can't figure out how to configure buildkitd.toml to use it to talk to the registry mirror (or anything for that matter - I can't figure out how to do a "login" with buildkitd00:08
tristanCmordred: it should yes, at least according to https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/run-buildset-registry/tasks/main.yaml#L61-L6800:11
openstackgerritMonty Taylor proposed zuul/zuul master: Install skopeo in container images  https://review.opendev.org/72434400:12
mordredianw: ^^00:12
mordredtristanC: awesome. well - I'll have to figure out how auth works tomorrow then :(00:12
tristanCthough i have to say this whole container process in zuul-jobs is quite under documented and i find it difficult to grasp00:12
corvustristanC: which part is under-documented exactly?00:13
corvustristanC: because i think they are among the most documented parts of zuul jobs00:13
tristanCcorvus: for example the answer to the question mordred was asking :)00:14
corvustristanC: there's an abstract overview of the system here: https://zuul-ci.org/docs/zuul-jobs/docker-image.html00:14
corvustristanC: and specific documentation of all the inputs and outputs of all the roles and jobs here: https://zuul-ci.org/docs/zuul-jobs/container-roles.html00:14
*** rlandy has quit IRC00:14
corvustristanC: i really don't know what else we could do.  maybe it's too much documentation?00:15
tristanCcorvus: yes there is a lots of documentation, but that is also a complicated process00:15
mordredit is - it's a complex use case it's solving00:15
corvusyeah00:15
mordredit is literally solved nowhere else on the planet00:15
corvusand we've never used buildx yet00:16
mordredso there are some, you know, complex concepts :)00:16
mordredhttps://zuul-ci.org/docs/zuul-jobs/container-roles.html#rolevar-run-buildset-registry.buildset_registry.username is the answer to my earlier question - I as totally being lazy asking here00:16
corvusmordred: whew.  thanks :)00:16
mordredcorvus: but - what I was saying to tristanC - I have no idea how to tell buildkitd how to use that00:16
mordredif you want to see something that's underdocumented - see the docs for buildkitd.toml00:17
mordredTHAT is under documented00:17
tristanCand it's built on top of container technology that also need to be understood00:17
mordredhttps://github.com/moby/buildkit/blob/master/docs/buildkitd.toml.md is it00:17
mordred*headdesk*00:18
tristanCcorvus: unfortunately i don't know either what else we could do. Perhaps we could breakdown the documentation into the 4 tutorial/how-to/discussion/reference categories?00:18
corvustristanC: why?00:19
corvustristanC: what problem are we solving?00:19
corvustristanC: that mordred didn't read the documentation that was there?00:19
corvustristanC: that didn't happen because they weren't organized right00:19
corvustristanC: that just happened because mordred didn't feel like reading the docs00:20
corvusthat happens00:20
corvuswe don't need to re-org the docs everytime a developer doesn't read them00:20
mordredwell - I think _adding_ a blog-style howto wouldn't be bad - but I think we're stil learning things about usage patterns now that we have the tool. that wouldn't help *me* in this case at all, because what I'm having an issue with is internals00:20
mordredand thankfully - those internals are mostly hidden most of the time00:20
corvusmordred: howto what?00:20
mordredin fact, thte fact that they're so hidden is great! but it means I have to page things in when I want to work on internals00:21
corvusmordred: yeah, it's not easy.  docker is never going to make it easy.00:21
mordredcorvus: how to set up some of the more complicated job relationships that we've gone through a couple of iterations to get right over in system-config. I feel like at some point a blog-post retrospective on that would be nice00:21
mordredbecause I feel like we learned some lessons on useful patterns while doing it00:22
tristanCcorvus: it seems like this problem is kind of solved for opendev, but it seems quite difficult to replicate.00:22
corvusmordred: yeah.  i don't think we've even completely figured them out yet.00:22
mordredcorvus: exactly00:22
corvustristanC: ah, i see what you're getting at.  let me make a suggestion:00:22
mordredthat's wy I don't think it's time to write that yet00:22
corvustristanC: these jobs are not directly consumable from zuul-jobs; they need an implementation to be provided by the zuul administrator.  so we can't make it super-easy for end users, but we can do this:00:23
corvustristanC: this documentation tells a zuul site admin how to set the system up: https://zuul-ci.org/docs/zuul-jobs/docker-image.html00:23
corvustristanC: and then they can document how to use that system for their end users.  opendev does that here: https://docs.opendev.org/opendev/base-jobs/latest/docker-image.html00:24
corvustristanC: anyone of course is welcome to copy and adapt that last bit of documentation for their own use00:24
corvustristanC: and yeah, once we have a better handle on how we should recommend people actually use these, we can probably consider that the reference documentation and add a blogpost/howto/tutorial that's more like "add this job.  type "requires:foo" here.  etc."00:25
mordredyeah00:27
mordredwe're still actively learning lessons and getting stuff wrong00:27
corvus(but note that opendev documentation is pretty close to that -- it does say what jobs to put in what kinds of repositories)00:27
mordredcorvus: ianw taught me something re: https://review.opendev.org/#/c/724344/ - and it is now more simple00:31
mordredcorvus: that thing only works in latest ubuntu and latest debian - but we're using those here, so it's ok00:31
tristanCcorvus: i didn't knew opendev base-jobs had such a docker-image documentation, it's quite handy. Shouldn't it be referenced from zuul-jobs or zuul-registry?00:40
*** guillaumec has quit IRC01:07
*** swest has quit IRC01:57
*** swest has joined #zuul02:12
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] xenial pip install  https://review.opendev.org/72478802:24
*** bhavikdbavishi has joined #zuul02:51
*** bhavikdbavishi1 has joined #zuul03:32
*** bhavikdbavishi has quit IRC03:34
*** bhavikdbavishi1 is now known as bhavikdbavishi03:34
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] xenial pip install  https://review.opendev.org/72478803:37
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] xenial pip install  https://review.opendev.org/72478803:44
*** evrardjp has quit IRC04:35
*** evrardjp has joined #zuul04:36
*** bhavikdbavishi has quit IRC04:51
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] xenial pip install  https://review.opendev.org/72478805:18
*** zxiiro has quit IRC05:23
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] xenial pip install  https://review.opendev.org/72478805:24
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] xenial pip install  https://review.opendev.org/72478805:30
openstackgerritIan Wienand proposed zuul/zuul-jobs master: [wip] xenial pip install  https://review.opendev.org/72478805:36
*** sgw has quit IRC06:00
*** bhavikdbavishi has joined #zuul06:03
*** bhavikdbavishi has quit IRC06:46
masterpeGood morning, I see that there is a gitlab driver for zuul: https://opendev.org/zuul/zuul/src/branch/master/zuul/driver/gitlab but is there also a manual how to configure it?07:05
*** yolanda has quit IRC07:38
*** bhavikdbavishi has joined #zuul07:47
*** yolanda has joined #zuul07:51
*** bhavikdbavishi has quit IRC08:02
*** bhavikdbavishi has joined #zuul08:02
*** bhavikdbavishi1 has joined #zuul08:37
*** bhavikdbavishi has quit IRC08:39
*** bhavikdbavishi1 is now known as bhavikdbavishi08:39
AJaegeravass: could you check for your changes to go from role install- to ensure-* whether those need backporting, please? I backported the magnum one now09:17
avassAJaeger: to release branches? sure09:23
AJaegeravass: yes, to stable ones like the magnum ones I did09:25
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Control log archive and user preservation with vars  https://review.opendev.org/70138109:25
avassAJager: I'll see what I can do, got the day off today so I have all the time in the world :)09:26
AJaegeravass: I think the airship ones might need backporting as well, openstack and opendev looks ok09:26
AJaegeravass: enjoy ;)09:26
AJaegerand no urgency, just a reminder :)09:26
avassI also saw that we're using 'with_items' instead of 'loop' on some tasks, checking if it's possible to use loop_control on those and if not, maybe we should avoid 'with_' type loops entirely?09:27
AJaegersorry, can't help with that one...09:28
avass:)09:28
AJaegermnaser: ok to +2A now https://review.opendev.org/724132 ?09:29
*** tosky has joined #zuul09:30
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Do not keep owner when pulling zuul-output  https://review.opendev.org/70138109:39
*** yolanda has quit IRC09:43
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Check for loop_control in with_ type loops  https://review.opendev.org/72481009:48
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-repositories: Add role  https://review.opendev.org/71750709:49
zbrafaik, there is are no plans from ansible team to deprecate with_ --- they wanted it at some point until they realised loop implementation made very common use practices much harder09:50
zbravass: am curious what are the reasons behind dropping the use of item/with_items?09:51
avasszbr: yeah, looks like you can use loop_control on with_ type loops so it's fine09:51
avasszbr: https://zuul-ci.org/docs/zuul-jobs/policy.html#ansible-loops-in-roles09:52
zbryes you can, loop can do anything with_* do, but at the cost of making much harder to read the code09:52
avasszbr: So that ^ should also be applied to with_ type loops, not just 'loop'09:52
avassAJaeger: can you update the with_items to use loop control? :)09:53
zbrafaik, use of loops with includes and blocks was never supported anyway09:53
avasszbr: you can't loop over blocks but you can loop over includes, so in what way is it not supported?09:54
avassnot sure what you mean09:55
zbrwhat if you have a block inside the role....09:55
zbravass: i am not saying this change is a mistake, just trying to gather facts, if true it means that in general roles should use unique vars in their loops?09:56
zbri bet 99% ore roles over written do not follow this practice09:57
avasszbr: I guess you usually don't need unique loop vars, but the roles in zuul-jobs are supposed to be easily imported to other projects09:57
zbrif that is really needed, it sounds like a cool new feature to add to ansible-lint09:57
avasszbr: but I guess collections would need unique loop vars as well09:58
avasszbr: so yeah, maybe all roles should avoid using the default loop_var, but if  we're thinking on that scope maybe there just shouldn't be a default loop var?09:59
avasswould be hard to deprecate that though09:59
zbrclose to impossible10:00
zbrin fact I did like the implicit loop var, make code easier to read, less boilerplate10:00
reiterativeavass Thanks, I thought that was the case. Just wasn't sure about the significance of the Workflow label..10:03
avasszbr: yeah I like it too, but as soon as you want to loop over the role it can cause problems10:06
avassreiterative: no problem!10:06
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-repositories: Add role  https://review.opendev.org/71750710:12
avassAJaeger: thank you!10:13
AJaegeravass: further updates needed...10:15
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-repositories: Add role  https://review.opendev.org/71750710:18
AJaegeravass: is that one ok now? ^10:18
AJaegerquick first ok would be fine - then I'll rebase the rest on top of it...10:19
AJaegerI meant "quick review"10:21
* AJaeger rebases now everyting on master...10:22
avassAJaeger: I'll take a look10:28
openstackgerritSorin Sbarnea (zbr) proposed zuul/zuul master: Add convenience Makefile  https://review.opendev.org/72383710:28
AJaegeravass: please give me ten minutes to finish rebasing10:28
*** bhavikdbavishi has quit IRC10:29
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-repositories: Add role  https://review.opendev.org/71750710:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-repositories  https://review.opendev.org/71750810:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-repositories  https://review.opendev.org/71750910:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737510:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-repositories  https://review.opendev.org/71751010:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure-repositories  https://review.opendev.org/71751110:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-repositories  https://review.opendev.org/71751210:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-repositories  https://review.opendev.org/71751310:31
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781710:33
avasszbr: there's no difference between with_item vs loop right?10:33
zbrwhat do you mean by difference?10:34
AJaegerso, everything rebased and updated - let's see whether it still works ;)10:34
zbrloops are newer, so they may have problems with really old ansible versions10:34
avasszbr: looks like they're used the same way at least :)10:34
avassso I'm doing a simple with_items -> loop in a lot of places10:34
avassAJaeger: I'll review once I see a +1 verified then :)10:35
AJaegeravass: no urgency - this was lingering several weeks ;)10:37
AJaegerI'll take a longer break now..10:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-repositories: Add role  https://review.opendev.org/71750710:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-repositories  https://review.opendev.org/71750810:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-repositories  https://review.opendev.org/71750910:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737510:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-repositories  https://review.opendev.org/71751010:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure-repositories  https://review.opendev.org/71751110:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-repositories  https://review.opendev.org/71751210:38
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-repositories  https://review.opendev.org/71751310:38
AJaegerargh, forgot to push latest revision - now good...10:39
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781710:39
zbrinteresting, cannot build zuul docs on mac, `zuul-manage-ansible -h` produces a segmentation fault10:40
zbri wonder if it would not be useful to add a BSD distro nodepool image to use for some tests10:42
zbroh fb-re2 joys, compiles and installs but re2.compile() chokes.10:59
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-repositories: Add role  https://review.opendev.org/71750711:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-repositories  https://review.opendev.org/71750811:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-repositories  https://review.opendev.org/71750911:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737511:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-repositories  https://review.opendev.org/71751011:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure-repositories  https://review.opendev.org/71751111:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-repositories  https://review.opendev.org/71751211:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-repositories  https://review.opendev.org/71751311:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781711:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781711:09
AJaegermnaser: please review my changes ^11:14
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Check for loop_control in with_ type loops  https://review.opendev.org/72481011:17
masterpeI'm trying to configure zuul, I see in executor.log the following message11:18
avassbig change, hope I don't break something this time11:18
masterpefatal: could not read Username for 'https://xxxxxxx': No such device or address'11:18
masterpeat first I had in /etc/zuul/zuul.conf in section [merger] the wrong git_user_name, I correct that, But I still see the message11:19
avassmasterpe: can you send a snippet of the logs in a paste like: http://paste.openstack.org/ ?11:20
avasseasier to see what could be wrong if I know the context :)11:20
avassmasterpe: oh is this a github issue?11:22
masterpehttp://paste.openstack.org/show/792982/11:24
masterpeI use gitlab as driver11:24
avasshmm, I don't know how well the gitlab driver is supported yet and I haven't used it11:27
*** bhavikdbavishi has joined #zuul11:31
avassmasterpe: what does your zuul.conf look like?11:32
masterpeI have the username in the merger section and gitlab11:33
masterpeI'm currently away will look into it an hour, when I'm back11:34
avassmasterpe: looking at the source I guess you set either cloneurl, baseurl or server in the gitlab connection with username and password?11:36
mgoddardHi, I'm trying to use Ansible's reboot module in a Zuul but it's giving me an ERROR. Anyone tried it before?11:38
mgoddardhttps://a1110360d0aa5b1915ef-de0170061a4c33caf35d62b404ee94ad.ssl.cf5.rackcdn.com/724819/2/check/kayobe-overcloud-host-configure-centos8/d17c0af/job-output.txt11:38
mgoddardhttps://review.opendev.org/72481911:38
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Check for loop_control in with_ type loops  https://review.opendev.org/72481011:39
avassmgoddard: if you check the json logs it gives you more info11:40
*** lseki has quit IRC11:40
avassmgoddard: http://paste.openstack.org/show/792984/11:41
avassmgoddard: first guess is that you need to use 'become:' and execute it as root11:42
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Check for loop_control in with_ type loops  https://review.opendev.org/72481011:45
*** Goneri has joined #zuul12:00
mgoddardthanks avass12:05
avassmgoddard: no problem :)12:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-repositories: Add role  https://review.opendev.org/71750712:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-repositories  https://review.opendev.org/71750812:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-repositories  https://review.opendev.org/71750912:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737512:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-repositories  https://review.opendev.org/71751012:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure-repositories  https://review.opendev.org/71751112:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-repositories  https://review.opendev.org/71751212:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-repositories  https://review.opendev.org/71751312:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781712:09
*** saneax has joined #zuul12:12
fungimasterpe: fbo|off has been working on the gitlab driver. the main reason it's undocumented still is that it's experimental and missing critical feature parity with other source connection drivers (you can't use it for project gating yet, as i understand), but he did have a working poc of it doing advisory testing on a gitlab deployment (or maybe it was gitlab.com) since late last year12:21
masterpe@av12:21
masterpeavass: http://paste.openstack.org/show/792985/ is the zuul config12:21
avassmasterpe: ah yeah, looking at the source it seems the username/password needs to be in the server/baseurl/cloneurl12:22
fungiaha, he had it working with gitlab.com apparently... https://gitlab.com/fabien.dot.boucher/demo-zuul/merge_requests/7#note_24478249312:24
avassfungi: nice! I think gitlab is something we're going to have in the future :)12:24
*** rlandy has joined #zuul12:24
avassfungi: or, I mean we have it, be we probably want to be able to gate those projects with zuul12:24
fungifor reference, these are the changes which implemented what's there so far: https://review.opendev.org/#/q/project:zuul/zuul+topic:gitlab12:27
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475712:34
masterpeavass: using username:password in the server config works, but it is not secure, there is also visible in the dashboard12:36
avassmasterpe: you can use %()s to interpolate from environment variables in zuul.conf12:37
avasslet me link something12:37
avassmasterpe: Oh, or yo mean the web dashboard?12:37
masterpeyes12:37
avassmasterpe: I think that shows the canonical_url, what happens if you set that value?12:38
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475712:38
fungibut yeah, for safety's sake that value should probably move to a separate option similar to https://zuul-ci.org/docs/zuul/reference/drivers/github.html#attr-%3Cgithub%20connection%3E.webhook_token12:41
fungiit would be better if leaving out the canonical_url inadvertently exposed a password12:42
fungier, better if it *didn't* i mean12:42
* fungi tries to get more coffee into his veins12:42
avassmasterpe: yeah, canonical_url defaults to server if it's not set12:42
avassfungi: yeah12:43
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-package-repositories: Add role  https://review.opendev.org/71750712:46
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-package-repositories  https://review.opendev.org/71750812:46
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-package-repositories  https://review.opendev.org/71750912:46
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737512:46
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-package-repositories  https://review.opendev.org/71751012:46
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure--package-repositories  https://review.opendev.org/71751112:46
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-package-repositories  https://review.opendev.org/71751212:46
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-package-repositories  https://review.opendev.org/71751312:46
masterpehad to use the cloneurl to solve this12:47
avassthis is ready: https://review.opendev.org/#/c/724810/ :)12:48
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781712:49
avassmasterpe: yeah that looks like a better option :)12:49
AJaegerif we use a role ensure-nodejs from ensure-yarn, do we add a file-matcher on ensure-yarn for ensure-nodejs as well? See https://review.opendev.org/#/c/717817/9/zuul-tests.d/js-roles-jobs.yaml12:53
* AJaeger thinks we need to update the stack a bit more for this, but wants feedback from zuul-jobs experts on this ^12:53
* AJaeger found the answer, we do this in other case. Sorry, another change set is coming...12:54
avassAJaeger: I'd say yes12:55
avassAJaeger: I think it's more important that we don't break something than we run more tests12:55
avass:)12:55
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write buildkitd.toml in use-buildset-registry  https://review.opendev.org/72483712:58
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-package-repositories  https://review.opendev.org/71750813:01
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-package-repositories  https://review.opendev.org/71750913:01
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737513:01
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-package-repositories  https://review.opendev.org/71751013:01
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure--package-repositories  https://review.opendev.org/71751113:01
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-package-repositories  https://review.opendev.org/71751213:01
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-package-repositories  https://review.opendev.org/71751313:01
AJaegeravass: agreed, and found we do it elsewhere  -so updated again...13:01
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475713:03
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write buildkitd.toml in use-buildset-registry  https://review.opendev.org/72483713:03
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781713:05
mordredAJaeger: comment on that last one13:05
mordredAJaeger: on 71751313:05
AJaegermordred: only on the last one? Good ;) thanks13:06
avassmordred: heh, tristanC already commented that on an earlier patchset ;)13:07
mordredhaven't looked at the others yet :)13:07
mordredhaha13:07
AJaegerI wanted to do that - let me check where I screwed up13:07
mordredAJaeger, avass: so - that has pointed out to me I've need to go update our use of ppa:projectatomic ...13:08
mordredturns out we want to use it for xenial but for bionic and focal we want to use kubic13:08
mordred\o/13:09
AJaegerah, there were two places where it needed removing, I only touched one - done now.13:09
mordredsweet13:09
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-package-repositories  https://review.opendev.org/71751313:09
AJaegermordred: so, want to make a change and I rebase this stack - or help merging this stack? ;)13:12
mordredAJaeger: oh - I'll totally do it after that stack :)13:12
mordredAJaeger: I have way too many balls juggling right now13:13
avassI know that feeling13:13
* AJaeger knows it as well...13:13
AJaegeranybody an idea why Zuul complains now on https://review.opendev.org/#/c/717513 about "an invalid configuration". Everything else in the stack looks sane13:15
corvusmordred: with https://review.opendev.org/724344 approved do you want to abandon https://review.opendev.org/717613  ?  :)13:16
avassAJaeger: I think that's a bug13:16
AJaegertobiash, tristanC, want to review the ensure-repositories stack again? It starts at https://review.opendev.org/#/c/717507/ and I just updated heavily13:17
corvusthe memory use on opendev is much better; enough that i think we can say that it looks like a memory leak in latest cherrypy13:17
AJaegeravass: ok, let's wait...13:17
AJaegercorvus: great13:18
corvuswebknjaz: hi, i suspect there is a memory leak in cherrypy 18.6.013:18
avasscorvus, mordred, AJaeger: update to loop-var linting so we catch with_ type loops is ready: https://review.opendev.org/#/c/724810/13:19
tristanCAJaeger: thanks!13:21
AJaegeravass: wow, will review later.13:21
avassAJaeger: yeah, might have to update it later if any loops get merged before it :)13:22
mordredcorvus: wow - I did that twice?13:22
AJaegermordred: a wise man said recently "I have way too many balls juggling right now" ;)13:23
avasshaha13:24
AJaegercorvus: you had a -1 earlier on https://review.opendev.org/#/c/717817/ - could you review again, please?13:24
mordredAJaeger: hahaha13:24
AJaegerargh, stack still broken - fixing RedHat installs..13:26
avasscorvus: if we don't want to keep the owner of unarchived or synchronized files between executor and remote, how about we add a linting rule for that too?13:27
mordredcorvus: latest buildkit patch didn't work - but looking at the registry logs, it's showing containerd as the UA - so maybe I need to do https://github.com/containerd/cri/blob/master/docs/registry.md13:28
corvusavass: have we fixed that yet and proven it everywhere?13:28
avasscorvus: no :)13:29
corvusavass: we should probably make sure the pattern is well established, proven, and always necessary before adding a linting rule; and it should probably be in the policy docs too :)13:29
AJaegerhttps://zuul.opendev.org/t/zuul/build/050ceb250c7f4c878ef40d3f4523b614 fails - could anybody tell me what I did wrong in https://review.opendev.org/#/c/717507/11/roles/ensure-package-repositories/tasks/RedHat.yaml , please?13:30
AJaegercorvus: thx13:30
avasscorvus: yeah I was thinking of writing some docs for that when I start working on it :)13:30
corvusmordred: do we not do that one already?  (jeez, how many of these are there?)13:30
avassAJaeger: left a comment13:32
corvusmordred: ok, i don't see it.  so i guess we should add that13:32
mordredcorvus: right?13:33
AJaegerthanks, avass13:34
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-package-repositories: Add role  https://review.opendev.org/71750713:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-package-repositories  https://review.opendev.org/71750813:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-package-repositories  https://review.opendev.org/71750913:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737513:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-package-repositories  https://review.opendev.org/71751013:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure--package-repositories  https://review.opendev.org/71751113:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-package-repositories  https://review.opendev.org/71751213:36
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-package-repositories  https://review.opendev.org/71751313:36
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: use-buildset-registry: fix modify_registries_conf library idempotency  https://review.opendev.org/72484013:36
mordredcorvus: I don't _know_ that that config will be the one13:36
mordredcorvus: it's also possible we need to restart buildkitd in the container13:37
avasscorvus: but since the synchronize owner/group parameter tries to set the owner to user on the remote, I'd say it's necessary to make sure it works for every system. Unless we want to force everyone to create a user on the executor for every user they have on a remote node :)13:37
corvusmordred: it looks like we should be able to add the prefix needed to support multiple registries; so this should enable more than docker.io.13:37
corvusavass: i'm pretty sure you're right; i just don't want the linting rules to get ahead of the practice :)13:37
mordredcorvus: which - I'm going to try now on my test node, because I'm not sure if that's even possible if it's the only process in the container - we might have to build our own image and tell buildx to use it13:37
mordredcorvus: heh. yeah - killing buildkitd sure does kill the container - but docker start sure does re-start it :)13:39
avasscorvus: sure, I'll push a change for it to get it ready, but we can wait with merging it13:39
mordredcorvus: actually - before I go writing containerd.toml - I'm going to toss in a container restart - I think that might be required to pick up the config.json now that I think of it13:40
corvusmordred: https://github.com/containerd/containerd/blob/master/.zuul.yaml13:40
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: use-buildset-registry: do not update ca when not necessary  https://review.opendev.org/72484113:40
corvustristanC, fbo|off: ^ fyi containerd repo has a .zuul.yaml from openlab13:41
tristanCcorvus: that is nice :-)13:42
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475713:43
avassAJaeger: left another comment :)13:44
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write buildkitd.toml in use-buildset-registry  https://review.opendev.org/72483713:44
tristanCcorvus: containers/libpod doesn't have a zuul.yaml, but rdoproject's zuul check each PR13:44
*** sanjayu_ has joined #zuul13:44
fungihttps://github.com/theopenlab/13:45
corvustristanC: that's some nice cross-community collaboration going on :)13:45
fungiinterestingly, they have a zuul-jobs fork from the defunct openstack-infra/zuul-jobs github mirror13:45
fungihttps://openlabtesting.org/ seems to have an expired letsencrypt cert13:46
fungiseveral weeks expired13:46
*** saneax has quit IRC13:47
masterpeHow can I figerout what to do with the pipeline in the config repo with the gitlab driver?13:47
corvusmasterpe: there isn't complete documentation since it's not finished yet, but a lot of it should be similar to github: https://zuul-ci.org/docs/zuul/reference/drivers/github.html#reference-pipelines-configuration13:48
fungilooks like openlab's zuul instance is still up and running, at least: http://status.openlabtesting.org/13:49
*** bhavikdbavishi has quit IRC13:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-package-repositories: Add role  https://review.opendev.org/71750713:49
*** guillaumec has joined #zuul13:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-package-repositories  https://review.opendev.org/71750813:49
AJaegeravass: thanks13:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-package-repositories  https://review.opendev.org/71750913:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737513:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-package-repositories  https://review.opendev.org/71751013:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-podman: refactor to use ensure--package-repositories  https://review.opendev.org/71751113:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-docker: refactor to use ensure-package-repositories  https://review.opendev.org/71751213:49
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: cleanup: move tests to use ensure-package-repositories  https://review.opendev.org/71751313:49
corvusmasterpe: /win 1113:50
corvusoops13:50
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add CA certificate to the registry tls secret  https://review.opendev.org/72484413:51
*** bhavikdbavishi has joined #zuul13:51
corvusmordred: i just double checked and didn't see a way to reload the config without restarting containerd13:55
AJaegerensure-package-repositories stack loooks passing now. please review https://review.opendev.org/#/c/717507 and https://review.opendev.org/717513 so that we can merge this stack13:56
* AJaeger enjoys tea now...13:56
mordredcorvus: I tossed in a docker restart - let's see what that does for us14:01
*** bhavikdbavishi has quit IRC14:05
mordredcorvus: quick question ...14:07
mordredcorvus: reading this log: https://zuul.opendev.org/t/zuul/build/8d355b2bd85a4a5c8a8ae8e3bf348a9f/log/builder/docker/buildset_registry.txt#12414:08
masterpeIf I use the example pipeline on https://zuul-ci.org/docs/zuul/reference/drivers/github.html#reference-pipelines-configuration I get a couple of failues: http://paste.openstack.org/show/792988/  @fbo can post an example?14:09
mordredcorvus: it looks like we might be authenticating? but looking for things that aren't there?14:09
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475714:18
openstackgerritMerged zuul/zuul master: Install skopeo in container images  https://review.opendev.org/72434414:19
*** sanjayu__ has joined #zuul14:19
*** sanjayu_ has quit IRC14:22
AJaegeryeah,stack starting at https://review.opendev.org/717513 passes fully - please review14:23
AJaegerhttps://review.opendev.org/#/c/717507 is the start of the ensure-package-repositories stack - 717513 is the end14:24
AJaegerthose two are the only ones that need two +2s14:25
*** lseki has joined #zuul14:30
AJaegertristanC, avass, in case you want to review again, please ^14:33
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485514:33
AJaegeroh, there are more changes that need a second +2 in the stack...14:35
AJaegermordred: thanks for some reviews14:35
avassAJaeger: I'll look :)14:35
AJaegerthx14:36
AJaegeravass: once that stack is merged, I'll review others - including your loop change14:37
corvusmordred: yeah https://zuul.opendev.org/t/zuul/build/8d355b2bd85a4a5c8a8ae8e3bf348a9f/log/builder/docker/buildset_registry.txt#134  is a 404 -- zuul-registry doesn't implement HEAD on a manifest14:37
mordredcorvus: so - we are now authenticating, but there's a missing verb in zuul-registry?14:40
mordred(just making sure I'm getting it all right in my brain head)14:41
corvusmordred: yep, i'm looking at adding it14:41
mordredcool14:42
avassAJaeger: everything looks good to me14:42
AJaegerthanks, avass14:42
avassAJaeger: and it didn't break the loop linting :)14:43
AJaegergreat!14:44
*** sanjayu__ has quit IRC14:46
AJaegercorvus, https://zuul.opendev.org/t/zuul/status hows me that https://review.opendev.org/717510 is failing since "it has an invalid configuration" - but it passed checks14:46
AJaegerthat looks like a bug - isn't it?14:47
openstackgerritJames E. Blair proposed zuul/zuul-registry master: Support HEAD on manifests  https://review.opendev.org/72485914:47
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485514:48
corvusmordred: 72485914:48
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475714:50
mordredcorvus: depends-on inception14:50
*** zxiiro has joined #zuul14:51
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485514:51
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Do not keep owner when pulling zuul-output  https://review.opendev.org/70138114:51
AJaegeravass: just addressed the nits ^14:51
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485514:52
avassAJaeger: thanks!14:53
AJaegercorvus: you had a -1 on 701381 earlier, want to review again?14:54
openstackgerritMerged zuul/zuul-jobs master: ensure-package-repositories: Add role  https://review.opendev.org/71750714:57
openstackgerritMerged zuul/zuul-jobs master: ensure-nodejs: refactor to use ensure-package-repositories  https://review.opendev.org/71750814:57
openstackgerritMerged zuul/zuul-jobs master: ensure-yarn: refactor to use ensure-package-repositories  https://review.opendev.org/71750914:57
openstackgerritMerged zuul/zuul-jobs master: install-yarn: always install  https://review.opendev.org/71737514:57
mordredcorvus: interestingly - https://review.opendev.org/#/c/724837/ - also fails on the podman job14:57
AJaegercorvus: https://review.opendev.org/717510 has "unknown configuration error"14:58
AJaegerzuul-maint, should I recheck or is there something you want to investigate?14:59
avassAJaeger: recheck :)15:01
avassAJaeger: I think it's known, but no one has figured out why it happens yet15:02
AJaegerthx - will do in a few minutes15:02
avassAJaeger: except that it happens whenever you have big stacks like that15:02
corvusAJaeger: 701381 lgtm;  it's tested so should be safe to land, but it'll be good to keep an eye on opendev jobs when it does15:03
zbravass: regarding ansilbe-lint, I just added a RFP at https://github.com/ansible/ansible-lint/issues/75515:03
AJaegercorvus: I'll merge slowly one stack after the other...15:03
corvusmordred, clarkb: can one of you also look at https://review.opendev.org/701381  ?  ( AJaeger, avass: let's get one more set of eyes on that)15:04
AJaegercorvus: ok15:05
*** rlandy is now known as rlandy|biab15:05
avasscorvus: sure15:05
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781715:08
openstackgerritSorin Sbarnea (zbr) proposed zuul/zuul-jobs master: fetch-sphinx-tarbal: allow to follow symlinks  https://review.opendev.org/72486815:13
avasszbr: interesting15:14
clarkbcorvus: avass AJaeger I've approved it15:14
AJaegerthanks, clarkb15:15
zbravass: see https://dashboard.zuul.ansible.com/t/ansible/build/e959ce3203dc495cabe9bef7caaf4040/console15:15
*** sgw has joined #zuul15:21
mordredcorvus: the podman failure is now showing up in more places15:21
mordredcorvus: https://zuul.opendev.org/t/zuul/build/8b5cbca02d89483e9714e9e8348980d515:21
mordredcorvus: https://zuul.opendev.org/t/zuul/build/8b5cbca02d89483e9714e9e8348980d5/log/builder/podman/buildset_registry.txt#22015:21
*** sanjayu__ has joined #zuul15:24
openstackgerritMerged zuul/zuul-jobs master: ensure-kubernetes: refactor to use ensure-package-repositories  https://review.opendev.org/71751015:28
openstackgerritMerged zuul/zuul-jobs master: ensure-podman: refactor to use ensure--package-repositories  https://review.opendev.org/71751115:28
tobiashmordred: did that multi arch change land could that have something to do with those failures?15:29
*** dpawlik has joined #zuul15:30
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: haskell-stack-test: add haskell tool stack test  https://review.opendev.org/72326315:35
openstackgerritMerged zuul/zuul-jobs master: ensure-docker: refactor to use ensure-package-repositories  https://review.opendev.org/71751215:36
AJaegerI had to resolve a merge conflict on https://review.opendev.org/717817 - could I get reviews again, please? That is part of the ensure-package-repositories zuul-jobs stack15:38
openstackgerritMerged zuul/zuul-jobs master: cleanup: move tests to use ensure-package-repositories  https://review.opendev.org/71751315:39
openstackgerritMerged zuul/zuul-jobs master: Add Bazel build and ensure roles  https://review.opendev.org/69351315:39
openstackgerritMerged zuul/zuul-jobs master: Do not keep owner when pulling zuul-output  https://review.opendev.org/70138115:39
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485515:41
zbrcorvus: mordred: any chance to do https://review.opendev.org/#/c/724868/ ?15:43
*** bhavikdbavishi has joined #zuul15:45
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485515:48
avasscorvus: alright, I think we can keep the discussion in that ^ change now :)15:48
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485515:49
mordredtobiash: nope, still working on it15:50
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add ansible-lint rule to check owner and group is not preserved  https://review.opendev.org/72485515:53
AJaegeravass: want to review https://review.opendev.org/723263 again after the rename of directories, please?15:55
avassAJaeger: sure15:56
AJaegerthx15:56
AJaegerclarkb, mordred, corvus, avass has a stack up to change the "ignore_errors" we use, could one of you review the stack starting at https://review.opendev.org/#/c/723640/ , please?15:57
*** bhavikdbavishi has quit IRC16:01
avassI'll be back in an hour, going for a walk :)16:03
clarkbAJaeger: I feel like I don't know enough about ansible to properly say if the old or new code is preferred there16:04
openstackgerritMerged zuul/zuul-jobs master: Check for loop_control in with_ type loops  https://review.opendev.org/72481016:06
AJaegerclarkb: thx for checking16:06
*** bhavikdbavishi has joined #zuul16:06
*** dpawlik has quit IRC16:08
openstackgerritMerged zuul/zuul-jobs master: fetch-sphinx-tarbal: allow to follow symlinks  https://review.opendev.org/72486816:08
openstackgerritMerged zuul/zuul-jobs master: haskell-stack-test: add haskell tool stack test  https://review.opendev.org/72326316:09
AJaegeravass: enjoy the walk. could you double check later your loop_control change. I would expect that "item" is unused now but it's not, like in test-playbooks/multinode/persistent-firewall.yaml16:11
tristanCAJaeger: avass: thank you for reviewing the new haskell jobs!16:28
AJaegertristanC: you're welcome!16:30
AJaegertristanC: do you have time to review https://review.opendev.org/#/c/717817/  after merge-conflict, please? and the stack starting at https://review.opendev.org/#/c/723640 ?16:31
* AJaeger is currently spring-cleaning zuul-jobs16:31
AJaegermnaser: shall we merge https://review.opendev.org/#/c/724132/ now?16:32
*** rlandy|biab is now known as rlandy16:33
*** evrardjp has quit IRC16:35
*** evrardjp has joined #zuul16:36
avassAJaeger: the policy is only for roles since they can be imported and used in other projects, it's fine to use the default loop_var 'item' in playbooks and tests16:58
avassAJaeger: that's why i only check tasks: https://opendev.org/zuul/zuul-jobs/src/branch/master/.rules/ZuulJobsNamespaceLoopVar.py#L1916:59
openstackgerritMerged zuul/zuul-jobs master: tox: Use 'block: ... always: ...' instead of ignore_errors  https://review.opendev.org/72364017:01
openstackgerritMerged zuul/zuul-jobs master: ensure-sphinx: use failed_when: false instead of ignore_errors: true  https://review.opendev.org/72364217:01
clarkbtobiash: are you still building your own zuul images?17:03
tobiashclarkb: yes17:04
clarkbwe are seeing memory leaks in opendev and I'm trying to compile a list of changes and realized that in addition to code changes we switched from running on ubuntu xenial hosts to running in zuul built containres which changed python3 versions and libc (and possibly other system libs)17:04
corvusclarkb: i wonder if scheduler memory use corresponds with the leading_errors bug?17:05
clarkbcorvus: I'm not familiar with that bug17:05
corvusi was just looking for log entries about the incident that AJaeger mentioned earlier and since you mentioned scheduler memory growing around the same time i thought maybe they're related17:05
corvusclarkb: it's your pet bug17:05
corvusAttributeError: 'NoneType' object has no attribute 'loading_errors'17:05
corvus2020-05-01 14:42:29,373 DEBUG zuul.Pipeline.zuul.gate: [e: b1ce40a9ea0d47b096e694914c8d9a37] <QueueItem 0x7f99c5cb8b50 for <Change 0x7f99db37d810 zuul/zuul-jobs 717510,9> in gate> is a failing item because ['it has an invalid configuration']17:05
clarkboh that one17:05
corvusclarkb: that one^17:05
corvusclarkb: 2020-05-01 13:09:57,081 is first instance today17:06
tobiashclarkb: at least we had a memleak with py37 a year ago and reverted to py36 and that's what we're running tipl now17:08
corvusclarkb: hrm, not a strong correlation there, but there is a stronger correlation at 14:42:29,373 today17:08
tobiashs/tipl/till17:08
clarkbcorvus: and according to cacti thats about when it started increasing the rate of growth17:09
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475717:10
mordredcorvus: ^^ hopefully that will work with requires: lines17:10
mordredclarkb, corvus, tobiash: we can also switch the base image to py3.8 at some point if we want to compare/try that17:11
clarkbmordred: or 3.6?17:11
mordredclarkb: well, we'd have to start building 3.6 python-base images - but yes, we could do that too17:11
clarkbnote the bug corvus is talking about has been observed on 3.5 and 3.7 now so doesn't seem version specific17:12
mordredtotally- it's possible the leak we're seeing is related to the bug17:12
webknjazcorvus: AFAIR the only thing added in the last version is support for UTF-8 filenames in the content-disposition header. Open a ticket if you have a reproducer17:12
mordredbut it's also possible there is a bug in 3.7 :)17:12
mordredmany things to try17:12
clarkbmordred: yup17:13
mordredclarkb: I think I'd suggest if we start trying different python versions we try 3.8 first - since that would be a roll forward - and if that doesn't have it we can try 3.617:13
clarkbmordred: ++17:13
corvuswebknjaz: i don't yet; it's just an indication at this point.  thought i'd give you a heads up.17:13
mordredbut - I think poking at the loading_errors bug first before we start doing python version roulette17:13
corvuswebknjaz: could be a false alarm, but in case someone else reports it, it's a data point17:13
clarkbon the loading_errors bug I dug into ita bit and think I wandered down an invalid path. Might be good to have fresh eyes on it?17:14
webknjaz👍17:15
clarkbthis mightalso be a case where we need more logging17:15
clarkbwe can catch the exception and log some state?17:15
openstackgerritMerged zuul/zuul-jobs master: ensure-yarn: run ensure-nodejs before  https://review.opendev.org/71781717:24
mordredcorvus: 2020-05-01 17:19:44,960 INFO cherrypy.access.140474922906896: ::ffff:172.17.0.1 - - [01/May/2020:17:19:44] "HEAD /v2/upstream/image/manifests/latest HTTP/1.1" 404 767 "" "containerd/1.3.0+unknown"17:28
mordredcorvus: still getting 404s17:28
mordredcorvus: perhaps since we're testing buildset registry we're not using buildset-registry for zuul-registry itself?17:29
corvusmordred: it should be plumb completely through -- there's actually quite a bit of code to make sure that the test buildset registry uses an image from the real buildset registry17:29
corvusmordred: it's probably worth a quick look at the logs to verify that's working (maybe checking image shas or pull logs or whatever), then we should probably confirm the functionality with a local test17:31
mordrednod17:31
corvusmordred: i'm still combing through loading_error logs, but can pitch in on that in a few mins17:31
mordredcorvus: in the meantime, there's a pep8 error - I can push up a fix for it if you want17:31
corvusmordred: ++17:31
openstackgerritMonty Taylor proposed zuul/zuul-registry master: Support HEAD on manifests  https://review.opendev.org/72485917:32
mordredclarkb: if you get a sec ^^17:32
mordredcorvus: I'm going to attempt to discover the concept known as "sandwich"17:32
mordredcorvus: so maybe let's sync in a bit17:32
corvusmordred: oh wait -- i *may* be thinking of the jobs in zuul-registry repo17:32
corvusmordred: it may be worth a look at that -- perhaps they work with speculative images but the ones in zuul-jobs don't?  i don't know, it's all worth double checking.17:33
corvusmordred: (also, maybe we should add a buildx job to zuul-jobs)17:33
corvusgrr17:33
corvusmordred: (also, maybe we should add a buildx job to zuul-registry)17:33
mordredcorvus: yes to bopth of those things17:33
mordredI'll see what I can see17:34
AJaegeravass: ah, thanks!17:39
corvusclarkb: theory: 2 changes in queue; first is a regular change, second has a dynamic config update; launch merge jobs for both; the second merge job arrives before the first; item.layout on the first change is not primed, but we process the second item anyway.17:40
AJaegeravass: what about roles/ensure-bazel/tasks/install-bazel.yaml ?17:40
clarkbcorvus: ooh17:41
AJaegeravass: and roles/configure-mirrors/handlers/main.yaml17:41
corvusclarkb: that should be provable in a unit test.  if that's so, that would explain the exception; not sure if the exception can explain the leak17:41
avassAJaeger: I'm not sure why it's not reacting to install-bazel, have to take a look at that later17:42
avassAJaeger: but yeah ,should probably check handlers as well17:43
avassAJaeger: maybe we should have tests for the custom linter rules :)17:44
AJaegermaybe :)17:45
avassAJaeger: oooh, for some reason ansible-lint thinks install-bazel is a playbook17:46
avassI guess that's a bug in ansible-lint17:47
zbrthe detection logic is flawed in many places, what can you expect when yaml is so popular? :)17:47
zbrtry to help it using ignore patterns17:48
avassbut you would think checking if it's a playbook would be easy, just check if "- hosts:" exist or not17:48
zbrit is far more complex than this, it needs to detect: playbooks, tasks, vars, roles,....17:48
avassah wait, no it detects is as a task if i give it the role path instead of the yaml file directly17:49
avassor, a tasks list17:49
AJaegercorvus, mordred, we reverted earlier https://review.opendev.org/#/c/723524/ and avass has fixed it in https://review.opendev.org/#/c/724132/ - want to merge again?17:49
zbruntil recently we did not had any guidelines for repository layout, but luckly collections helped.17:49
zbri am considering proposing a change to support only collection layout.17:50
corvusclarkb: i was looking into why this error doesn't happen over and over, and it turns out the situation can correct itself, but zuul has already annotated the item with the config error list, so it's stuck thinking it's an error until the next time it's enqueued (or nnfi changes)17:52
corvusas typified by these 2 lines: 2020-05-01 14:42:32,645 INFO zuul.Pipeline.zuul.gate: [e: b1ce40a9ea0d47b096e694914c8d9a37] Configuration syntax error not related to change context. Error won't be reported.17:53
corvus2020-05-01 14:42:32,646 DEBUG zuul.Pipeline.zuul.gate: [e: b1ce40a9ea0d47b096e694914c8d9a37] <QueueItem 0x7f99c5cb8b50 for <Change 0x7f99db37d810 zuul/zuul-jobs 717510,9> in gate> is a failing item because ['it has an invalid configuration']17:53
corvusthey're kind of contradictory when you think about it :)17:53
avassAJaeger: good job finding that, I'll try to figure out what's happening with install-bazel :)17:53
clarkbcorvus: that first message is what led me astray I think17:53
corvus("will not be reported"..."has in invalid configuration")17:53
clarkbcorvus: it had me thinking the error was elsewhere so we just had to ignore it17:53
AJaegeravass: thanks - but no urgency for that one, it's not a false positive ;)17:54
AJaegercorvus: and re-approving the change it merged. So, somehow Zuul was confused17:55
corvusAJaeger: that re-enqueued it, so it started with a clean slate17:55
AJaegerthere was no invalid configuratoin - just Zuul thought with 8 changes enqueued there is one17:55
AJaegercorvus: yes17:55
corvusAJaeger: my unconfirmed theory is that the connection with the number of changes is that more changes means more opportunity for config merge jobs to race, so the original bug is more likely to manifest17:56
AJaeger"race" - ah!17:56
corvusAJaeger: yeah see my msg at 17:40 for an explanation of the (suspected) race sequence17:57
AJaegerI saw it - but now I parse it correctly. thanks17:58
corvusit was shorthand :/17:58
AJaegerit was me reading too quickly17:59
*** bhavikdbavishi has quit IRC18:01
corvusclarkb: re memory, this can cause mayn more throwaway dynamic layouts to be built (basically, one for each pass through the queue during the window where the second merge job has completed but the first has not).  i see several of thos in the 13:00 hour, but only 2 near the 14:42 event.  i sort of expect them to be cleaned up correctly by the gc too.  i think it'd be a stretch to tie the memory leak to this18:01
corvusat this point.  not impossible, but i think if it is, it's more likely to be some weird python gc edge case, and not a zuul logic bug.18:01
clarkbgotcha, we probably want to fix it either way since its a user noticeable bug but unlikely to be our memory fix18:02
corvusyep18:02
corvusi plan on writing a unit test to confirm/repo and then a fix after helping mordred.  but before that, i need some exercise; biab.18:03
corvusalso, i really apologize for my spelling today, it's atrocious18:03
avassAJaeger: Wow.... "include" isn't a taask18:11
avassAJaeger: so for includes we'd have to use "match" to match individual lines instead of "matchtask" ...18:11
AJaegerInteresting18:15
avassAJaeger: so we could to a simple check for include, include_tasks, and check if they use "item", but not for include_role, since that has a different syntax for some reason18:17
AJaegerone step at a time ;)18:24
AJaegerzuul-jobs reviewers, the stack at https://review.opendev.org/#/c/723643 and https://review.opendev.org/#/c/724132/ would be nice to get some review love, please18:34
openstackgerritMonty Taylor proposed zuul/zuul master: Build zuul images with python 3.8  https://review.opendev.org/72490818:40
mordredclarkb: ^^18:40
clarkb+2 thanks18:42
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491018:51
avassAJaeger: I guess you just have to use undocumented features *shrug*18:51
avassAJaeger: and for some reason it's a 'task' if you match the play, I'll have to check if this is a bug or not18:52
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491019:04
AJaegerzbr: is that something you can help avass with, please? ^19:09
openstackgerritClark Boylan proposed zuul/zuul-jobs master: Fix some item usage where var is zj_* now  https://review.opendev.org/72491619:10
clarkbAJaeger: avass ^ is a bug with loop control var renaming that was discovered by one of our users19:10
AJaeger+2A19:12
avassclarkb: thanks!19:16
clarkbGoing to mention it here since I don't have time to fully debug it currently, but zuul-web's SIGUSR2 handling isn't completely correct. It does dump threads an all that as expected but it also stops the service19:25
*** lseki has quit IRC19:35
mordredclarkb: well that's less than awesome19:39
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491019:47
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491019:53
*** Goneri has quit IRC19:55
corvusmordred: need a hand on the registry thing?  i'm all yours now20:01
mordredcorvus: yes!20:01
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491020:09
avassI feel like a hypocrite using the default loop var in the tests :)20:10
AJaegeravass: something is wrong in stage-output, see https://zuul.opendev.org/t/openstack/build/3a76691e85dd4faeb582d30fab9f19a2/console20:10
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491020:10
avasschecking20:11
AJaegerhttps://zuul.opendev.org/t/openstack/builds?result=POST_FAILURE shows more20:11
AJaegerhttps://review.opendev.org/#/c/724810/4/roles/stage-output/tasks/main.yaml looks broken - I don't see it yet20:14
avassI can't figure out what could be wrong either20:15
AJaegerThe errors point to https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/stage-output/tasks/main.yaml#L34-L4620:15
AJaegeranybody has an idea?20:15
avassyeah, either that of the sources stat is wrong20:16
avassI can't see anything that could be wrong, it's just a 's/item/zj_source/' pretty much20:21
corvusagree20:21
AJaegerso, how to unbreak? Revert that change for now?20:22
mordredyeah - I looked at the diff from previous and it looks fine20:22
avassshould we change it back to 'item' and ignore the linting for that file for now?20:22
corvusi'm trying to repro locally; give me a few mins to do that20:22
avassand see if that fixes it20:22
*** iurygregory has joined #zuul20:23
mordredAJaeger: if we revert - we need to find the other follow changes we've made - but let's wait for corvus20:23
AJaegermordred: agreed20:23
corvusmaybe start preparing that change in case i fail?20:23
AJaegermordred: https://review.opendev.org/#/c/724916/ is not merged yet20:23
* AJaeger removed the +A from 72491620:24
mordredAJaeger: nod20:24
mordredAJaeger: yeah - let's prep the revert patch - just in case20:24
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Revert "Check for loop_control in with_ type loops"  https://review.opendev.org/72492320:24
corvusi have repro'd20:25
AJaegerhere's a *complete* revert ^20:25
AJaegercorvus: cool20:25
corvusfatal: [localhost]: FAILED! => {"msg": "The conditional check 'zj_source.item.value' failed. The error was: error while evaluating conditional (zj_source.item.value): 'dict object' has no attribute 'item'\n\nThe error appears to be in '/tmp/test.yaml': line 14, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n      register: sources\n20:25
corvus  - name: Set source and destination for files and folders\n      ^ here\n"}20:25
clarkbcorvus: and you ran the task "Register sources" at the beginning of the file ?20:26
AJaegeravass just renamed "item.item.value" to zj_source.item.value20:26
* AJaeger is puzzled20:26
clarkbI wonder if reusing the zj_source var from that loop impacts the subsequent task odly20:26
corvusclarkb: ya20:26
corvusclarkb: i just tried that -- renamed the second zj_source, same error20:26
corvusclarkb: good idea though, i thought :)20:27
avassooh20:27
avassthis might be stupid, but could this be it?20:28
mordredthere are no stupid things in this context :)20:28
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: use zj_source.zj_source  https://review.opendev.org/72492520:28
clarkbif that is the fix then I think my change for the pdf thing needs updating too20:28
AJaegeravass: interesting theory20:28
clarkbit still has a foo.time20:29
clarkb*foo.item20:29
corvusthat runs without error20:29
mordredWOW20:29
AJaegerthen we should also double check avass' change whether there are other problems20:29
clarkbnice20:29
avasswow20:29
AJaegerWow indeed20:29
mordredI *never* would have imagined that - but now that it's there it makes sense20:29
corvusyeah.  mind boggled.20:29
clarkbsomeone should update my pdf change, feel free to do that20:29
clarkb(I need to pop out)20:29
mordredI mean "makes sense"20:29
corvusmordred: i'll have what you're having :)20:29
mordredI'm guessing we need to do a quick search for use of with_dict20:30
corvusmordred: that was with_items20:30
AJaegercan you take care of this, please? I need to call it a day now... Feel free to abandon my revert20:30
mordredit was the earlier with_dict along with loop_var that caused the inner item to be zj_source I thnjk20:31
mordredhttps://review.opendev.org/#/c/724810/4/roles/stage-output/tasks/main.yaml lines 1-820:31
AJaegerAh!20:32
mordredcorvus: could test that theory by changing that loop var to something else and then seeing if the second item should match it20:32
mordredbut I think it's the register along with that with_dict that is the source of the inner .item20:32
corvusmordred: i did a debug on sources and it says             "zj_source": {20:32
AJaegerSo, https://review.opendev.org/#/c/724916/1/roles/fetch-sphinx-tarball/tasks/pdf.yaml looks fine, doesn't it?20:32
corvus"zj_source": {"key": "/var/log/syslog", "value": "logs_txt"}20:33
mordredyeah. that's because of the loop_var in the thing that created it20:33
corvusmordred: yeah, "makes sense"20:33
mordredcorvus: "exactly"20:33
SpamapSisn't everything supposed to be with: now anyway?20:33
mordredSpamapS: well - there are about 7 different "supposed to"s20:33
mordred:)20:33
mordredcorvus: maybe we shoudl change the first one to be a different name just for clarity20:33
corvusSpamapS: maybe you're thinking of everything should be "loop" but they changed their minds on that and with_* is fine again20:34
mordredyeah20:34
AJaegerso, can we +A https://review.opendev.org/724916 ?20:34
mordredbecause it turns out loop+lookup is bonghits bad20:34
SpamapSoh right loop:20:34
avassSpamapS: yeah loop is preferred20:34
* SpamapS may not have looked at any ansible for about 2 months. ;)20:34
mordredavass: they changed their mind20:34
corvusavass: i would not say that at this point :)20:34
avassah :)20:34
mordredavass: you want to update your patch?20:35
mordredor I can if you're busy20:35
avassyou can do it :)20:35
corvusmordred: what needs updating?20:35
avasschanging the first zj_source?20:35
corvushttps://review.opendev.org/724925 looks fine to me20:35
mordredyeah - so that it's clear to readers of the file what's coming from where20:35
corvusok20:35
corvusi'll wait for an update20:35
tristanCcorvus: we got a first successfull image-update >> image-test >> image-promote pipeline execution. From such image description: https://softwarefactory-project.io/cgit/zuul-images-jobs/tree/example/openstacksdk.dhall , we created this zuul configuration : https://softwarefactory-project.io/cgit/zuul-images-jobs/tree/example/pipeline.yaml20:35
AJaegerthanks everybody!20:36
mordredavass: also - good idea on that :)20:36
* AJaeger waves good night and wishes everybody a nice weekend20:36
mordredAJaeger: have a good weekend!20:36
avassmordred: it was a gut feeling :)20:37
avassAJaeger: bye!20:38
tristanCcorvus: about using the zuul-registry, we proposed those improvements: https://review.opendev.org/#/q/topic:use-buildset-registry-idempotency20:38
corvustristanC: great!  i've got several fires that need putting out right now, but next week when things settle down, let's work on integrating the registry roles you need with the rest of the system to maximise reuse and interoperability.  also, i have ideas about how this could be done with gating if you want to have a design session to talk about it.20:38
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491020:38
corvustristanC: cool, i expect those should be straightforward20:39
corvusavass: you're updating 724925 right?20:39
corvusoh, no mordred is updating it20:40
corvussorry i missed that20:40
tristanCcorvus: then looking at `upload-docker-image` and `promote-docker-image`, it seems very specific to docker and dockerhub, so i'm not sure how we could add podman and other registry support20:41
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Distinguish zj_source and zj_result and item  https://review.opendev.org/72492520:41
mordredcorvus, avass, clarkb: ^^20:41
corvustristanC: the general rule is that if it says 'docker' in the name it's intentionally docker-based and we probably want a new job/role.  the ones that don't say docker should work for anything.20:41
corvustristanC: mostly i say that so you know what the expectation was when the role was originally written20:42
mordredyeah - so use-buildset-registry should handle everything. but we need an upload-container-image that's not docker specific to go along with build-container-image20:42
mordredyeah?20:42
corvusmordred: yep: https://zuul-ci.org/docs/zuul-jobs/container-roles.html has a note (cc tristanC )20:43
tristanCmordred: the main issue we have with use-buildset-registry is that the registry.cert needs to be the issuer ca.crt, not the registry tls.crt20:43
tristanCor at least on fedora after running update-ca-trust, that didn't work with the tls.crt content20:43
corvustristanC: then we should identify and fix that bug20:43
corvusanyway, i really need to get back to firefighting20:44
corvus925 is approved20:44
mordredwoot20:44
tristanCcorvus: mordred: i think our initial PoC story is now completed, and i'd be happy to talk more about how to design such things20:45
openstackgerritMerged zuul/zuul-jobs master: Fix some item usage where var is zj_* now  https://review.opendev.org/72491620:47
avasswe need to fix that ^20:48
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Use zj_sphinx_pdf instead of item  https://review.opendev.org/72492720:50
avasscorvus, mordred, tristanC: ^20:50
openstackgerritMerged zuul/zuul-jobs master: Distinguish zj_source and zj_result and item  https://review.opendev.org/72492520:52
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491020:54
*** Goneri has joined #zuul21:00
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491021:01
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491021:02
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491021:04
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Use zj_sphinx_pdf instead of item  https://review.opendev.org/72492721:06
avassmordred, corvus, tristanC: ^ had to fix linting21:06
*** guillaumec has quit IRC21:11
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491021:11
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Only run tests for ensure-bazel when it is updated  https://review.opendev.org/72493321:15
openstackgerritMerged zuul/zuul master: Build zuul images with python 3.8  https://review.opendev.org/72490821:17
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491021:21
*** cmurphy has joined #zuul21:21
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491021:26
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: ansible-lint: use matchplay instead of matchtask  https://review.opendev.org/72491022:03
mordredclarkb: could I get you to +A https://review.opendev.org/#/c/722062/1 real quick?22:06
*** klindgren has quit IRC22:07
*** mhu has quit IRC22:07
*** gouthamr has quit IRC22:07
*** evrardjp has quit IRC22:07
*** irclogbot_0 has quit IRC22:07
*** kgz has quit IRC22:07
*** pots has quit IRC22:07
*** toabctl has quit IRC22:07
*** toabctl has joined #zuul22:07
*** evrardjp has joined #zuul22:10
*** pots has joined #zuul22:10
*** klindgren has joined #zuul22:11
avassmordred, clarkb, tristanC, corvus: https://review.opendev.org/#/c/724927/22:11
avasszuul-jobs-maint: ^22:11
*** gouthamr has joined #zuul22:11
*** irclogbot_2 has joined #zuul22:12
openstackgerritJames E. Blair proposed zuul/zuul-registry master: Add a buildkit functional test  https://review.opendev.org/72494222:19
corvusmordred: ^ that's a small step toward improving testing of zuul-registry22:19
corvusthat's just using it as a standard registry; the job normally also tests using it as a buildset registry (ie, with a full mirror config) but i figure we can add that once this works22:20
corvusclarkb: can you +3  https://review.opendev.org/722062 ?22:21
corvusthe HEAD change was stacked on that22:21
mordredcorvus: thanks for the help!22:25
mordredI thnik we might actually be almost actually ready to almost be able to do this22:25
openstackgerritMonty Taylor proposed zuul/zuul-jobs master: Write a buildkitd config file pointing to buildset registry  https://review.opendev.org/72475722:32
mordredcorvus: if that's green (once z-r change lands) - I'm going to squash all three into one change22:32
clarkbcorvus: looking22:45
*** rlandy has quit IRC22:53
openstackgerritMerged zuul/zuul-registry master: Support listing tags  https://review.opendev.org/72206223:01
openstackgerritMerged zuul/zuul-registry master: Support HEAD on manifests  https://review.opendev.org/72485923:01
openstackgerritMerged zuul/zuul-jobs master: Use zj_sphinx_pdf instead of item  https://review.opendev.org/72492723:05
openstackgerritClark Boylan proposed zuul/zuul master: Don't exit zuul-web when signals are received  https://review.opendev.org/72494623:17
clarkbmordred: corvus ^ I think that may fix the sigusr2 + zuul-web thing. That is mostly a reminder to myself for next week whenI can test it a bit more23:17
clarkbcloudnull: just noticed your tripleo container proposal and wanted to mention the Zuul docker image gating stuff thats gone on. You might want to think about incorporating that if you haven't already23:35
clarkbcloudnull: its somewhat orthogonal to your goals but if you are shufflign everythinganyway it might be a good time for it23:36
*** tosky has quit IRC23:45
mordredcloudnull: ++23:54
mordredcloudnull: I'd be happy to help you sort out what that looks like- we've got some extra sexy container tools for you these days23:55

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