Tuesday, 2019-08-27

flaper87SpamapS: roger that! I think I'll follow your approach00:08
*** rlandy|ruck is now known as rlandy|ruck|bbl00:11
*** stewie925 has joined #zuul00:14
*** threestrands has joined #zuul00:24
SpamapSShrews: Oh, btw, I agree with you that the Dockerfile probably isn't an API to be carefully adjusted. I just wanted to bring up that it broke us and that I'm still looking for a way to run Zuul and Nodepool without every upgrade being a slog through dependencies, release notes, and trial&error. Not complaining.. just asking for help in figuring out how I can follow closely without feeling like I"m on a00:49
SpamapStreadmill.00:49
fungisometimes i'm tempted to take up goat farming00:53
* fungi sympathizes00:53
SpamapSEvery time I rotate API keys on our 30+ 3rd party SaaS API's I finish by checking real estate prices in the Highlands of Scotland.00:54
ShrewsSpamapS: i have developed more thoughts around that00:54
SpamapS"Maybe we can just buy a plot of grass and watch the sheep roam."00:54
*** michael-beaver has quit IRC00:55
ShrewsI think if the Dockerfile that we've created for our testing/demonstration purposes is going to be promoted for others to use in their systems (and we develop a promise around that to not break you) then it should probably be separated into a total "zuul docker-based packaging" unit, separate from nodepool, that can then be tested in various ways we are not yet doing.00:56
SpamapSYeah, I really am hesitant to make any changes to what I'm doing until the Kubernetes operator happens. I may even find some cycles for working on that next month.00:57
ShrewsSpamapS: because I don't think we've ever suggested others to use that (unless I've missed that)00:57
SpamapSShrews:to be clear, this breaks me *with the official images*00:58
SpamapSI don't use the Dockerfile, I just pull and push the nodepool images into my local registry.00:58
ShrewsSpamapS: ah00:58
SpamapSThe default user changed, and thus, my k8s objects must be adjusted.00:58
SpamapSI think the thing that's going wrong, is that we're not being explicit about what the support level is for those docker images.00:59
SpamapSThey're damned useful for the quickstart.00:59
ShrewsYeah00:59
ShrewsIf we are going to be explicit about a higher support level, then yeah... it needs to be a real packaging thing. But we've explicitly tried to stay out of that area. But seems we still have a foot lingering in it...01:00
SpamapSIMO it will make a lot more sense when there's an operator, and we can test the whole thing in minikube in the gate.01:00
ShrewsThe operator probably makes all this moot01:00
Shrewsyeah, what you said01:00
ShrewsSpamapS: in the meantime, i'll poke you if I see any more Dockerfile changes put up01:01
Shrewswith a sharp, pointy stick01:02
fungiand now i have kraftwerk's "pocket calculator" stuck in my head01:02
fungithanks01:02
fungi(i'm the operator with my pocket calculator)01:02
Shrewsyou kids and your new fangled music01:03
* fungi shakes his cane at Shrews01:03
SpamapSShrews:mighty kind of you01:05
SpamapSI think the real problem is just that I've charged off into the bold unknown and now I'm annoyed that they don't have wifi or ice cubes.01:05
ShrewsSpamapS: they do have b****face at the bar01:06
* Shrews grabs 2 straws01:06
SpamapSdamn straight01:06
*** calebb has quit IRC01:25
clarkbzuulians I've been talking with stewie925 over in #openstack-qa about a weird thing opendev.org/x/ranger-agent has noticed for jobs against https://review.opendev.org/#/c/677258/5 that change is proposed against the python3 branch but some jobs check out master instead of python3. This leads them to testing the wrong commit01:29
clarkbWhat I've found is that on the executors that run the jobs against master there is no python3 branch in the /var/lib/zuul/executor-git repo for that project01:30
clarkbthe jobs that run on executors with a python3 branch succeed01:30
clarkbInitially I thought maybe a problem with our opendev replication but thost executor git repos all have remotes for review.opendev.org which is the canonical source (gerrit)01:31
*** bhavikdbavishi has joined #zuul01:31
fungiany idea how long ago that branch was created?01:32
clarkbI don't know01:33
clarkbit was well before these jobs ran because an earlier patchset was pushed on the 19th01:33
fungijust wondering if we could find logs from when the executors should have fetched that branch01:34
clarkbwell they should do an update on every job run01:35
*** bhavikdbavishi1 has joined #zuul01:35
*** bhavikdbavishi has quit IRC01:35
*** bhavikdbavishi1 is now known as bhavikdbavishi01:35
fungican probably take a snapshot of the git tree from an affected executor and then try a remote update in it01:36
clarkb2019-08-26 16:35:41,406 INFO zuul.Merger: [e: 9e01fe2c653a4c7ea9d121e41c2ed5f7] [build: b405f247cf3a441b924bce4c35b2f635] Skipping updating local repository gerrit/x/ranger-agent01:39
clarkbthat may be the problem "skipping"01:39
fungihuh... why ever for, zuul?01:39
clarkbif I'm reading the code correctly bceause the rev/commit already exists in the repo01:40
fungioh! so it's a commit present on master too?01:40
clarkbno I think this may be more subtle the commit (e5ef4f738e6d916103c178aedb65e6aa7d2e9dfd) does not exist in master or on ze05's repo01:41
fungiwait, that doesn't make sense01:41
fungichange pushed for a nonexistent parent?01:42
clarkbno the commit is proposed against python3 and has not merged yet01:42
clarkbso does not exist anywhere near master01:42
fungiand the parent is the tip of that branch?01:43
clarkbyes01:43
clarkbwhich happens to also be master01:43
fungier01:43
fungiokay, so the master and python3 branches have the same head commit currently01:43
fungiyeah, that's probably a corner case we didn't think about but will happen any time a branch is created from the tip of another existing branch i guess01:44
clarkbwhat is odd is some executors have updated01:44
clarkbbut ya I guess if we check the parent commit then we could think the branch is there and not update01:44
clarkbso the needs update check should also check if the ref as well as the rev is present01:45
fungithe difference in result is merely cosmetic though, right? because it's testing the same git history in either case?01:45
clarkbno it isn't that is the problem01:46
clarkbit is testing a checkout of master which is the parent commit01:46
fungioh, but i guess for cross-repo dependencies it'll compare the wrong refname01:46
clarkbthis is for the repo under test specifically01:46
clarkbon the test node it checks out master01:46
fungioh, it doesn't actually checkout the change?01:46
clarkbmaster has the wrong ref because we pushed the correct ref to python301:46
clarkbcorrect it checks out master01:46
fungiyeah that's broken then01:46
fungiso a fallback behvior gone awry01:47
fungii guess ff merges between branches could also result in this scenario01:48
fungimaybe that's the difference? the branch appeared on some mergers when there was an outstanding parent which had not merged to the python3 branch and had not then been subsequently merged from python3 to master?01:49
fungier i mean which had merged to the python3 branch01:49
clarkbpossible those other executors had never handled jobs for that repo too01:50
clarkband so when they get one they started from scratch01:51
clarkbexecutors that had handled the repo in the past did the skip?01:51
fungiso python3 branch created from tip of master, changes a,b proposed in series to python3, change a merges and now python3 and master differ, change b is tested and the executor fetches the (differing) python3 branch01:51
fungilater python3 is ff merged into master01:51
funginow the branch tips are equivalent again01:51
fungiahh, yeah, executor cloning repo for the first time could also explain it01:52
fungior executor's merger handling a cat job on scheduler restart?01:52
openstackgerritClark Boylan proposed zuul/zuul master: This is a stub for a bug to help us find and fix it  https://review.opendev.org/67871001:53
clarkbfungi: ya I think a cat on restart might do it too01:53
clarkbin any case I think ^ that calls out the code that needs updating. What I've written is more psuedo code than anything becase it is late and I don't understand the datastructures that are currently passed in01:53
clarkbchances are we need to pass more data to do this check properly01:53
clarkbI was just handed a plate of dinner so eating that next01:54
clarkbthen probably won't get to this until tomorrow01:54
*** stewie925 has quit IRC02:16
*** rlandy|ruck|bbl is now known as rlandy|ruck02:29
*** rlandy|ruck has quit IRC02:29
*** noorul has joined #zuul02:35
*** dolpher has quit IRC02:36
*** noorul has quit IRC02:52
*** rfolco has quit IRC04:03
*** raukadah is now known as chkumar|rover04:26
* SpamapS kinda needs a whiteboard to understand that conversation04:34
AJaegerzuul-maint, do you know why target_dir is not passed on from https://opendev.org/openstack/project-config/src/branch/master/playbooks/static-docs/promote.yaml#L40 to https://opendev.org/openstack/project-config/src/branch/master/playbooks/static-docs/promote.yaml#L55 ? See https://zuul.opendev.org/t/openstack/build/6e42137688154d8fa6759ec5dcf03651/console  which failed with04:52
AJaegerhttps://zuul.opendev.org/t/openstack/build/6e42137688154d8fa6759ec5dcf03651/console#1/1/0/static.openstack.org04:52
*** swest has joined #zuul05:10
*** swest has quit IRC05:16
*** swest has joined #zuul05:17
*** sanjayu_ has joined #zuul05:42
AJaegerianw found a solution and explained it to me on #openstack-infra  - thanks!05:54
*** badboy has joined #zuul06:53
badboyhi06:54
mordredShrews, SpamapS: the dockerfiles and containers produced from them are totally intended for production usage - so I think that breakage indicates an area where our testing is insufficient and needs to be improved (sorry SpamapS)07:00
*** fdegir has quit IRC07:07
*** fdegir has joined #zuul07:08
*** gtema_ has joined #zuul07:28
*** threestrands has quit IRC07:32
*** jpena|off is now known as jpena07:40
openstackgerritMonty Taylor proposed zuul/zuul master: Make json outfile seeking clearer  https://review.opendev.org/67874007:43
*** panda has quit IRC08:02
*** panda has joined #zuul08:02
badboyhow can I filter vote-deleted event based on the content?08:22
*** jangutter has quit IRC08:37
*** badboy has quit IRC08:48
*** badboy has joined #zuul09:00
*** jangutter has joined #zuul09:01
*** zbr has joined #zuul09:12
badboytristanC: as I understand Zuul only accepts the following events: https://opendev.org/zuul/zuul/src/branch/master/zuul/driver/gerrit/gerritconnection.py#L11909:16
badboytristanC: so vote-deleted is not one of them09:16
*** hashar has joined #zuul09:39
*** sshnaidm is now known as sshnaidm|afk09:41
*** bjackman has joined #zuul09:42
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul Web: add /api/user/authorizations endpoint  https://review.opendev.org/64109909:48
*** mhu has joined #zuul09:56
zbrdoes anyone have a CLI script that I can use to query status of zuul jobs on current change? like listing jobs and their status: queued, running, finished.10:02
openstackgerritMonty Taylor proposed zuul/zuul master: Write errors from ansible execution into json log  https://review.opendev.org/67672310:02
openstackgerritFabien Boucher proposed zuul/zuul master: A Zuul reporter for Elasticsearch  https://review.opendev.org/64492710:09
*** jpena is now known as jpena|lunch11:30
openstackgerritMerged zuul/zuul master: Apply changes to command module from ansible 2.6  https://review.opendev.org/67859411:42
AJaegerzuul-maint, everybody, when and how to move to ansible 2.7 for OpenDev? See  https://review.opendev.org/67669711:43
tobiashAJaeger: 2.7 is the default in zuul, is that a preparation to switch the default to 2.8?11:44
*** sanjayu_ has quit IRC11:46
AJaegerlet'S ask pabelanger , we switched Zuul tenant already11:49
*** AJaeger is now known as AJaeger_11:50
openstackgerritBenedikt Löffler proposed zuul/zuul master: Report retried builds in a build set via mqtt.  https://review.opendev.org/63272711:51
openstackgerritBenedikt Löffler proposed zuul/zuul master: Report retried builds via sql reporter.  https://review.opendev.org/63350111:51
*** gtema_ has quit IRC11:52
*** gtema has joined #zuul11:53
*** themr0c has joined #zuul11:55
*** themroc has quit IRC11:55
*** gtema has quit IRC11:59
*** sshnaidm|afk is now known as sshnaidm11:59
*** badboy has quit IRC12:15
*** rfolco has joined #zuul12:22
*** rlandy has joined #zuul12:28
*** rlandy is now known as rlandy|ruck12:29
*** jpena|lunch is now known as jpena12:32
openstackgerritMatthieu Huin proposed zuul/zuul master: Zuul Web: add /api/user/authorizations endpoint  https://review.opendev.org/64109912:43
openstackgerritFabien Boucher proposed zuul/zuul master: Add reference pipelines file for Gerrit driver  https://review.opendev.org/67268312:48
openstackgerritFabien Boucher proposed zuul/zuul master: Add reference pipelines file for Github driver  https://review.opendev.org/67271212:57
*** bjackman has quit IRC12:59
*** yolanda has quit IRC13:06
*** yolanda__ has joined #zuul13:06
fbohi zuul-maint; who should I ping to ask for review on the Elasticsearch reporter https://review.opendev.org/644927 ? I think the review is ready and seems fine to be merged also we use this reporter w/o issue since some months.13:07
tobiashfbo: pinging zuul-maint is correct ;)13:08
*** bjackman has joined #zuul13:09
fbotobiash: so that's perfect :)13:09
pabelangertobiash: AJaeger_: yah, I wanted to flip the switch to ansible 2.8 before 2.9 was released. So we we're 2 releases back.13:23
pabelangerbut need to fix up stack at https://review.opendev.org/674854/ first13:23
*** bhavikdbavishi has quit IRC13:29
*** bhavikdbavishi has joined #zuul13:29
*** michael-beaver has joined #zuul13:55
openstackgerritTristan Cacqueray proposed zuul/zuul master: webtrigger: add web route and rpclistener  https://review.opendev.org/55483913:56
*** jeliu_ has joined #zuul14:02
*** jeliu_ has quit IRC14:02
*** jeliu_ has joined #zuul14:03
openstackgerritMerged zuul/zuul master: Write json log file by seeking and appending  https://review.opendev.org/67671714:12
openstackgerritBenedikt Löffler proposed zuul/zuul master: Report retried builds in a build set via mqtt.  https://review.opendev.org/63272714:16
openstackgerritBenedikt Löffler proposed zuul/zuul master: Report retried builds via sql reporter.  https://review.opendev.org/63350114:16
Shrewsmhu: oh hi! I could use your help on something. My changes in https://review.opendev.org/#/q/topic:autohold-revamp introduce two new zuul CLI commands: autohold-delete and autohold-info. I'm not very familiar with cherrypy and wondering if you could help in integrating those? Or guide me in what needs to be done.14:26
*** sshnaidm_ has joined #zuul14:29
*** sshnaidm has quit IRC14:30
*** sshnaidm__ has joined #zuul14:34
*** spsurya has joined #zuul14:35
openstackgerritMonty Taylor proposed zuul/zuul master: Write errors from ansible execution into json log  https://review.opendev.org/67672314:35
*** sshnaidm_ has quit IRC14:36
*** sshnaidm__ is now known as sshnaidm14:51
clarkbcorvus: did you see the notes about zuul running tests against the wrong branch in scrollback?15:01
clarkblong story short it seems that zuul may skip repo updates when new branches are created and that results in zuul falling back to a default branch of master15:01
mhuShrews, happy to help if I can! I'll have a look at your changes15:02
corvusclarkb: i did not see that; i'm pretty sure we thought of that and we're under the impression that works and is tested, so it will be interesting to see what we missed15:02
clarkbcorvus: I think it may happen beacuse we check if a commit is present and not necessarily that the refs re present15:03
clarkbthen later we check if the branch is in the repo that we did't update because the commit was there?15:03
clarkbI think we need to check for refs and commits before deciding if an update is appropriate15:03
*** jamesmcarthur has joined #zuul15:05
Shrewsmhu: Thanks! I started to get confused as to the best approach when I looked at ZuulWebAPI.autohold().15:06
corvusclarkb: oh, i read scrollback -- that was a later efficiency change that tobiash came up with -- I9364e438d581b068fa19c9dfc24adab60479c38515:06
corvusclarkb: that's got a test we can probably adapt15:07
corvusclarkb: i just left a comment on that change -- can you take a look and see if that's the sort of thing you had in mind?15:08
clarkbyup I even pushed a psuedocode change that "does" that15:09
clarkbbecause it was late and wanted a pointer for the future15:09
corvusclarkb: cool, i think that's the right approach15:09
corvusat least, it sounds good to my tired braid15:09
corvusbrain15:09
clarkbtobiash: ^ if you hvae a moment can you look at that too since you wrote that optimization15:10
tobiashclarkb, corvus: I'm currently in fire fighting mode in my own deployment, is it ok if I look in about two hours?15:11
clarkbtobiash: yes, no rush.15:12
tobiashclarkb: is there a tldr so I don't have to read the whole scrollback?15:13
clarkbtobiash: basically in https://review.opendev.org/#/c/648229/6/zuul/merger/merger.py isUpdateNeeded only checks if commits are present and not refs. So when a new branch is created with a shared commit of an existing branch we dno't update and pull in that new branch. Later this causes zuul to fall back to the default branch if the change was proposed to a new branch15:14
tobiashclarkb: thanks, I'll check later at home15:15
tobiashhowever my understanding of the repo state was that it should be complete and re-creates every ref15:16
tobiashis that understanding wrong?15:16
fungiit was the case until that mechanism was changed to skip updating when the ref is already present15:16
clarkbI haven't gotten that far yet. Mostly identifying behavior based on logs so far. I will go through and trace that after meetings and try to understand the specific cause15:16
fungier, when the commit is already present15:16
tobiashso this check should check if every commit referenced by the refs to be created by the repo state is present (so it can be recreated)15:17
tobiashif not, it updates the repo, if everything is there update is not needed15:17
tobiashthat was the idea15:17
*** mattw4 has joined #zuul15:17
clarkband that every ref is present15:17
fungiproblem is the commit can be there because it was present on another branch15:17
tobiashbecause restoring the repo state throws all refs away and recreates them with their target commits (which has been verified to exist)15:18
fungiwhen the commit is present on the default branch and the target branch, we're seeing it not fetch the target branch ref and it logs "skipping updating local repository..."15:21
fungi(so hitting line 620 there)15:21
*** mattw4 has quit IRC15:22
*** themr0c has quit IRC15:29
*** chkumar|rover is now known as raukadah15:31
openstackgerritMerged zuul/zuul master: Improve visualization retry attempts in UI  https://review.opendev.org/67814715:32
*** jangutter has quit IRC15:46
*** sanjayu_ has joined #zuul15:51
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed zuul/zuul-jobs master: Add tests for manifest generation for missing files  https://review.opendev.org/67857315:52
*** sshnaidm is now known as sshnaidm|afk15:54
*** jpena is now known as jpena|off16:04
*** noorul has joined #zuul16:06
openstackgerritClark Boylan proposed zuul/zuul master: Check refs and revs for repo needing updates  https://review.opendev.org/67889516:09
clarkbcorvus: fungi tobiash ^ I think something like that is much closer to the fix we want. Now to figure out testing for it16:09
clarkb(my psuedocode is now real code that may or may not work)16:09
*** noorul has quit IRC16:22
*** jamesmcarthur has quit IRC16:22
*** jamesmcarthur has joined #zuul16:27
openstackgerritClark Boylan proposed zuul/zuul master: Check refs and revs for repo needing updates  https://review.opendev.org/67889516:40
clarkbcorvus: tobiash fungi ^ I think that is ready for review now16:40
*** amotoki is now known as amotoki_16:42
openstackgerritDmitriy Rabotyagov (noonedeadpunk) proposed zuul/zuul-jobs master: Add tests for manifest generation for missing files  https://review.opendev.org/67857316:44
clarkbCan someone explain to me how to manage zuul/web/static/.keep properly?16:44
clarkbseems like every time I push a change that gets modified16:44
openstackgerritJeff Liu proposed zuul/zuul-operator master: Add PerconaXDB Cluster to Zuul-Operator  https://review.opendev.org/67731516:44
clarkbmaybe I should stop using git commit -a and instead explicitly git add files?16:44
tobiashclarkb: this needs fixing, then the keep file should be no problem anymore: https://review.opendev.org/66310816:45
tobiashclarkb: what I don't understand on the ref fix is, why isn't that branch part of the repo state?16:46
clarkbtobiash: it is part of the repo state but its rev value matches master so the rev commit is present16:46
tobiashfrom my understanding the repo state should be complete and contain every ref needed for the job in that repo16:46
clarkbwe have refs/origin/master: '12345' and refs/origin/python3: '12345' beacuse the rev value matches master in the repo we see that as not needing an update16:47
clarkbthen the executor local git repo does not update16:47
*** jamesmcarthur has quit IRC16:47
fungiit contains every commit and every named ref, but apparently not necessarily every associated branch ref16:47
tobiashbut why do we need an update in this case?16:47
tobiashwe're restoring every ref from the repo state16:48
clarkbtobiash: because later zuul checks if the change's proposed branch is a valid branch in the local repo and beacuse we did not update python3 does not exist in the local repo16:48
clarkbthen it falls back to the default branch (master)16:48
tobiashis that before we restore the repo state then?16:48
tobiashbecause after restoring it the branch should be there16:48
fungiwhich routine does the "restoring"?16:49
tobiashhttps://opendev.org/zuul/zuul/src/branch/master/zuul/merger/merger.py#L67916:49
tobiash_restoreRepoState16:50
tobiashit deletes all refs and sets all new16:50
clarkbtobiash: https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L1158-L1160 is where we select the default branch16:50
tobiashand the check before is designed to ensure that this works16:50
clarkbtobiash: they are different repos16:52
clarkbresolve branch is looking in executor git, and your restore state is in the build git repo16:53
clarkband yes self.project_info is populated before doMergeChanges which does the state restore16:54
clarkb(so even if it were the same repo the ordering is wrong)16:54
clarkbI think this ensures both sets of repos will be correct then we don't have to worry about strict ordering so much16:55
tobiashah, got it16:57
openstackgerritClark Boylan proposed zuul/zuul master: Check refs and revs for repo needing updates  https://review.opendev.org/67889516:57
clarkbfixed the .keep file so unittests can run16:57
tobiashresolvebranch only resolved the branch name in the other repo and the correct revision is done later16:57
tobiashactually this might even fix some weird issue which one of my users reported16:59
tobiashhe complained that zuul did use a wrong commit somewhere but I hadn't time for an analysis yet16:59
tobiashIt's very likely that this is the issue16:59
tobiashclarkb: fix lgtm, thanks!17:01
clarkbthank you!17:01
Shrewsmhu: thx for the hints/feedback. I'll take a stab at making those changes and ping you if I need more help.17:08
*** jamesmcarthur has joined #zuul17:27
clarkbianw: I'm reading corvus' comments on https://review.opendev.org/#/c/678049/ to imply he would prefer we restart the log streamer instead of killing the executor entirely. I think I'll hold off on incorporating any further code changes until we have agreement on the best high level approach there. But I do think it is implementing the pipe read on both sides (and maybe as a followup look at multiprocessing)17:30
clarkbjeliu_: are you using the install-kubernetes role from zuul-jobs in your operator testing?17:31
clarkbjeliu_: if so have you run into any problems with dns resolution? I'm curious if https://review.opendev.org/#/c/677787/ would be helpful (based on other people's jobs I think it will be but you are probably doing the most with that currently)17:31
*** hashar has quit IRC17:32
*** jamesmcarthur has quit IRC17:52
*** bhavikdbavishi has quit IRC17:52
*** bhavikdbavishi has joined #zuul17:54
*** bhavikdbavishi has quit IRC18:13
jeliu_clarkb: yes I am using the role. And we haven't ran into dns problems that I know of, the only networking problem we had before was related to firewall18:27
openstackgerritTristan Cacqueray proposed zuul/zuul master: webtrigger: add web route and rpclistener  https://review.opendev.org/55483918:28
*** mhu has quit IRC18:30
*** bjackman has quit IRC18:43
openstackgerritTobias Henkel proposed zuul/zuul master: Revert "Revert "Create zuul/web/static on demand""  https://review.opendev.org/66310819:02
*** jamesmcarthur has joined #zuul19:03
*** michael-beaver has quit IRC19:04
*** sanjayu_ has quit IRC19:06
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: fix connections list github base_url  https://review.opendev.org/67895019:47
openstackgerritTobias Henkel proposed zuul/zuul master: Update heuristing of parallel starting builds.  https://review.opendev.org/67170220:07
*** weshay is now known as weshay_pto20:11
openstackgerritTobias Henkel proposed zuul/zuul master: web: test trailing slash are removed from renderTree  https://review.opendev.org/67682420:34
*** wxy-xiyuan has quit IRC20:45
*** jamesmcarthur has quit IRC20:46
pabelangerhow would I add datetime to builds page? eg: https://dashboard.zuul.ansible.com/t/ansible/buildsets?result=MERGER_FAILURE doesn't say when they happened, which is helpful to know21:02
tristanCpabelanger: perhaps using https://review.opendev.org/#/c/677466/ ?21:02
pabelanger\o/21:03
pabelangeryah, we are seeing a lot of MERGER failures on github, and want to see if they are all related. By theory is some race condition on github side for when event is sent out, and the ref on remote side is created21:04
tristanCwe saw a few recently too, hence the wip patch, though it was for an opendev repo21:05
tristanCwhich hasn't been updated for a long time, and for some reason the merger job failed once on each salled content21:06
*** spsurya has quit IRC21:07
pabelangerthat's about the only issue we see now with github, all other improvements from tobiash have been awesome21:07
openstackgerritMerged zuul/zuul master: web: extract pure functions from the TaskOutput component  https://review.opendev.org/67546021:18
openstackgerritJeff Liu proposed zuul/zuul-operator master: Add PerconaXDB Cluster to Zuul-Operator  https://review.opendev.org/67731521:20
openstackgerritMerged zuul/nodepool master: Functional testing: add journal-to-console element  https://review.opendev.org/66978721:32
openstackgerritMerged zuul/zuul master: github: properly exist when failing to get a pull request  https://review.opendev.org/67694821:33
openstackgerritMerged zuul/zuul master: Hide "root" variable in job web page  https://review.opendev.org/67546121:47
openstackgerritTristan Cacqueray proposed zuul/zuul master: web: add build button to trigger job  https://review.opendev.org/63571621:54
clarkbianw corvus had some thoughts on https://review.opendev.org/#/c/678049/ if you want to check them21:59
openstackgerritJeff Liu proposed zuul/zuul-operator master: Add PerconaXDB Cluster to Zuul-Operator  https://review.opendev.org/67731522:08
clarkbjeliu_: I think as soon as we try to run workload in the pods that pulls external resources (from say github or gerrit etc) we may need that cahnge22:09
clarkbjeliu_: do you know if you are doing anything like that already (would be useful to know if minikube somehow solves this problem when kubeadm doesn't)22:09
jeliu_I currently do have external resources in my change from github (will try to remove these dependencies later on) and it seems to be working fine. Is the use case that your patch fixes for minikube or kubeadm?22:19
jeliu_clarkb: going offline soon feel free to contact me through email (jeliu@redhat.com)22:19
clarkbjeliu_: mnaser ran into problems with dns resolution using kubeadm. Reviewing our use of minikube I beleive we have the same flaw22:20
clarkbbut should only be affected if the pods themselves make dns requests for things on the internet22:21
*** jeliu_ has quit IRC22:25
*** armstrongs has joined #zuul22:33
*** armstrongs has quit IRC22:42
ianwclarkb: yeah, i don't have strong opinions; as you say i think systemd restarting the service, or k8s or whatever is, for mine, is just an easier to reason about behaviour23:07
ianwi think moreso though, if we had a test that would be awesome23:08
ianwand then i'd feel more comfortable about a bigger change like jumping to multiprocessing to handle it, if we thought that was a bit of a simplification23:08
clarkbI wonder if it would make sense to test that in the quickstart job? testing forking behavior in the unittest suite seems wrong, but maybe it is ok there23:13
clarkbthe unittests have never been real unittests23:14
ianwyeah, it does not seem unit-testy, i agree ... it's a tricky one23:14
*** rlandy|ruck has quit IRC23:57

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!