Friday, 2020-10-02

*** stevthedev has joined #zuul00:05
openstackgerritMerged zuul/zuul master: Update Gerrit config for quickstart  https://review.opendev.org/75566900:16
*** hamalq has quit IRC00:16
openstackgerritMerged zuul/zuul-jobs master: Fix certificate issue with use buildset registry  https://review.opendev.org/74158400:26
openstackgerritMerged zuul/zuul master: Revert "Revert "Update images to use python 3.8""  https://review.opendev.org/75567100:31
*** freenzyfriday has joined #zuul00:35
*** freenzyfriday has quit IRC00:39
*** weshay|ruck has quit IRC00:54
*** weshay has joined #zuul00:55
*** weshay is now known as weshay|ruck00:55
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Disable broken fetch-sphinx-tarball test job"  https://review.opendev.org/75319903:16
*** stevthedev has quit IRC03:21
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Disable broken fetch-sphinx-tarball test job"  https://review.opendev.org/75319903:28
*** bhavikdbavishi has joined #zuul03:30
*** bhavikdbavishi1 has joined #zuul03:33
*** bhavikdbavishi has quit IRC03:34
*** bhavikdbavishi1 is now known as bhavikdbavishi03:34
*** stevthedev has joined #zuul03:49
*** freenzyfriday has joined #zuul04:15
*** bhavikdbavishi has quit IRC04:25
*** bhavikdbavishi has joined #zuul04:26
*** evrardjp has quit IRC04:33
*** evrardjp has joined #zuul04:33
*** freenzyfriday has quit IRC04:36
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Revert "Disable broken fetch-sphinx-tarball test job"  https://review.opendev.org/75319904:59
*** bhavikdbavishi has quit IRC05:00
*** bhavikdbavishi has joined #zuul05:00
*** bhavikdbavishi has quit IRC05:23
openstackgerritJan Kubovy proposed zuul/zuul master: Merge Zookeeper connection methods and specialize exceptions  https://review.opendev.org/75436005:24
*** holser has joined #zuul05:24
*** holser has quit IRC05:25
*** holser has joined #zuul05:27
*** hamalq has joined #zuul06:12
*** holser has quit IRC06:21
*** jcapitao has joined #zuul07:00
*** bhavikdbavishi has joined #zuul07:02
*** yolanda has quit IRC07:04
*** yolanda has joined #zuul07:04
*** hamalq has quit IRC07:13
*** bhavikdbavishi has quit IRC07:17
*** bhavikdbavishi has joined #zuul07:17
openstackgerritJan Kubovy proposed zuul/zuul master: Separate connection registries in tests  https://review.opendev.org/71295807:31
openstackgerritJan Kubovy proposed zuul/zuul master: Prepare Zookeeper for scale-out scheduler  https://review.opendev.org/71726907:31
openstackgerritJan Kubovy proposed zuul/zuul master: Mandatory Zookeeper connection for ZuulWeb in tests  https://review.opendev.org/72125407:31
openstackgerritJan Kubovy proposed zuul/zuul master: Driver event ingestion  https://review.opendev.org/71729907:31
openstackgerritJan Kubovy proposed zuul/zuul master: Connect merger to Zookeeper  https://review.opendev.org/71622107:31
openstackgerritJan Kubovy proposed zuul/zuul master: Connect fingergw to Zookeeper  https://review.opendev.org/71687507:31
openstackgerritJan Kubovy proposed zuul/zuul master: Connect executor to Zookeeper  https://review.opendev.org/71626207:31
openstackgerritJan Kubovy proposed zuul/zuul master: Improve typings in context of 744416  https://review.opendev.org/75357807:31
openstackgerritJan Kubovy proposed zuul/zuul master: Merge Zookeeper connection methods and prepare test zookeeper  https://review.opendev.org/75436007:31
openstackgerritJan Kubovy proposed zuul/zuul master: Switch to using zookeeper instead of gearman for jobs  https://review.opendev.org/74441607:31
*** bhavikdbavishi1 has joined #zuul07:43
*** tosky has joined #zuul07:43
*** bhavikdbavishi has quit IRC07:44
*** bhavikdbavishi1 is now known as bhavikdbavishi07:44
*** bhavikdbavishi has quit IRC07:51
*** jpena|off is now known as jpena07:57
*** hashar has joined #zuul07:58
*** holser has joined #zuul07:59
*** armstrongs has joined #zuul08:15
*** armstrongs has quit IRC08:24
openstackgerritzbr proposed zuul/zuul-jobs master: ensure-docker: validate  network connectivity  https://review.opendev.org/75550508:27
openstackgerritzbr proposed zuul/zuul-jobs master: ensure-docker: validate network connectivity  https://review.opendev.org/75550508:32
*** jfoufas1 has joined #zuul08:39
*** bhavikdbavishi has joined #zuul08:44
*** bhavikdbavishi1 has joined #zuul08:49
*** bhavikdbavishi has quit IRC08:51
*** bhavikdbavishi1 is now known as bhavikdbavishi08:51
avasssomething strange is going on with our executor running in eks. it doesn't seem possible to pause it since it keeps running jobs even though it's reporting that it's paused to statsd09:43
avassfor some reason this only happens in kubernetes09:43
tobiashavass: could it be that it already was disabled by a governor?10:06
tobiashavass: I've saw occurrences that pause while it's unregistered fails due to double unregister and then it went into a weird state10:07
tobiashbut hadn't time to fix it yet10:08
tobiashavass: e.g. this is a double pause attempt: http://paste.openstack.org/show/798640/10:10
tobiashmaybe you find a similar stack trace10:10
avasstobiash: I'll see if I can find something. paused_on_startup doesn't seem to work either10:21
avasstobiash: we're still on 3.19 though since we've been slow to set up zookeeper tls10:22
tobiashavass: I think that part didn't change since then10:24
openstackgerritzbr proposed zuul/zuul-jobs master: ensure-docker: validate network connectivity  https://review.opendev.org/75550510:35
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Consolidate common log upload code into module_utils  https://review.opendev.org/74273610:39
openstackgerritTobias Henkel proposed zuul/zuul-jobs master: Consolidate common log upload code into module_utils  https://review.opendev.org/74273610:40
*** holser has quit IRC10:40
tobiashAJaeger, ianw: I think that should address your comments ^10:41
avasstobiash: looks like it's logging that the executor is starting in paused mode but then starts jobs anyway: http://paste.openstack.org/show/798642/10:46
tobiashlooks like it's refistering  regardless of pause at startup10:47
tobiashwhat happens if you execute zuul-executor pause inside the pod?10:47
*** holser has joined #zuul10:48
avasstobiash: http://paste.openstack.org/show/798643/10:50
avasstobiash: looks like it works this time10:52
avasstobiash: only difference is that it's using the default logconfig instead of outputting it in a json format. maybe that's causing some kind of problem10:53
avasstobiash: actually no, it keeps starting jobs10:57
tobiashthat's weird, if it really unregistered that should not be possible10:57
tobiashoh wait10:58
tobiashit only paused the merge worker, not the executor worker10:58
tobiashis there no exception or so?10:58
avassnope10:58
tobiashmaybe just the log is misleading10:59
tobiashcan you check gear's function list?10:59
avasshow do I do that?11:00
tobiashhttps://zuul-ci.org/docs/zuul/howtos/troubleshooting.html11:01
tobiashyou can connect to gearman using openssl and enter status11:01
avassah :)11:01
tobiashthen it prints all registered functions and queue lengths11:02
*** bhavikdbavishi has quit IRC11:06
avasstobiash: anything specific I'm looking for?11:07
tobiashthe execute functions11:07
*** jcapitao is now known as jcapitao_lunch11:09
zbris anyway aware that task summary counters for failed do not match what console display? you may have failed tasks but it is always 011:09
zbrexample at https://zuul.opendev.org/t/zuul/build/262bad816e954d4394ddaf0b5bfe7aac11:10
avasstobiash: for that specific executor it looks like this: http://paste.openstack.org/show/798644/11:11
tobiashavass: resume and stop are always there11:11
tobiashexecute doesn't have the executor name in the function name11:12
avasstobiash: just saw it you mean this right: "executor:execute 47 47 6"?11:12
tobiashyes11:12
tobiashjudging from the counts that's not a test env right?11:12
openstackgerritMerged zuul/zuul master: Optimize GitHub requests on PR merge  https://review.opendev.org/75288611:12
avassnope11:13
tobiashcan you get a list of all that starts with 'executor:'?11:13
tobiashor better compare the number of execute functions with the number of running executors11:16
*** jfoufas1 has quit IRC11:17
avasstobiash: there are more functions than running executors, but only six that is registered as available workers11:18
tobiashI think I've found a race when pausing11:18
tobiashpausing is implemented as a pause sensor of the normal governor11:19
tobiashsee the manageLoad function11:19
tobiashthat is called either after accepting a job or every 10 seconds11:19
tobiashso if you pause the executor there might be 10 seconds in which it can take additional jobs before it really unregisters11:20
avasstobiash: and self.register_work sets self.accepting_work = True11:21
avasstobiash: I'm guessing the reregister = True should not be there11:22
openstackgerritTobias Henkel proposed zuul/zuul master: Call manageLoad during pause and unpause  https://review.opendev.org/75576511:23
avasstobiash: oh actually I take that back11:23
tobiashI think that should fix it ^11:23
avassyeah I have to go through that to understand how it fits together11:24
tobiashavass: can you verify that after pausing it at least stops accepting jobs after 10+ seconds?11:24
avasstobiash: it doesn't :)11:24
tobiashthat is weird then11:25
tobiashI have another idea then11:25
bolgzuul-main: can I ask for a review on https://review.opendev.org/c/744416 and the rest of the branch (topic: scale-out-scheduler). Current comments were worked in.11:26
bolgzuul-maint: ^^^11:26
tobiashavass: you might have a deadlock of the governor here: https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L300811:26
tobiashthat would block the governor completely11:26
tobiashavass: do you have 'Unregistering due to' or 'Re-registering as job is within its limits' messages in your logs?11:27
tobiashavass: a thread dump (kill -SIGINT2) coud help to prove this theory. If the theory is right, you'll have a thread hanging in one of the sensors (zuul.executor.sensor.* packages)11:28
tobiashs/SIGINT2/SIGUSR211:29
avasstobiash: no such logs11:30
tobiashsome of those query some system metrics which makes that plausible as you said it's only on eks11:30
tobiashavass: so that further backs the hanging thread hypothesis11:31
tobiashavass: so the thread dumo should be the next step11:31
*** jpena is now known as jpena|lunch11:36
openstackgerritGuillaume Chauvel proposed zuul/zuul master: tutorial: Rework quick-start and prepare for other tutorials  https://review.opendev.org/73206611:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: tutorial: Add "gate your first patch"  https://review.opendev.org/73206711:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: tutorial: Add "Use zuul jobs"  https://review.opendev.org/73206811:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: tutorial: Add "gate pipeline"  https://review.opendev.org/73206911:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: tutorial: Add "job secrets"  https://review.opendev.org/73207011:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: tutorial: Add "job dependencies"  https://review.opendev.org/73207111:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: Rename quick-start to zuul-tutorial-quick-start  https://review.opendev.org/73765611:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: [DNM] TEST run zuul tutorials to test stream+callback (+ zuul-jobs change)  https://review.opendev.org/73547711:40
openstackgerritGuillaume Chauvel proposed zuul/zuul master: [DNM] Test: run multiple tutorials ('job dependencies' 2 times)  https://review.opendev.org/74155811:40
avasstobiash: SIGINT or SIGUSR2?11:43
tobiashSIGUSR211:43
tobiashsorry, typo ;)11:43
avasstobiash: oh, missed the next line :)11:43
*** jfoufas1 has joined #zuul11:46
*** sshnaidm is now known as sshnaidm|afk11:46
avasswell, I get a ton of exceptions doing that11:47
*** iurygregory has quit IRC11:55
tobiashthat are no exceptions, that is a complete thread dump11:55
tobiashcan you paste it?11:56
avassah yeah I just realized that11:56
*** jcapitao_lunch is now known as jcapitao11:56
*** iurygregory has joined #zuul11:57
avasstobiash: yeah, one second11:58
*** rfolco has joined #zuul11:58
avasstobiash: http://paste.openstack.org/show/798645/12:01
*** rlandy has joined #zuul12:07
*** rlandy is now known as rlandy|rover12:07
*** mattd01 has joined #zuul12:09
tobiashhrm, I don't see anything unusual12:09
tobiashand the governor thread seems to be in its normal 10s wait12:10
tobiashavass: when I pause I get this after latest 10s: zuul.ExecutorServer: Unregistering due to paused12:16
avassis there any way the executor can reach the state accepting_work = false and any sensor = false after having registered?12:16
tobiashaccepting_work is only written un (un)register_work12:17
tobiashand those are only used in _manageLoad12:18
avasshmm12:18
*** jpena|lunch is now known as jpena12:30
*** Goneri has joined #zuul13:13
*** hashar has quit IRC13:25
*** hashar has joined #zuul13:55
*** jfoufas1 has quit IRC13:57
openstackgerritzbr proposed zuul/zuul-jobs master: ensure-docker: validate network connectivity  https://review.opendev.org/75550514:04
*** holser has quit IRC14:09
*** holser has joined #zuul14:12
zbravass: ianw tristanC: please recheck ^ is now ready.14:33
*** Eighth_Doctor has quit IRC14:33
*** stevthedev_ has joined #zuul14:38
*** stevthedev has quit IRC14:40
*** stevthedev_ is now known as stevthedev14:40
*** Eighth_Doctor has joined #zuul14:48
logan-Hello! My github connection broke today and I was wondering if it is related to https://developer.github.com/changes/2020-04-15-replacing-create-installation-access-token-endpoint/. I am running 3.19 and confirmed I've got the fix https://opendev.org/zuul/zuul/commit/ea97b9f2e829331b0af0a6f0904cba691628c1f5 in my running env. Log output looks like15:36
logan-http://paste.openstack.org/raw/798652/15:36
mhuHello zuul-maint, the encrypt subcommand in zuul-client is go: https://review.opendev.org/#/q/topic:zuul-client_encrypt+(status:open) if you're okay with the changes, let's +3 them15:37
tobiashlogan-: can you enable debug logs to see if there is more info?15:40
logan-tobiash: Oh whoops. I thought I had debugging enabled but I was mistaken, getting updated logs gathered.15:47
logan-w/ debug enabled: http://paste.openstack.org/raw/798655/15:53
tobiashlogan-: you get 403 when requesting check runs16:02
tobiashyou probably need to add check run permissions to the zuul github app16:02
fungihe's the third person to report what looks like permission issues from the recent gh driver change, i wonder if we need an additional reminder of perms required in the release notes?16:06
logan-Ah yes, that was it. Thank you!16:07
tobiashat least there is https://zuul-ci.org/docs/zuul/reference/releasenotes.html#relnotes-3-17-0-new-features but it seems that somewhere in between it got required16:09
fungiis the sudden requirement on github's side or something we changed then?16:12
tobiashI think it might be a side effect of an optimization16:13
logan-Yep it happened between 3.18 -> 3.19. I upgraded to 3.19 to pull in the fix for that access token endpoint change and thats when the checks permission broke.16:13
fungiso maybe an unintended regression16:13
openstackgerritzbr proposed zuul/zuul-jobs master: Update ensure-docker for new releases  https://review.opendev.org/75263016:13
tobiashshould we amend a release note of 3.19 to add that as an upgrade notice?16:13
tobiashI think that would appear at the correct version right?16:14
fungii'm not familiar enough with reno to know for sure if it's possible to alter release notes after the tag, but i think you can. seems like it just cares when the note identifier appeared in the history, not what the state of the file for it was in at that time16:15
logan-Yes imo. I read the release notes for 3.19 so it would have avoided my ping at least. :)16:15
tobiashfungi: afaik we did this already in the past16:15
openstackgerritTobias Henkel proposed zuul/zuul master: Add upgrade note to 3.19 regarding check run permissions  https://review.opendev.org/75584216:22
tobiashfungi, logan- ^16:22
openstackgerritTobias Henkel proposed zuul/zuul master: Add upgrade note to 3.19 regarding check run permissions  https://review.opendev.org/75584216:24
*** hashar has quit IRC16:28
zbrtobiash: fungi https://review.opendev.org/#/c/748480/ please.16:42
tobiashfungi: I've responded to your comment16:45
fungithanks16:47
*** hamalq has joined #zuul16:58
fungicorvus: so we got some clarification on the ansiblefest virtual booth features... our package comes with private attendee/sponsor chat capability, just not a general booth group chat/message board17:00
fungiso it is still synchronous17:01
fungialso clunky and confusing that they have two entirely separate text chat mechanisms integrated17:05
*** mattd01 has quit IRC17:06
openstackgerritMerged zuul/zuul-jobs master: Partial address ansible-lint E208  https://review.opendev.org/74848017:18
*** jpena is now known as jpena|off17:20
*** holser has quit IRC17:27
corvustobiash: +317:54
*** jcapitao has quit IRC17:55
zbrtwo more on ensure-docker: https://review.opendev.org/#/q/topic:ensure-docker+(status:open+OR+status:merged)17:56
corvusfungi: i'm not sure i fully understand who can chat with who in that situation; can you explain with more words?  (are you saying an attendee can privately chat with "zuul"?  or are you saying that fungi, as an attendee who is also a sponsor, is able to chat with other attendees?)17:57
fungicorvus: the attendees can privately chat with the booth sponsor staffers in real time to ask questions, et cetera17:58
fungithat's a base feature which is included in our sponsor package apparently17:59
fungithere's a separate chat feature which allows booth attendees to leave persistent messages in real time and potentially talk to each other as well as the sponsor booth staffers, and that is not included in our package18:00
*** mattd01 has joined #zuul18:01
corvusok.  what we have sounds moderately useful then18:01
fungithe staffers can also invite other specific attendees into the same private chat the attendee initiates apparently (if i fully understood the demo they showed us), but it's not just a wide open anybody can wander into the same chat space thing18:02
*** hashar has joined #zuul18:43
openstackgerritJames E. Blair proposed zuul/zuul master: Add CORS header to quickstart log server config  https://review.opendev.org/75586418:44
corvusfungi, clarkb, tobiash: ^ got 99% through recording the zuul talk and hit that18:44
corvusthe good news is that i think our quickstart test job is doing a pretty good job of keeping things from bit-rotting.18:45
corvusthe 2 things that did bitrot are relatively minor annoyances, and would be pretty hard to test18:46
fungioof18:49
openstackgerritMerged zuul/zuul master: Add upgrade note to 3.19 regarding check run permissions  https://review.opendev.org/75584219:02
*** yolanda has quit IRC19:04
*** yolanda has joined #zuul19:04
hamalqi dont know if this question should be asked here? how we can access the openstackdev config inside Tempest test?19:06
fungihamalq: you probably want the #openstack-qa channel for that19:07
hamalqfungi: thanks19:07
fungithe quality assurance team in openstack handles the tempest testsuite19:07
openstackgerritMerged zuul/zuul master: Add CORS header to quickstart log server config  https://review.opendev.org/75586419:42
*** tosky has quit IRC19:57
*** tosky has joined #zuul19:58
*** tosky has quit IRC20:19
*** mattd01 has left #zuul20:41
*** freenzyfriday has joined #zuul20:47
*** freenzyfriday has quit IRC20:55
*** hashar has quit IRC20:56
*** rfolco has quit IRC20:58
*** freenzyfriday has joined #zuul21:41
*** freenzyfriday has quit IRC21:47
*** holser has joined #zuul21:48
*** rlandy|rover has quit IRC21:59
*** freenzyfriday has joined #zuul22:35
*** freenzyfriday has quit IRC22:44
*** yolanda has quit IRC23:23
*** yolanda has joined #zuul23:24
*** freenzyfriday has joined #zuul23:30
*** freenzyfriday has quit IRC23:35

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