Friday, 2021-05-14

*** evrardjp has quit IRC02:33
*** evrardjp has joined #zuul02:33
*** josefwells has quit IRC02:45
*** ykarel has joined #zuul04:44
*** bhavikdbavishi has joined #zuul04:54
*** bhavikdbavishi has quit IRC05:20
*** bhavikdbavishi has joined #zuul05:21
*** ykarel_ has joined #zuul05:36
*** ykarel has quit IRC05:38
*** bhavikdbavishi has quit IRC05:58
*** bhavikdbavishi has joined #zuul06:13
*** bhavikdbavishi1 has joined #zuul06:18
*** bhavikdbavishi has quit IRC06:20
*** bhavikdbavishi1 is now known as bhavikdbavishi06:20
*** bhavikdbavishi has quit IRC06:26
*** bhavikdbavishi has joined #zuul06:27
*** bhavikdbavishi has quit IRC06:39
*** bhavikdbavishi has joined #zuul07:03
*** ykarel_ is now known as ykarel07:12
*** jpena|off is now known as jpena07:30
*** bhavikdbavishi has quit IRC07:32
*** tosky has joined #zuul07:47
*** saneax has joined #zuul07:59
*** sshnaidm|afk is now known as sshnaidm|pto08:00
*** yoctozepto6 is now known as yoctozepto08:03
*** nils has joined #zuul08:22
*** ykarel is now known as ykarel|lunch08:25
*** mgoddard has quit IRC08:43
*** mgoddard has joined #zuul08:43
*** ykarel|lunch is now known as ykarel09:34
openstackgerritLucas Alvares Gomes proposed zuul/zuul-jobs master: [dnm] testing devstack 791085  https://review.opendev.org/c/zuul/zuul-jobs/+/79111709:37
*** jpena is now known as jpena|lunch11:34
*** rlandy has joined #zuul11:49
*** bhavikdbavishi has joined #zuul12:14
*** rlandy is now known as rlandy|training12:14
*** bhavikdbavishi1 has joined #zuul12:19
*** bhavikdbavishi has quit IRC12:21
*** bhavikdbavishi1 is now known as bhavikdbavishi12:21
*** jpena|lunch is now known as jpena12:31
*** Shrews has joined #zuul12:36
*** saneax has quit IRC12:44
*** josefwells has joined #zuul12:51
*** rlandy|training is now known as rlandy13:23
*** bhavikdbavishi has quit IRC13:29
openstackgerritLucas Alvares Gomes proposed zuul/zuul-jobs master: [dnm] testing devstack 791085  https://review.opendev.org/c/zuul/zuul-jobs/+/79111713:39
lyrHey, I tried to use zuul-client (0.0.4) enqueue-ref, error 500, on server side it's missing "trigger". Which was an existing option in "zuul" cli, and zuul-client seems to be missing it13:46
lyrI got zuul from software factory 3.513:48
lyrMaybe it's a change in recent zuul ?13:48
*** Deknos has joined #zuul14:23
*** bhavikdbavishi has joined #zuul14:43
corvuslyr: as of zuul 4.0, the rest api should no longer accept the trigger argument; are you using a new zuul-client with a zuul < 4.0?14:43
lyrI did pip install zuul-client14:43
lyrZuul version: 3.19.1-3.el714:44
corvuslyr: i'm not sure zuul-client ever sent the trigger event, so in other words, i don't think 'zuul-client enqueue-ref' is ever worked before zuul 4.014:45
*** bhavikdbavishi1 has joined #zuul14:45
corvuss/trigger event/trigger parameter/14:46
*** bhavikdbavishi has quit IRC14:47
*** bhavikdbavishi1 is now known as bhavikdbavishi14:47
openstackgerritLucas Alvares Gomes proposed zuul/zuul-jobs master: [dnm] testing devstack 791085  https://review.opendev.org/c/zuul/zuul-jobs/+/79111715:08
*** bhavikdbavishi has quit IRC15:15
corvuszuul-maint: i pushed 4.3.015:28
clarkbcool so that gets us the git dir moves and some of the zk stuff but not the executor changes15:28
corvusyep15:29
corvusand i think the next batch of changes will be easy to roll back -- it's just gear -> zk15:30
corvusso if we mess it up again, a rollback to 430 should be no big deal15:30
*** adpopescu has joined #zuul15:37
*** ykarel has quit IRC15:52
*** jamesmcarthur has joined #zuul15:56
openstackgerritLucas Alvares Gomes proposed zuul/zuul-jobs master: [dnm] testing devstack 791436  https://review.opendev.org/c/zuul/zuul-jobs/+/79111716:11
*** rlandy is now known as rlandy|biab16:25
*** jpena is now known as jpena|off16:28
clarkbcorvus: I think the problem with the zuul executors is that they way you extend yaml's loader to recognize additional objects relies on side effects and to get those side effects you need to import zuul.configloader in any context wishing to have that additional yaml goodness16:42
clarkbcorvus: we get that in our unittest because everything ends up imported, but when you run one of the more specialized daemons this isn't necessarily the case16:42
clarkbcorvus: maybe that pkcs1 YAMLObject should be split into yamlutil and configloader can import it from there and others get it when using yamlutil16:42
clarkb(to be clear I mean the general 'you' here that seems to be the way pyyaml does it and there isn't a more explicit way that might make this more clear)16:46
corvusclarkb: oh nice, that sounds plausible.16:49
corvusclarkb: i think we *can* be more explicit, if we want to; but i think maybe for something like the pkcs thing having it be global is kind of nice.  so maybe we just move that import around.16:50
corvus(er, move the object def into yamlutil as you suggest)16:51
fungiit does seem like a good explanation for why we ran into it where we did and not in testing16:51
clarkbcorvus: ya16:51
corvusi'm going out for a bit; bbl16:51
clarkbcorvus: also note that configloader.py has a couple of other override things that we may need to successfully parse configs elsewhere?16:52
clarkb(I am not sure how much of that gets pushed down to the executors)16:52
corvusclarkb: the others should be only local to configloader16:52
corvusthey're about being able to do the nice error messages; shouldn't matter for the executor16:53
openstackgerritClark Boylan proposed zuul/zuul master: Move encrypted/pkcs1-oaep yaml object handling into yamlutil  https://review.opendev.org/c/zuul/zuul/+/79151416:59
clarkbThat doesn't add any testing, but I figure a good first check is that the move works at all (it should but who knows). Maybe if the trivial move passes testing you can unrevert over the top of it and see what things look like17:00
*** bhavikdbavishi has joined #zuul17:10
*** rlandy|biab is now known as rlandy17:17
*** jamesmcarthur has quit IRC17:34
mordredclarkb: totally seems plausible to me too ... assuming you're right, how do we set up a test to make sure we don't break that in the future?17:42
clarkbmordred: I think maybe leaning on more functional testing that runs services independently of each other? Figuring that out in a unittest context is likely to be fragile and annoying17:43
clarkbjust due to the way python works17:43
mordredyeah17:43
mordredI'm a little sad that the way the yaml extension works is a magic side-effect17:43
clarkbif we do want to go the more unittest like method wht we could do is write a few tests in a corner then run those separately from the main test run17:45
*** jamesmcarthur has joined #zuul17:45
clarkbthat way we can more tightly control what is loaded into the test runner for those tests17:46
clarkbthe tox.ini would end up looking like stestr run all the normal tests && stestr run the pyyaml tests17:46
*** jamesmcarthur_ has joined #zuul17:47
*** jamesmcarthur has quit IRC17:51
*** smyers has quit IRC17:53
fungicould the quickstart job test it effectively?17:54
fungithe services there are quite thoroughly isolated, and not too dissimilar from how we run things in the environment where we encountered the problem17:55
clarkbyup that may work if we pass jobs through it17:56
josefwellscorvus: whats the status on the zuul-operator kopf stuff.. is it worth doing some testing on?17:59
avassjosefwells: I think it's supposed to be ready18:02
avassbut since the stack isn't merged they're still subject to change :)18:02
josefwellsavass: sorry this is my unfamiliarity with gerrit, as it looks like it is on a branch "kopf", but I don't see that branch in the zuul-operator repo.. is there a way to grab that stack of proposed changes easily?18:04
mordredjosefwells: the git review command has an option to download a change18:05
mordredso if you find the last change in the stack (https://review.opendev.org/c/zuul/zuul-operator/+/786349)18:05
mordredyou can go into a zuul checkout and do "git review -d 786349"18:05
mordredand it will download it and put it in to a local branch for you18:06
mordreds/zuul/zuul-operator/18:06
avassyou can also just click the three dots on the top right and download the patch :)18:07
mordredyah - that too18:07
josefwellsmordred: avass: Thanks, I'll see if I can get it going this way18:08
clarkbok my change does not work and results in: "could not determine a constructor for the tag '!encrypted/pkcs1-oaep'" which is maybe good beacuse it is similar to the problem we saw on the executors18:21
openstackgerritClark Boylan proposed zuul/zuul master: Move encrypted/pkcs1-oaep yaml object handling into yamlutil  https://review.opendev.org/c/zuul/zuul/+/79151418:28
clarkbif ^ works better then we have to be very careful about aligning the SafeLoader implementation18:28
mordredisn't there a yamllib api that can be used to explicitly add things to a loader?18:33
clarkbmordred: there is https://pyyaml.org/wiki/PyYAMLDocumentation search Constructors, representers, resolvers18:47
clarkbthats probably a reasonable next step if we can't get this to look sane18:47
mordredyeah- yaml.add_constructor and yaml.add_representer is what I was thinking18:49
*** jamesmcarthur_ has quit IRC18:59
*** Shrews has quit IRC19:00
*** rlandy is now known as rlandy|training19:03
*** smyers has joined #zuul19:09
clarkbthe py38 unittest job has passed on my second patchset. I think there may be two layers of issue here that this exposes. The first is the one I initially brought upwhere you need to import that object to side effect its registration with pyyaml. The other is one of the object attributes is the SafeLoader implementation to apply it against and you need to ensure that you apply it to the load that you19:39
clarkbare going to use everywhere19:39
*** bhavikdbavishi has quit IRC19:41
*** rlandy|training is now known as rlandy20:16
*** ikhan has joined #zuul20:28
*** ikhan has quit IRC20:47
*** adpopescu has quit IRC20:49
*** ikhan has joined #zuul21:00
*** josefwells has quit IRC21:12
*** ikhan has quit IRC21:59
*** ikhan has joined #zuul22:03
*** rlandy has quit IRC22:21
*** ikhan has quit IRC22:21
*** dpawlik has quit IRC22:45
corvusclarkb, mordred: it may be worth switching to the more explicit method.22:47
corvusi have some code for that laying around22:50
*** dpawlik7 has joined #zuul22:53
*** tosky has quit IRC23:11
*** sduthil has quit IRC23:28

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