Thursday, 2022-06-30

-@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 847646: Fix merging with submitWholeTopic https://review.opendev.org/c/zuul/zuul/+/84764606:45
-@gerrit:opendev.org- Dmitriy Rabotyagov proposed on behalf of Denys Mishchenko: [zuul/nodepool] 842913: Fix for post_upload_hook failure. id missing https://review.opendev.org/c/zuul/nodepool/+/84291307:40
-@gerrit:opendev.org- Simon Westphahl proposed: [zuul/zuul] 848234: Fix read-only branches error in zuul-web https://review.opendev.org/c/zuul/zuul/+/84823409:04
-@gerrit:opendev.org- Matthieu Huin https://matrix.to/#/@mhuin:matrix.org proposed: [zuul/zuul] 848093: zuul-web: raise 404s when tenant isn't found https://review.opendev.org/c/zuul/zuul/+/84809310:07
-@gerrit:opendev.org- Simon Westphahl proposed: [zuul/zuul] 848234: Fix read-only branches error in zuul-web https://review.opendev.org/c/zuul/zuul/+/84823411:30
-@gerrit:opendev.org- Matthieu Huin https://matrix.to/#/@mhuin:matrix.org proposed: [zuul/zuul] 848132: zuul-web: return errors as JSON https://review.opendev.org/c/zuul/zuul/+/84813213:36
@vlotorev:matrix.orgHi, could zuul-maint have a look at https://review.opendev.org/c/zuul/zuul/+/844742? It already has one CR+2.14:05
-@gerrit:opendev.org- Matthieu Huin https://matrix.to/#/@mhuin:matrix.org proposed: [zuul/zuul] 848132: zuul-web: return errors as JSON https://review.opendev.org/c/zuul/zuul/+/84813214:07
@jim:acmegating.comvlotorev: i think your change is fine -- but https://review.opendev.org/842290 from mhu will need a rebase after it lands (but it needs a release note added anyway, so that's not a big deal)14:42
@mhuin:matrix.org> <@jim:acmegating.com> vlotorev: i think your change is fine -- but https://review.opendev.org/842290 from mhu will need a rebase after it lands (but it needs a release note added anyway, so that's not a big deal)14:45
yeah the rebase is fine, np. Do keep in mind though that the REST commands in the zuul admin CLI are deprecated, so I think we should limit changes related to that
@mhuin:matrix.orgHowever this is a minor QoL change so I don't see why we shouldn't have it14:46
@mhuin:matrix.orgBTW is there a target window for the next zuul release?14:47
@jim:acmegating.comnot yet14:53
@mhuin:matrix.orgokay good, I can relax about that then 🙂14:54
@vlotorev:matrix.orgcorvus: mhu: thanks.15:17
@clarkb:matrix.orgtristanC: is the failed_when: false from https://review.opendev.org/c/zuul/zuul-operator/+/847846/2/playbooks/zuul-operator-functional/test.yaml#170 leftover from debugging?17:42
@tristanc_:matrix.orgClark: this task is expected to fail, the real test happens in the following tasks17:44
@clarkb:matrix.orgwhy does wsdump fail? I guess that aspect of the change wasn't clear from the commit message. The commit message says the echo is there to fix it but its still returning non zero?17:45
@tristanc_:matrix.orgClark: if i recall correctly, the command may error because of EOF. Though it's fine, what matter is that its output contains the expected console log17:46
@clarkb:matrix.orgNote the task in the job that ran for that ps had an rc of 017:47
@clarkb:matrix.orgok17:47
@clarkb:matrix.orgtristanC: in https://review.opendev.org/c/zuul/zuul-operator/+/845851/19/deploy/crds/zuul-ci_v1alpha2_zuul_cr.yaml why is the database section commented out? Is that meant to be an example?18:04
@clarkb:matrix.orgleft a couple of questions on that chagne18:12
-@gerrit:opendev.org- Zuul merged on behalf of Tristan Cacqueray: [zuul/zuul-operator] 847846: Pin pykube-ng and fix the CI https://review.opendev.org/c/zuul/zuul-operator/+/84784618:21
-@gerrit:opendev.org- Zuul merged on behalf of Albin Vass: [zuul/zuul-operator] 800265: Gracefully shutdown executor on SIGTERM https://review.opendev.org/c/zuul/zuul-operator/+/80026518:21
-@gerrit:opendev.org- Zuul merged on behalf of Tristan Cacqueray: [zuul/zuul-operator] 847978: Remove gearman configuration https://review.opendev.org/c/zuul/zuul-operator/+/84797818:30
-@gerrit:opendev.org- Zuul merged on behalf of Tristan Cacqueray: [zuul/zuul-operator] 847809: Remove CONTRIBUTE.md documentation https://review.opendev.org/c/zuul/zuul-operator/+/84780918:31
-@gerrit:opendev.org- Tristan Cacqueray proposed: [zuul/zuul-operator] 845851: Update CRD apiVersion to v1 (from v1beta) https://review.opendev.org/c/zuul/zuul-operator/+/84585118:46
-@gerrit:opendev.org- Clark Boylan proposed: [zuul/nodepool] 848331: Add python3.10 testing https://review.opendev.org/c/zuul/nodepool/+/84833119:09
-@gerrit:opendev.org- Clark Boylan proposed: [zuul/nodepool] 848331: Add python3.10 testing https://review.opendev.org/c/zuul/nodepool/+/84833119:33
-@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com:19:46
- [zuul/zuul] 845284: Clarify missing merge requirement message https://review.opendev.org/c/zuul/zuul/+/845284
- [zuul/zuul] 846232: Improve gerrit connection event queue logging https://review.opendev.org/c/zuul/zuul/+/846232
@clarkb:matrix.orgcorvus: https://review.opendev.org/c/zuul/zuul/+/837063 is a straightforward one that I thought I'd call out due to small linkage to the comment work for circular deps/same topic merges20:06
@clarkb:matrix.orgI didn't approve it to give you a cahnce to look at it if you want, but I'll probably approve later today20:07
@jim:acmegating.comClark: i have previously reviewed that -- thanks for the reminder20:34
@jim:acmegating.comClark: but what do you mean the "comment work"?20:37
@clarkb:matrix.orgcorvus: the multi phase reporting20:37
@clarkb:matrix.orgthey are both interacting with the "make a comment in code review system" portion fo the code but should be doing so in non interferring ways20:38
@jim:acmegating.comClark: i agree; i don't think the two-phase reporting should cause any problems, so i wall approve that change (gate will tell us if i'm wrong)20:40
@jim:acmegating.com * Clark: i agree; i don't think the two-phase reporting should cause any problems, so i will approve that change (gate will tell us if i'm wrong)20:40
@jim:acmegating.com(and it looks like my earlier comments are addressed)20:40
-@gerrit:opendev.org- Thiago Paiva Brito proposed: [zuul/zuul-jobs] 848334: Remove zuul_work_dir from role https://review.opendev.org/c/zuul/zuul-jobs/+/84833420:44
-@gerrit:opendev.org- Thiago Paiva Brito proposed: [zuul/zuul-jobs] 848334: Remove zuul_work_dir from role https://review.opendev.org/c/zuul/zuul-jobs/+/84833421:01
-@gerrit:opendev.org- Clark Boylan proposed: [zuul/nodepool] 848331: Add python3.10 testing https://review.opendev.org/c/zuul/nodepool/+/84833121:15
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 848337: Include user/driver data in node detail list https://review.opendev.org/c/zuul/nodepool/+/84833721:32
-@gerrit:opendev.org- Thiago Paiva Brito proposed: [zuul/zuul-jobs] 848339: Adding git commit message guidelines check https://review.opendev.org/c/zuul/zuul-jobs/+/84833922:08
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 848341: Fix race in test_aws_resource_cleanup https://review.opendev.org/c/zuul/nodepool/+/84834122:24
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 848337: Include user/driver data in node detail list https://review.opendev.org/c/zuul/nodepool/+/84833722:25
@clarkb:matrix.orgcorvus: does the last bit in https://review.opendev.org/c/zuul/zuul/+/846055/1/releasenotes/notes/dependency-validation-000f63204da83b4a.yaml mean that you'd have to correct these problems before being able to (re)start zuul?22:27
@jim:acmegating.comClark: they would turn into config errors.  i actually don't think it would even change the layout (ie, the project-pipeline stanza will still be there and include the job).  but the error list would be one entry longer and have the reference exception.22:34
@clarkb:matrix.orggot it22:34
@jim:acmegating.comClark: i'd like you to double check me on that though22:34
@jim:acmegating.combecause i thought something different this morning22:35
@jim:acmegating.comClark: my thinking is this is the crux: https://opendev.org/zuul/zuul/src/branch/master/zuul/configloader.py#L2398-L240122:36
@clarkb:matrix.orgit should raise an exception there which will bubble up through to TenantParser.fromYaml()?22:36
@clarkb:matrix.orgI guess that is why I'm concerned because it isn't clear to me how far an exception can go and the initial config loading survive?22:36
@jim:acmegating.combut https://opendev.org/zuul/zuul/src/branch/master/zuul/configloader.py#L2400 should catch it22:36
@clarkb:matrix.orgoh yup I missed that because it wasn'y a try except22:37
@clarkb:matrix.orgI should pay more attention22:37
@clarkb:matrix.orgso ya it won't bubble all the way up and the rest of the layout parsing will continue22:37
@jim:acmegating.comi mean i was wrong about this this morning... :)  22:38
@clarkb:matrix.orgok ya I think this will do what you describe.22:38
@jim:acmegating.comand https://opendev.org/zuul/zuul/src/branch/master/zuul/model.py#L7076 is a bare Exception22:38
@jim:acmegating.comand that's what we should be raising22:38
@clarkb:matrix.orgIf it was a ConfigurationSyntaxError then my concern would be a problem22:38
@jim:acmegating.comright22:38
@jim:acmegating.combut https://opendev.org/zuul/zuul/src/branch/master/zuul/configloader.py#L334 catches bare Exceptions and accumulates only without reraising22:39
@clarkb:matrix.orgThis would be an AttributeError or similar which the bare exception catch should handle22:39
@jim:acmegating.comwell in the case of the missing job (my favorite conan doyle story), we explicitly raise an Exception() at https://opendev.org/zuul/zuul/src/branch/master/zuul/model.py#L707622:41
@clarkb:matrix.orgAh ok. But ya in that case this should be "fine". It will be a new error but not change behavior for end users or operators really. Zuul can still be restarted and you'll get a new entry under the blue error bell22:41
@clarkb:matrix.orgrather than jobs that just fail to run22:42
@jim:acmegating.comyep.22:42
@clarkb:matrix.orgok I'm going to approve it22:42
@clarkb:matrix.orghttps://review.opendev.org/c/zuul/zuul/+/848137 is another small bugfix I'm going to approve22:42
@clarkb:matrix.orghrm actually I may need to think about this one twice too :)22:43
@clarkb:matrix.orggetBlobKeys() is used to get the live blobs that we don't want to delete.22:43
@clarkb:matrix.orgThe old behavior here is an exception which would've stopped us from deleting anything (and wait until alter to do the deletes safely)22:44
@clarkb:matrix.orgis it possible that when we return set() there we'd end up with a short live blobs set and delete things we shouldn't and the exception is actually desireable?22:44
@jim:acmegating.comClark: i *think* the stuff in scheduler.py that gets a starting ltime for the start of the cleanup should mean that any blobs that are in the process of being created should be excluded from cleanup even if that's a short set.22:46
@clarkb:matrix.org`unused_blobs = blobstore.getKeysLastUsedBefore(start_ltime)` that bit?22:47
@jim:acmegating.comyeah... but i'm a little less sure about that now... maybe it's possible to start creating a blob after that and then hit this case...22:48
@jim:acmegating.comoh we hold the pipeline lock!22:49
@jim:acmegating.comso nothing should be being created while we hold the lock22:49
@jim:acmegating.comso i think the combo of starting ltime, then holding the pipeline lock so that when we get the live blob keys we know it's stable means that we should be good22:50
@jim:acmegating.combasically, either getBlobKeys will work as originally intended, or, if we hit that exception, then there really is nothing there (ie, nothing is in the process of being created)22:51
@clarkb:matrix.organd start_ltime is from before we hold the lock so we're looking at everything created before the lock is held anyway22:51
@jim:acmegating.comyep22:51
@clarkb:matrix.orgya so nothing new should be evaluated22:51
@clarkb:matrix.orgok ya that should make it safe to return an empty set there22:51
@clarkb:matrix.organd in that case we'll clean up blobs more quickly and not need to occasionally avoid the exception to claen things up22:52
@clarkb:matrix.orgcorvus: did you want to rereview https://review.opendev.org/c/zuul/zuul/+/735475?22:53
@clarkb:matrix.orghttps://review.opendev.org/c/zuul/zuul/+/817393 too though that one you reviewed far less recently22:53
@jim:acmegating.comdone and done, thx22:55
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 848344: Include backing node request id in metastatic log https://review.opendev.org/c/zuul/nodepool/+/84834423:07
@iwienand:matrix.orgdoes anyone have a problem with the dib bump in https://review.opendev.org/c/zuul/nodepool/+/847698 so we can get fresh containers?23:10
-@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/nodepool] 846432: AWS driver create/delete improvements https://review.opendev.org/c/zuul/nodepool/+/84643223:24
@clarkb:matrix.orgswest: left some questions on https://review.opendev.org/c/zuul/zuul/+/84823423:27
@clarkb:matrix.org> <@iwienand:matrix.org> does anyone have a problem with the dib bump in https://review.opendev.org/c/zuul/nodepool/+/847698 so we can get fresh containers?23:27
No objections here. Approved
@jim:acmegating.comianw: https://review.opendev.org/848341 is a fix to the fix we were working on recently23:31
@iwienand:matrix.orgoh right; will context switch that back in a few 23:32
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/nodepool] 848172: AWS multi quota support https://review.opendev.org/c/zuul/nodepool/+/84817223:41
-@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 846449: Add extra validation to dynamic-only projects https://review.opendev.org/c/zuul/zuul/+/84644923:58

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