Monday, 2021-06-07

*** timburke has quit IRC00:00
*** timburke has joined #zuul00:00
*** timburke has quit IRC00:26
*** zenkuro has quit IRC01:37
*** Clark[m] has quit IRC01:40
*** josefwells_ has joined #zuul02:53
*** josefwells has quit IRC03:00
*** josefwells_ has quit IRC03:10
*** mgoddard has quit IRC03:33
*** mgoddard has joined #zuul03:33
*** marios has joined #zuul05:28
*** rpittau|afk is now known as rpittau07:26
*** jpena|off is now known as jpena07:37
*** hashar has joined #zuul08:29
*** sshnaidm|afk is now known as sshnaidm08:51
*** sshnaidm has quit IRC08:58
*** sshnaidm has joined #zuul08:59
*** mhu has joined #zuul09:03
*** bhagyashris__ has joined #zuul09:06
*** bhagyashris_ has quit IRC09:07
*** zenkuro has joined #zuul10:38
*** bhagyashris__ is now known as bhagyashris10:54
tobiash[m]ianw:10:59
tobiash[m]ianw:  commented on ^, otherwise lgtm11:00
*** holser has joined #zuul11:24
*** jpena is now known as jpena|lunch11:34
*** eliadcohen has quit IRC11:47
*** eliadcohen has joined #zuul11:50
*** tosky has joined #zuul11:59
opendevreviewMatthieu Huin proposed zuul/zuul master: Test zuul-client console-stream  https://review.opendev.org/c/zuul/zuul/+/79485412:15
*** josefwells_ has joined #zuul12:19
*** marios is now known as marios|call12:21
*** jpena|lunch is now known as jpena12:21
*** marios|call is now known as marios12:30
opendevreviewMatthieu Huin proposed zuul/zuul master: Test zuul-client console-stream  https://review.opendev.org/c/zuul/zuul/+/79485412:58
opendevreviewFelix Edel proposed zuul/zuul master: WIP: Lock/unlock nodes on executor server  https://review.opendev.org/c/zuul/zuul/+/77461013:13
opendevreviewMatthieu Huin proposed zuul/zuul master: Test zuul-client console-stream  https://review.opendev.org/c/zuul/zuul/+/79485413:18
*** zenkuro has quit IRC13:26
*** zenkuro has joined #zuul13:26
*** Clark[m] has joined #zuul13:32
opendevreviewMatthieu Huin proposed zuul/zuul master: Test zuul-client console-stream  https://review.opendev.org/c/zuul/zuul/+/79485413:59
opendevreviewMohammed Naser proposed zuul/zuul-helm master: Allow overriding image names, tags and pull policy  https://review.opendev.org/c/zuul/zuul-helm/+/79511214:04
*** JohannesFoufas[m] has joined #zuul14:43
JohannesFoufas[m]woah, finally found my way in again14:44
JohannesFoufas[m]anyone knows here we can find Emit stats for semaphore holders?14:45
corvusJohannes Foufas: yep, they should be in gauges.zuul.tenant.<tenant>.semaphore.<semaphore name>.holders14:46
*** zenkuro has quit IRC14:49
*** zenkuro has joined #zuul14:49
JohannesFoufas[m]thank you, I think @vas14:50
JohannesFoufas[m] will debugg, sicne I can not find anything there14:50
opendevreviewMerged zuul/zuul-website master: Use matrix for webchat links  https://review.opendev.org/c/zuul/zuul-website/+/79366814:53
*** timburke has joined #zuul15:00
zenkurohi, is there a way to set a limit to a particular job?15:19
clarkbzenkuro: there are timeouts and you can use labels to limit where jobs run. What sort of limits are you looking for?15:22
fungialso you can limit concurrency with semaphores and/or the serial pipeline manager15:23
zenkuroclarkb: I want to make sure that my job that is running on static machine will not multiple times... since Im planing to use another machine to 'restore from snapshot' the main one15:24
zenkurofungi: thanks, I defiantly need to get familiar with this thing.15:24
corvuszenkuro: sounds like semaphores are what you need15:25
clarkbby default each label should only be used by one job at a time. You could then have a cleanup phase playbook do the restore. Or do that in a prerun15:25
fungizenkuro: zuul will only run one job at a time on each job node anyway, unless you've done something to make it look like multiple nodes15:25
clarkbbut ya also semaphores are useful if you want to break that up across jobs15:25
fungis/node/nodeset/ i mean15:26
corvushttps://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.semaphores and https://zuul-ci.org/docs/zuul/reference/semaphore_def.html15:26
*** timburke has quit IRC15:39
*** timburke has joined #zuul15:40
mnasercorvus: do i remember that you shared helm values/etc for tls zk not-so-long ago?15:45
opendevreviewMatthieu Huin proposed zuul/zuul-client master: Add console-stream subcommand  https://review.opendev.org/c/zuul/zuul-client/+/75123815:46
opendevreviewMatthieu Huin proposed zuul/zuul-client master: Add console-stream subcommand  https://review.opendev.org/c/zuul/zuul-client/+/75123815:49
*** timburke has quit IRC15:53
*** timburke has joined #zuul16:00
*** rpittau is now known as rpittau|afk16:01
*** marios is now known as marios|out16:05
*** zenkuro has quit IRC16:14
corvusmnaser: i switched gerrit's zuul to just plan k8s yaml (because it was easier for a singleton instance to do that); but they're based on the helm charts, so should be easy to incorporate: https://gerrit.googlesource.com/zuul/ops/+/refs/heads/master/k8s/zuul.yaml16:15
mnasercorvus: ok awesome, i'll hack away.. finally doing the tls thing today ;<16:16
corvusmnaser: ++16:16
corvusmnaser: there's also tls support in both the current operator (using zk-ca.sh), and the kopf update (stack ends here: https://review.opendev.org/786349 if you want to look at it, i recommend just checking that out locally); the kopf version uses cert-manager (it's about the same thing as what i did for gerrit).16:18
*** marios|out has quit IRC16:19
avass[m]mnaser: i have a change in zuul-helm that sets up TLS for zookeeper. I don't remember what state it is in though16:20
avass[m]But maybe that helps16:20
mnaseravass[m]: neat, zuul-helm is failing tests so i think i need to unbreak it16:20
avass[m]I think i just did a code dump from our charts :)16:21
opendevreviewMatthieu Huin proposed zuul/zuul master: Test zuul-client console-stream  https://review.opendev.org/c/zuul/zuul/+/79485416:30
*** jpena is now known as jpena|off16:40
opendevreviewAde Lee proposed zuul/zuul-jobs master: Add role to enable FIPS on a node  https://review.opendev.org/c/zuul/zuul-jobs/+/78877817:47
*** timburke_ has joined #zuul17:50
*** timburke has quit IRC17:56
clarkbif anyone has time for a review https://review.opendev.org/c/zuul/zuul/+/794878 is a small cleanup that I did after getting local test runs going again17:56
*** timburke_ has quit IRC18:17
*** timburke_ has joined #zuul18:28
*** spamaps[m] has joined #zuul19:24
*** spamaps[m] has left #zuul19:25
*** jangutter_ has quit IRC19:33
clarkbcorvus tobiash[m] I don't see benjamin in here but https://review.opendev.org/c/zuul/zuul/+/788481 lgtm.  Idid leave a couple of thoughts though20:39
clarkbsimilar situation on https://review.opendev.org/c/zuul/zuul/+/663413. Both lgtm but I had a couple of ideas20:53
corvusclarkb: i replied on the first one20:53
clarkbthanks, and ya I agree re picking a behavior.21:00
clarkbIt wasn't clear to me from the spec which behaviors we wanted though21:00
corvusclarkb: ++ and also replied on the 2nd21:01
clarkbwfm thanks21:02
clarkbianw: I responded to your comments on https://review.opendev.org/c/zuul/zuul/+/794371 can you take a look and check that I'm making sense?21:10
opendevreviewMerged zuul/zuul master: Cleanup Zuul's stdout/stderr output  https://review.opendev.org/c/zuul/zuul/+/79487821:18
*** hashar has quit IRC21:40
*** zenkuro has joined #zuul21:41
opendevreviewMatthieu Huin proposed zuul/zuul master: Test zuul-client console-stream  https://review.opendev.org/c/zuul/zuul/+/79485421:50
ianwclarkb: i can put a >200 <300 in if you feel strongly.  I can't find any documentation on the return codes, I suspect because we're doing queries here we shouldn't get things like created etc.21:59
clarkbianw: ya that is probably the case. In my head I guess it was to help avoid problems like the one we have today where it mysteriously doesn't work ebcause we're either filtering too little or too much21:59
clarkbif you want to just go with 200 for now and address and api weirdness later should it show up I'm ok with that too I guess22:00
*** tosky has quit IRC22:04
opendevreviewMatthieu Huin proposed zuul/zuul master: Test zuul-client console-stream  https://review.opendev.org/c/zuul/zuul/+/79485422:34
opendevreviewJames E. Blair proposed zuul/zuul master: Fix layout cache and adding a project to a pipeline  https://review.opendev.org/c/zuul/zuul/+/79518923:07
opendevreviewJames E. Blair proposed zuul/zuul master: Fix reporting merge failure behind change adding ppc  https://review.opendev.org/c/zuul/zuul/+/79519023:07
mhucorvus, guillaumec I'm having a bit of trouble testing the console stream with zuul-client in https://review.opendev.org/79485423:10
mhuin the latest build I can see that zuul-web can't maintain the websocket connection with zuul-client apparently, but no idea why https://d29e095404ca86d71246-7daaa7daeb1030fb2122101d5d422feb.ssl.cf2.rackcdn.com/794854/14/check/zuul-tox-zuul-client/9da7d02/testr_results.html23:11
mhuAny ideas why?23:12
clarkbcorvus: why does the test job run by the new test in https://review.opendev.org/c/zuul/zuul/+/795189/1/tests/unit/test_v3.py fail?23:36
clarkblooks like its playbook just runs an empty task list23:36
corvusclarkb: search for "failJob"23:37
corvus(artificially induced failure)23:38
clarkboh that is an externally induced side effect23:38
corvusclarkb: yep; that test class doesn't actually run ansible23:38
corvus(still needs a playbook to make zuul happy though; but contents don't matter)23:39
clarkbgotcha23:40

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