Wednesday, 2024-05-22

dpawlikHey fungi o/ The old server is as tonyb said - can be removed. He created new one, so the 01 can be removed06:17
dpawlikfungi: I send you an email on which you can forward. Thanks :)06:19
*** ykarel__ is now known as ykarel08:10
fungidpawlik: thanks! i bounced the message to you with my openinfra.dev account since gmail doesn't like to accept messages from my personal account any longer. date on it was may 12, from "ahmad alassaf" with some png attachments13:15
fungiif it doesn't come through (check your junk mail first), i can try passing it along some other way13:15
dpawlikfungi: checking13:30
dpawlikfungi: I have in spam \o/13:36
fungiokay, great!13:36
dpawlikfungi: looks odd, and probably we need help from reeed 13:36
dpawlikfungi: replied14:09
dpawlikhope this time you will get email14:09
fungidpawlik: yep, i can receive from gmail addresses just fine, it's sending to gmail that's challenging for me. anyway, looking at your reply, maybe that report wasn't about our opensearch instance at all? i saw the mention of elasticsearch and assumed (incorrectly?) that's what the reporter was talking about14:33
fungibut yes, now that i look closer, i wonder if they contacted me because i'm listed as a security contact for zuul and they're confusing netflix's zuul webrouter project with the zuul gating project14:34
fungi#status log Deleted the obsolete logscraper01.openstack.org server instance and associated DNS records14:42
opendevstatusfungi: finished logging14:42
jovial[m]I don't understand why zuul isn't rechecking this job: https://review.opendev.org/c/openstack/kayobe/+/910513. Any ideas?15:07
clarkbjovial[m]: patchset 11 was tested but 12 and 13 were not. If you look at the diff between the two the only changes are depends on to several github projects. I suspect that is related15:12
clarkbI can look at logs after I've loaded some ssh keys but possibly zuul is unable to load the relevant info on those PRs and thus can't make a determination on how to run the jobs15:13
fungijovial[m]: clarkb is right, you've added a depends-on to projects which aren't in zuul's openstack tenant15:17
fungizuul has to be told about the existence of every repo you're going to depends-on15:18
fungithat is done by adding them to https://opendev.org/openstack/project-config/src/branch/master/zuul/main.yaml15:18
clarkbfungi: jovial[m] it may go beyond that the zuul log is complaining that it has insufficient permissions to check if those PRs are mergeable15:19
clarkbERROR zuul.github.graphql: [e: 0aa0ed729db8463092667d7b4885bf00] Error running query canmerge15:19
clarkb"Your token has not been granted the required scopes to execute this query. The 'pattern' field requires one of the following scopes: ['public_repo'], but your token has only been granted the: [''] scopes.15:19
clarkbthat may be a bug in how we generated our token though15:19
clarkball three PRs have merged though so removing them from the depends on list is a noop and would workaround this in the short term15:20
fungiwell, it's a noop if the jobs are checking out the target branch(es) for the pull requests anyway15:21
clarkbya the change specifies explicit checkouts for the three repos15:23
clarkbso the depends on would be completely ignored except for preventing merging until the parents merged if I read this properly15:23
fungiclarkb: i suspect those depends-ons were some misguided attempt to work around another problem. looking at the pull requests, they all merged over a month ago15:25
fungibut the depends-on lines were added just last week15:25
fungialso a likely reason for the error you saw in the log is that at least one of those pull requests already has its underlying branch deleted15:26
clarkb" I do see some use in referencing the PRs with depends-on in the commit message for documentation purposes, but these projects are not in zuul config so won't affect the CI." from the comments15:26
clarkboh yup if it is one of those PRs that could explain it15:27
fungiaha, okay so they were adding them as informational and counting on zuul to just ignore them because it doesn't have those repos configured, but apparently a depends-on to a post-merge cleaned-up pull request will confuse zuul15:27
opendevreviewJeremy Stanley proposed openstack/project-config master: Clean up unused labels from nl02 config  https://review.opendev.org/c/openstack/project-config/+/92019015:36
opendevreviewMerged openstack/project-config master: Add Ubuntu 24.04 LTS (ubuntu-noble) nodes  https://review.opendev.org/c/openstack/project-config/+/92014915:49
jovial[m]thanks clarkb and fungi - I will do as you suggest and remove the depends-on for the projects that zuul does not know about. You were right, I did think that zuul would ignore those and added them purely for documentation purposes.16:39
-opendevstatus- NOTICE: There will be a short Gerrit outage while we update to the latest 3.8 release in preparation for next weeks 3.9 upgrade.17:01
opendevreviewJeremy Stanley proposed openstack/project-config master: Fix unbound setup for ubuntu-noble  https://review.opendev.org/c/openstack/project-config/+/92020819:35
opendevreviewMerged openstack/project-config master: Fix unbound setup for ubuntu-noble  https://review.opendev.org/c/openstack/project-config/+/92020820:09

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