Friday, 2025-07-18

ianychoiHi team, would it be possible to get a backup of translate.openstack.org database? I have two main reasons: 1/ I want to move forward on Weblate migration by analyzing manual data and 2/ Now I cannot approve Korean language team members after I delete one Zanata user.. I need to double-check some table/data integrity issues.10:37
opendevreviewTakashi Kajinami proposed openstack/project-config master: Remove networking-midonet  https://review.opendev.org/c/openstack/project-config/+/91941511:01
tonybianychoi: we can do that.   safer to give you a copy of the backup than do live investigation.11:02
fungithough it looks like the local db backups on the server are empty13:54
fungithe database we're dumping definitely has content and the defaults file we tell mysqldump to use works to give me access with mysqlclient13:56
fungimysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces13:57
fungii think that has something to do with it13:58
fungilooks like it's because we're trying to back up all databases with the zanata user even though it only has access to the zanata db14:00
fungiif i drop the --all-databases option and specify the "zanata" database, i get the dump i expect from it14:01
fungithough the tablespaces error is somewhat orthogonal, i have to add --no-tablespaces to silence that14:02
fungiunrelated... infra-root: config-core: i've self-approved https://review.opendev.org/954374 (Remove CLA enforcement from all projects and lock) since we said today is when we were going to do the other gerrit config changes depending on it14:06
fungiokay, back to the zanata db backup topic, it looks like the exact edits described above are already implemented for the stream backup borg is doing, so it looks like our remote copies are fine, it's just the local dumps that aren't14:19
opendevreviewMerged openstack/project-config master: Remove CLA enforcement from all projects and lock  https://review.opendev.org/c/openstack/project-config/+/95437414:20
fungiaha, this is apparently already known, and covered in the code comment at https://opendev.org/opendev/system-config/src/commit/a88a6f5/modules/openstack_project/manifests/translate.pp#L133-L13814:21
fungiso anyway, if we're going to hand off a db dump, it'll either have to be fetched from one of the backup servers or use mysqldump to make a one-off with the options described there14:22
Clark[m]fungi: I'm slowly rolling in (doing system updates now). Once clas are removed from projects the next step is updating all projects acls to remove the clas themselves. Do we want to do one at a time and confirm that the accepted target group isn't removed or otherwise affected?14:28
Clark[m]I think that info may still be relevant going forward. I don't expect that removing the cla itself will affect the group existence 14:28
fungiwell, that's all stored in notedb in git repos anyway, right? so if it does remove them then there will be a transaction history regardless, so if we still need the data in the future we can pull it from there anyway14:30
Clark[m]Good point. I believe this is the case14:30
Clark[m]Looks like manage projects may be slow again (likely due to an overwhelmed gitea but I haven't checked yet)14:35
clarkbgitea13 does have somewhat high load (not the highest I've seen but high enough to indicate it is probablythe thing slowing down manage-projects)14:46
clarkbacls should be updated in gerrit now though (gitea management is done according to the playbook log)14:46
fungiBuild succeeded (deploy pipeline).14:56
fungiall good14:56
clarkbI guess next step is manually applying https://review.opendev.org/c/opendev/system-config/+/954376/2/doc/source/gerrit.rst to all projects then we can approve that change?15:00
clarkbI've reapplied my +2 to that change and I think I'm ready for the manual updates and change approval if you are15:04
clarkbthen once we're happy with the results of that we can consider if we also want to proceed with the last omnibus gerrit image update: https://review.opendev.org/c/opendev/system-config/+/882900 before restarting the service to pick upthe changes15:04
fungiyeah, i'll work on applying the contributor-agreement config removals... i guess doing it through the ui is still the simplest approach? or have we been pushing config changes like that into git lately?15:07
clarkbfungi: I think if you go through the web ui it forces you to code review the chagnes now15:07
fungiah, it's admittedly been a while15:07
clarkbwhich is doable but you may have to modify your group membership to review and approve such a change. I think when hashtags were updated globally corvus pushed to all projects directly for that15:08
fungiyeah, looks like i did that a couple of years ago for receive.rejectImplicitMerges15:09
corvusyeah, the web ui didn't work for some reason; i think we need some permissions changes for that... we should probably do it, but it's a diversion.  i burned some cycles on it last time before just pushing like we usually do15:09
fungimainly i just have to remember the summoning and binding incantations for pushing to the right ref in all-projects15:10
corvusi'm sure i left details in the irc log15:10
corvus(about the red herring of web ui review... i probably didn't do anything useful like leave the correct incantation)15:10
fungigit fetch origin refs/meta/config && git checkout FETCH_HEAD [...] git push origin HEAD:refs/meta/config15:13
fungithat's the bookends15:13
fungiHEAD is now at 283e0b0 Allow any gerrit user to edit hashtags15:14
fungithat meets expectations15:14
fungiinfra-root: this is what i'm preparing to push https://paste.opendev.org/show/btHxpa3asThwid10tfht/15:18
clarkbthat diff looks correct to me15:19
fungii corrected some typos in the commit message just now but otherwise that's what i'm planning to push15:20
fungii think i'll have to grant my admin account additional permissions15:22
clarkbyes I think you need to add your admin account to project bootstrappers temporarily15:22
fungi283e0b0..76473b6  HEAD -> refs/meta/config15:24
fungi#status log Manually injected project.config edits indicated in https://review.opendev.org/954376 for CLA removal from Gerrit15:25
clarkbI wonder if it validates that nothing is using the cla at this point. We believe that to be the case so unlikely to get an error if they do validate it15:25
opendevstatusfungi: finished logging15:25
clarkbhttps://review.opendev.org/c/opendev/system-config/+/954376 is next once we're happy that cla removal hasn't caused problems. Not sure what we would check though. Pushing code to a project that long used the cla to ensure we didn't leave some vestigal config laying around?15:26
fungilooks like we've got a bit of documentation and example cleanup to do still, but nothing urgent: https://codesearch.opendev.org/?q=requireContributorAgreement15:27
fungiand none of those repos required a cla, so can't really use them to test things regardless15:28
fungiJul 18 15:29:47 eavesdrop01 docker-gerritbot[646]: 2025-07-18 15:29:47,538 INFO gerritbot: Sending "Dan Smith proposed openstack/nova master: WIP: Parallelize s-g generators  https://review.opendev.org/c/openstack/nova/+/955091" to #openstack-nova15:30
fungigood enough?15:30
clarkbya I suspect that is about as good as we'll get15:30
clarkbI've noticed that I don't think 954376 will trigger infra-prod-run-review. But that is ok since all it does is update the conatiner image which we manually deploy for gerrit anyawy. Also the quay followup would trigger infra-prod-run-review if we proceed with that one and bundel up all this into a single restart15:33
clarkbshould I approve 954376 or do you want to do that?15:33
fungigo for it15:33
clarkbdone15:34
fungithanks!15:35
clarkbI'll let others weigh in on https://review.opendev.org/c/opendev/system-config/+/882900 to move gerrit images to quay.io while we wait on that change15:35
fungiyeah, looks like it hasn't changed since i last reviewed it 3 months ago15:36
clarkbya I think the main thing there is confirming we're in a spot where we are comfortable to make the switch (should be with gerrit running on podman now) and that nothing has changed since originally pushed/updated and now that would impact the change (rechecking it and having it come back green is a good indication that this is also fine)15:39
clarkbbut if others think its still a good idea and the change itself is sound we should probably approve that soonish as well.15:40
opendevreviewAntoine Musso proposed opendev/git-review master: Command to delete applied local branches  https://review.opendev.org/c/opendev/git-review/+/95509415:45
clarkbother than the planned gerrit updates is there anything else I should be looking at or catching up on this morning? Seems like it was fairly quiet other than the unexpected gerrit shutdown tuesday morning?15:49
corvusclarkb: on the niz front https://review.opendev.org/q/hashtag:+opendev-niz+status:open has 2 interesting things:15:52
corvus1) the changes to clean up the bionic arm64 stuff15:52
corvus2) the changes to remove nodepool15:52
clarkblooks like the bionic arm64 ozj cleanup is still hung up on the openstack/requirements unmaintained branches15:53
corvusfor item #1, i think the state is we're waiting for those depends-on changes to merge15:53
corvusyeah, so to progress that, those changes either need to merge, or we need to time out and say we waited long enough, and just merge https://review.opendev.org/954761 without the dependencies15:54
corvus(we can do that; it will just add some config errors to the relevant repos)15:54
corvusi did merge the use-nodepool switch, so missing labels are now config errors15:54
corvus(i updated 954761 to account for that, so it removes the xenial labels instead of making them "xenial-invalid" like we had before)15:54
clarkbthat is good to know. Let me review the changes I haven't reviewed yet and I know fungi was trying to get feedback from elodilles_pto on cleaning up the unmaintained branches. However _pto indicates that maynot happen quickyl I suspecy15:55
corvusfor item #2 -- merging that is not something for today, but reviewing those 2 changes so that they're ready to merge next week would be good15:55
corvusfungi: you reviewed the child, but you may want to look at the parent too: https://review.opendev.org/955228 removes the nodepool docs15:56
corvus(from system-config)15:56
clarkbcorvus: https://review.opendev.org/c/opendev/zuul-providers/+/951018 appears to be in merge conflict as well (its not part of 1 or 2)15:56
fungiaha, thanks15:56
corvusclarkb: yeah, i'll catch up on that later; not important right now.15:57
corvusi think i'll shut down the nodepool servers tomorrow when i can better keep an eye on them.  no changes needed for that -- that'll just be a manual docker compose down15:58
clarkbcorvus: did you want to weigh in on https://review.opendev.org/c/opendev/system-config/+/882900 as part of the gerrit omnibus update?15:58
clarkbcorvus: sounds good re nodepool shutdown. I would put the servers in the emergency file list as I think ansible may start them up again15:58
corvus(to recap, at this point zuul should not be interacting with nodepool at all, which is why it's safe to shut the servers down any time, and then delete them some time after that)15:59
corvusclarkb: ack re emergency file15:59
clarkbcorvus: https://review.opendev.org/c/opendev/system-config/+/955229/2/playbooks/roles/zuul-executor/tasks/main.yaml the change to add the key material under a new name needs a zuul executor restart to pick up right? But we're not actually changing the content and we don't remove the old file so things should transition gracefully16:02
clarkb(just want to make suer that is the expectation and intention)16:02
corvusclarkb: 882900 +2 with comment -- will leave it up to you to decide how important that is -- but also, i can't remember if our scripts actually change that value, so the initial value may be difficult to change?16:03
corvusclarkb: re key exactly -- material is the same16:04
corvus(also, that change is complete in private hostvars)16:04
clarkback thanks16:04
clarkbI'll finish this review of the nodepool cleanup change then update the gerrit image descriptions for quay16:05
clarkbcorvus: is there a openstack/project-config cleanup to fix the zuul config error on 955229 ? I'm not seeing that one yet16:06
corvusthink it merged; one sec16:07
corvushttps://review.opendev.org/95523516:08
corvusi rechecked 22916:08
clarkbthanks16:08
opendevreviewJeremy Stanley proposed opendev/system-config master: Drop devstack-gate documentation  https://review.opendev.org/c/opendev/system-config/+/95538616:09
funginoticed that ^ when reviewing the nodepool docs removal16:09
corvushttps://review.opendev.org/q/hashtag:+opendev-niz+status:merged  if you want to see other stuff over the last few days16:09
corvusi did a bunch of cleanup16:09
opendevreviewClark Boylan proposed opendev/system-config master: Migrate gerrit images to quay.io  https://review.opendev.org/c/opendev/system-config/+/88290016:11
fricklerclarkb: corvus: as quasi-reqs-core I'd say to force-merge the open changes there for the unmaintained branches. I've still enabled my acc after the devstack cleanup so I can just do it?16:11
clarkbfungi: corvus ^ now with better repo descriptions16:11
clarkbfrickler: ya I think from the opendev side of things we're hapyp for that as the changes are purely mechanical and don't impact the content of the repo as it were16:11
clarkbfrickler: so if openstack/requirements are also happy with that approach I am too16:12
corvussgtm16:14
fungiagreed16:14
fricklerdone, except for https://review.opendev.org/c/openstack/requirements/+/954774 which seems to be in normal progress now16:23
clarkbthe cla cleanup change should merge in a few minutes. I guess if the quay change passes check testing I'll go ahead and approve it too16:29
clarkbthen after that change lands and deploys we can start on a gerrit restart to switch the image source and pull the latest updates16:30
opendevreviewMerged opendev/system-config master: Stop installing and configuring CLAs  https://review.opendev.org/c/opendev/system-config/+/95437616:44
opendevreviewMerged opendev/system-config master: Remove nodepool documentation  https://review.opendev.org/c/opendev/system-config/+/95522816:44
clarkbfungi: I'm guestimating that the earliest we could restart gerrit is around 1900 UTC if we wait for the quay move16:47
fungithat's fine by me, i'll still be around16:52
fungigoing to push up a few changes to clean up requireContributorAgreement references so they're less likely to get cargo-culted16:52
opendevreviewJeremy Stanley proposed opendev/infra-manual master: Replace CLA references with DCO  https://review.opendev.org/c/opendev/infra-manual/+/95539117:04
opendevreviewJeremy Stanley proposed opendev/system-config master: Drop a CLA reference in jeepyb docs ACL example  https://review.opendev.org/c/opendev/system-config/+/95539217:07
fungithose are the main ones17:07
fungithere's also a test fixture in gerritlib that expressly turns requireContributorAgreement off, and similar in zuul's quickstart test gerrit setup, which i didn't bother with as they're not enabling it17:09
fungiand in an airship gerrit deployment script too17:10
fungibut nothing else in any repos we host that turns it on, once the above changes merge17:10
clarkbdouble checking build logs for 882900 I realized that quay.io/opendevorg/gerrit-base:latest does already exist but is a couple years old from our previous attempt17:18
clarkbbut looking at the build logs I'm pretty sure that the gerrit 3.10 image build is pulling the gerrit-base image from the intermediate registry properly17:18
clarkbhttps://zuul.opendev.org/t/openstack/build/19b9f9f95ab9430383e5105e91fe7345/log/job-output.txt#1342-1365 this is the build side pulling the image and the hashes there seem to line up with the hashes on the gerrit-base image build side here: https://zuul.opendev.org/t/openstack/build/555df3b64b444858ad0318d329141bc7/log/job-output.txt#2681-272717:19
fungiyeah, we had a brief attempt to use it from quay back then17:20
clarkbI'm going to approve the change now as the only job remaining is gitea so unaffected by the move17:20
fungisounds good, thanks17:20
clarkbbut if others want to confirm that we appear to be building the image with non stale data that would be appreciated17:20
clarkboh hrm there was a gerrit 3.10.7 release17:21
fungiof course there was17:27
fungido we want to hold up for that?17:27
fungii could go either way17:27
clarkbI'm working on a change for it now17:27
clarkbbut looking at the changelog in https://gerrit.googlesource.com/plugins/replication/+/refs/tags/v3.10.7 I don't think any of those ~3 changes are critical for us17:28
clarkband we don't use webhooks at all so the updates there shouldn't affect us at all17:28
fungiyeah, i was just pulling that up17:28
clarkbalso note that the way we build gerrit proper we're going to update gerrit proper17:30
clarkbbut the plugins are pinned to tagged versions17:30
clarkbhttps://www.gerritcodereview.com/3.10.html#3107 is the release notes for gerrit proper17:30
opendevreviewClark Boylan proposed opendev/system-config master: Update gerrit images to 3.10.7 and 3.11.4  https://review.opendev.org/c/opendev/system-config/+/95539517:32
fungiyeah all that looks fine to me17:32
clarkbI couldn't rebase things because that will restart the testing of 882900 so I did a depends on instead17:32
fungiwfm17:33
clarkb955395 doesn't appear to trigger the gitea job so I think we could sneak it in today without losing a bunch of time if we think that is safest17:34
fungii'm okay with it either way, and can stick around later if needed too, i don't have any evening plans other than cooking dinner at some point17:35
opendevreviewClark Boylan proposed opendev/system-config master: Update gerrit images to 3.10.7 and 3.11.4  https://review.opendev.org/c/opendev/system-config/+/95539517:35
clarkbactually I realized that I should force an image rebuild for publication purposes and edited the change. Not sure if gitea is triggered now17:35
clarkbnope that still doesn't cause it to do gitea things17:36
clarkbfungi: I think the main reason to try and get 955395 in as well is simply to ensure the plugins all match the gerrit core version. There may be something we don't understand in that replication change log that is important (though that seems unlikely)17:37
clarkband ya its only 10:37am local time here. Maybe we should just get this out of the way too. Otherwise its another wait for a good time to restart gerrit loop17:37
clarkbso I think I'm leaning towards including 955395 in the restart as well17:37
fungii'm good with that plan17:39
fungiand already +2 on the change17:40
fungii guess i can go ahead and approve it17:40
clarkbits interesting that in the zuu.l queue it still says it is waiting on repo state17:40
clarkbI wonder fi that depends on has confused something?17:41
clarkbthough it has the jobs figured out so in must've merged something17:41
clarkbnow it is running jobs. I just needed to be patient17:47
fungiintermittent failure pulling haproxy container images? https://zuul.opendev.org/t/openstack/build/be5d9e300ed7429799840d594a2cf44417:58
fungihard to tell from the log whether it was haproxy or haproxy-statsd that hit it17:59
clarkbyou may be able to tell by looking up the blob hash to see which image it belongs to. We're mirroring haproxy to quay.io but haproxy-statsd is still on docker hub18:07
clarkbI just pulled both locally and they both worked18:09
clarkb3da95a905ed5 belongs to haproxy18:09
fungiah okay18:09
clarkbmaybe a hiccup with quay ?18:10
clarkbor possibly a race with our mirroring jobs? THough those run periodically and should've been done for hours by the time this job ran18:10
mnasiadkaWhile we’re at mirroring - any chance to get reviews on https://review.opendev.org/c/opendev/system-config/+/954703 ?18:19
clarkbhttps://review.opendev.org/c/opendev/system-config/+/954978 is the other change on my backlog for this week. This one checks afs is mounted before starting zuul executor containers during weekly updates. Not sure that is urgent but probably worth doing at some point18:19
opendevreviewMerged opendev/system-config master: Migrate gerrit images to quay.io  https://review.opendev.org/c/opendev/system-config/+/88290018:35
opendevreviewMerged opendev/system-config master: docker-mirror: Add Ubuntu 24.04 and Debian Bookworm/Trixie mirrors  https://review.opendev.org/c/opendev/system-config/+/95470318:36
clarkbthe quay.io image builds promoted to quay.io and skimming https://quay.io/repository/opendevorg/gerrit/manifest/sha256:92c6933f69e3c0c5cca3013453308de11fb9f36288cbaf8839d71d71a823072d the python version is 3.12 in there so I'm like 99% certain we used the correct base image to build that image18:40
clarkbat this point I think we could restart with the original planned set of changes. The 3.10.7 change just entered the gate though. SO maybe we aim for more of a 2000 UTC restart cc fungi18:41
clarkbI am happy that my original estimate was reasonably accurate until we added another change to the list18:41
clarkbthat gives me time to eat lunch first too so I'm happy18:41
opendevreviewMerged opendev/system-config master: Wait for AFS to mount when rebooting executors  https://review.opendev.org/c/opendev/system-config/+/95497818:48
fungisounds fine to me18:51
opendevreviewJeremy Stanley proposed opendev/system-config master: Fix indentation on Gitea splash page  https://review.opendev.org/c/opendev/system-config/+/95240719:17
opendevreviewJeremy Stanley proposed opendev/system-config master: Hyperlink service icons on Gitea splash page  https://review.opendev.org/c/opendev/system-config/+/95240819:17
opendevreviewJeremy Stanley proposed opendev/system-config master: Link Rackspace donor logo to testimonial article  https://review.opendev.org/c/opendev/system-config/+/95286119:17
fungii expect those ^ should probably be squashed once people are satisfied with them individually, so as to not churn our gitea services with unnecessary restarts on deploy19:22
clarkb++19:23
clarkbmanage projects for 882900 is still running. load on gitea13 is similar to what it was before so I'm not super concerned it should eventually complete19:24
clarkbbut it has created a small deploy traffic jam we may wish to wait for completion of before starting gerrit restarts later (assuming they aren't done by then)19:25
fungisure, makes sense19:25
fungideploy reported for 882900 (success)19:32
opendevreviewMerged opendev/system-config master: Update gerrit images to 3.10.7 and 3.11.4  https://review.opendev.org/c/opendev/system-config/+/95539519:35
clarkblooks like everything has deployed according to zuul19:45
clarkbpulled the image locally which matches what I see in quay.io and it appears to have the correct content in it19:49
clarkb(I just checked the timestamp on the python3 binary and its newer than the years old old base image on quay)19:49
clarkbfungi: so I think our process for restarting gerrit is going to be `docker compose pull; docker inspect $imageid and confirm it matches latest on quay ; then send an announcement; docker compose down ; move gerrit waiting replication queue dir aside / delete it; delete large gerrit h2 caches ; docker compose up -d ; then after things are running initiate reindexing of changes19:50
fungiassuming we're going to want a root screen session on review, i've started one19:51
fungiand that sequence lgtm, i can start the pull19:51
clarkbgerrit_file_diff and git_file_diff appear to be the caches to be worried about this time19:51
clarkbfungi: I've attached to the screen.19:52
fungiquay.io/opendevorg/gerrit       3.10      2e7da5290a2d   54 minutes ago19:52
fungiprevious one from dockerhub looks like 50502a8647b519:53
clarkbfungi: ya so if you `docker inspect 2e7da5290a2d | grep RepoDigests -A 1` that should show you a digest that matches https://quay.io/repository/opendevorg/gerrit/manifest/sha256:c931c215a837a0bd51133eb57f3ef6fbc930300e177c746ed4d5ccca9d3db8ec19:53
fungiquay.io/opendevorg/gerrit@sha256:c931c215a837a0bd51133eb57f3ef6fbc930300e177c746ed4d5ccca9d3db8ec19:54
fungiyep19:54
clarkband ya the current container appears to be running off of 50502a8647b5 (noting that in case we have to revert)19:54
clarkbcool that is also the image I checked looking and looked correct after a brief a glance19:55
clarkbso I think I'm ready to proceed whenever you are. Do we want ot wait for the hourly jobs to run in about 5 minutes first?19:55
fungistatus notice The Gerrit service on review.opendev.org will be offline briefly for a configuration and version update, but should return to service momentarily19:55
fungisomething like that? ^19:56
clarkb++19:56
fungiand yeah, let's wait for hourlies to finish19:56
fungiand they're enqueued now20:01
clarkbshouldn't be long20:02
clarkbthe queued command looks correct to me20:03
clarkbthose cache names seem to match the two I pasted above in here20:03
fungicool, it's apparently basically the same thing i ran for a restart in may, sans the date on the file copy20:03
fungishould i go ahead and do the status notice now or wait for the hourly jobs to get closer to done?20:04
clarkbya I think we can send it now20:04
clarkbalso we need to be careful about the difference between opendevorg/gerrit and opendevmirror/gerrit20:05
fungi#status notice The Gerrit service on review.opendev.org will be offline briefly for a configuration and version update, but should return to service momentarily20:05
opendevstatusfungi: sending notice20:05
clarkbin this case I believe we've got the correct string and are using opendevorg's gerrit not the gerrit gerrit mirrored in opendevmirror20:05
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline briefly for a configuration and version update, but should return to service momentarily20:05
clarkbI just wanted to call that out as a potential mixup gotcha20:05
fungiyeah20:05
opendevstatusfungi: finished sending notice20:08
clarkbhourlies are finishing up too20:08
clarkbthey are gone (so done)20:08
clarkbI'm ready if you are20:08
fungiokay, starting20:09
clarkbI'm going to be sad if this shutdown takes 5 minutes20:09
fungiyeah20:09
fungiit's still taking far longer that i was expecting after we dropped the db pruning20:10
fungi78 seconds20:10
fungiit should be on its way back up now20:10
clarkbat least it didn't timeout and it shutdown on its own (so sigint is working)20:10
fungiPowered by Gerrit Code Review (3.10.7-1-g5f52a4e3d5-dirty)20:11
fungiwebui is up and responding20:11
clarkb[2025-07-18T20:10:41.373Z] [main] INFO  com.google.gerrit.pgm.Daemon : Gerrit Code Review 3.10.7-1-g5f52a4e3d5-dirty ready20:11
clarkbanyone have a change/patchset to push up? We'll be able to verify replication and pushes work afterwards20:11
fungii see file diffd20:11
fungidiff20:11
fungis20:12
clarkbya I see diffs as well20:12
fungii don't have anything to push (should have saved some of the updates i was working on a few minutes ago but didn't think about it)20:13
fungii'm tailing the gerritbot log though20:13
clarkbI've started digging through my backlog but we just merged all of them :)20:13
clarkbI think there is a new gitea release. I'll push a change for that20:14
fungilooks like gerritbot gets flooded by replicaton events20:14
clarkbya those are normal on the event stream iirc20:15
opendevreviewClark Boylan proposed opendev/system-config master: Update to gitea 1.24.3  https://review.opendev.org/c/opendev/system-config/+/95541120:17
clarkbhttps://opendev.org/opendev/system-config/commit/e03b19448e80d9833fbe19778eb7f4f5ec22b7ba I think replication is working (as is my push)20:18
clarkbfungi: anything else you think I should check on?20:18
fungino, everything looks fine to me20:18
fungi953624,1 is about 10 minutes from merging, i forgot that was likely to result in a gitea redeploy20:19
fungi(updating the well-known file for element/matrix)20:19
clarkbthats probably fine. The main thing is gitea13 has been busy20:19
clarkblunch actually arrived late so I'm going to eat that quickly now. But I'm around this afternoon and can monitor that gitea deployment and ensure the 1.24.3 change doesn't need more updates20:20
clarkboh right we need to reindex changes for that 78s shutdown period20:20
clarkbfungi: ^ do you want to trigger that or should I?20:20
clarkb`ssh -p 29418 admin@review.opendev.org gerrit reindex start --force changes` is the incantation I believe20:21
clarkbs/reindex/index/20:22
fungii can20:23
fungiit's just "index" not "reindex" but close!20:24
fungianyway it's running now20:24
clarkbfungi: I just saw a traceback for an openid login attempt20:26
clarkbbut it is for elastic recheck20:26
clarkbsomething that I don't expect to acutally succeed at auth. Do you think you should login as fungi3 and double check login works typically?20:27
clarkbI should really set up the test account for myself already20:28
fungii think i did something a while back that broke that test account when playing around with merges and the like, but i can certainly try logging in with my normal account20:30
fungisigned in successfully20:31
clarkbok thanks. I think the issue is on whatever is trying to log in as that account (we haven't used it in a long time)20:31
fungiinterestingly, my name shows up in all-caps in the top-right corner now, i don't recall it appearing that way in the past20:31
clarkbdoes for me as well. If I click on my name for the drop down to get settings etc it shows my name with normal casing20:32
clarkbI can't remember if this is new behavior. I awnt to say it may have done this for a while20:32
clarkbreindexing is about 1/4 of the way done20:33
clarkbI detached from the screen and will let you decide when it can be shutdown20:33
fungithanks, i think we can tear it down safely. i'll do that now20:35
clarkbonce reindexing is done I'm going to look at some local network updates. The one thing I've noticed switching from pfsense to opnsense is that opnsense is much more consistent about regular updates20:38
clarkba good thing but I also don't want to fall behind20:38
opendevreviewMerged opendev/system-config master: Update .well-known/matrix/client for mobile OIDC  https://review.opendev.org/c/opendev/system-config/+/95362420:42
opendevreviewClark Boylan proposed opendev/system-config master: Add iptables rule blocks to drop traffic from specific IPs  https://review.opendev.org/c/opendev/system-config/+/95541420:54
clarkbfungi: I think gitea is serving the updated matrix client well know data20:56
clarkbgitea itself was not restarted20:56
fungiah good, the deploy is smart enough not to restart gitea unless the image contents change20:57
clarkbfungi: in https://opendev.org/opendev/system-config/src/commit/f4c176ebdf26746744f6caae0df540ae48f99429/playbooks/roles/iptables/templates/rules.v4.j2#L28 is the `-p {{ host.protocol }}` a bug? or does the --dport rule ensure that we're checking the correct port?20:57
clarkbI guess I'm confused over why we have both -p and --dport specified there. As written it would do something like -m tcp -p tcp -s some.add.res.s --dport 8443 -j ACCEPT20:58
fungii think the module and protocol are separate options20:59
clarkb[2025-07-18T20:56:55.488Z] [Reindex changes v86-v86] INFO  com.google.gerrit.server.index.OnlineReindexer : Reindex changes to version 86 complete20:59
clarkbfungi: gotcha20:59
fungiclarkb: or are you confusing the -p (protocol) option with --dport (destination port)?21:00
clarkbthree changes failed to reindex. Same number as before and they were all old changes that I Think we expect this from unfortunately21:00
clarkbfungi: ya I guess I'm confused since -p also takes a protocl number21:00
fungifwiw, this is way simpler with netfilter, if we ever redo our rules21:00
clarkblike maybe we have some redundancy in there but I guess saying tcp twice and then finally filtering on port whatever is workable21:00
fungiit's saying iptables should use the tcp module with the tcp protocol21:01
clarkbgotcha21:01
fungii don't know if the tcp module supports additional protocols besides tcp, but our rules assume it doesn't21:02
clarkband for the drop rule we don't care about tcp or udp or whatever so don't need any of that just the source ip address21:02
fungiright21:03
clarkbthanks for double checking21:04
fungicould argue for rejecting connections with icmp admin-prohibited errors instead or something, but in cases where you're blocking spoofed attackers that's bad and enables reflection attacks or inadvertent backscatter21:04
clarkbI think the stuff we had in flight is looking happy at the moment so I'm going to proceed with local network gear updates21:04
clarkbfungi: yup that is why I didn't use reject21:04
fungi[insert thumbs-up emoji here]21:05
clarkbthen next week I guess I'm diving into gerrit 3.11 upgrade prep properly21:08
clarkbthat was quick. I like that updates come more frequently so that the update process itself is better exercised21:20
clarkbhttps://687a0a9b9a79cc21edde-9d697031d66865af8e6eba8e2a3ea98e.ssl.cf1.rackcdn.com/openstack/89bf4bb7cd59426db4e8c920c923fdbf/bridge99.opendev.org/screenshots/ gitea 1.24.3 screenshots look good21:25
clarkbI'm not in a rush to do that upgrade and we can probably wait for monday21:25
clarkbMostly I'm worried that gitea13 might have a sad21:25
fungiyeah, seems like a good idea this close to everyone's weekend21:26
clarkbwe got a fair bit done. Gerrit should be all caught up on the backlog of issues surrounding it which is nice. We also confirmed that sigint works but it is still somewhat slow. I did start running a strace but I couldn't confirm the file number mapping via lsof before it stopped21:28
clarkbI suspect its still trying to deal with those large db files on shutdown21:28

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