Thursday, 2025-04-10

opendevreviewClark Boylan proposed opendev/system-config master: Update Etherpad to 2.3.0  https://review.opendev.org/c/opendev/system-config/+/94684200:19
opendevreviewClark Boylan proposed opendev/system-config master: Update Etherpad to 2.3.0  https://review.opendev.org/c/opendev/system-config/+/94684200:40
*** ykarel_ is now known as ykarel06:00
opendevreviewJaromír Wysoglad proposed openstack/project-config master: Add jobs for new Aetos repository  https://review.opendev.org/c/openstack/project-config/+/94674207:25
opendevreviewMerged openstack/project-config master: Add jobs for new Aetos repository  https://review.opendev.org/c/openstack/project-config/+/94674212:34
fungi/opt/backups-202010 on backup02.ca-ymq-1.vexxhost has reached 91% utilization, so i've initiated a prune in a root screen session just now13:33
*** noonedeadpunk_ is now known as noonedeadpunk13:35
*** dxld_ is now known as dxld13:36
*** frickler_ is now known as frickler13:48
*** sean-k-mooney1 is now known as sean-k-mooney14:17
fungi#status log Pruned backups on backup02.ca-ymq-1.vexxhost reducing volume usage from 91% to 63%14:26
opendevstatusfungi: finished logging14:26
opendevreviewClark Boylan proposed opendev/system-config master: Update Etherpad to 2.3.0  https://review.opendev.org/c/opendev/system-config/+/94684214:50
clarkbscreenshots do seem to show adding the = suffix on vars unsets our initial default value14:50
clarkbhopefully screenshots show that latest patchset corrects the problem14:50
opendevreviewClark Boylan proposed opendev/system-config master: Add new Noble review03 to the inventory  https://review.opendev.org/c/opendev/system-config/+/94663714:55
clarkbI added review03 to the backup group in ^ but otherwise the change is the same. I think today is a decent day to land that and monitor nothing unexpected happens then we have tomorrow and/or early next week to start testing the move.14:56
clarkbProbably worth sending an announcement tomorrow with a plan to swap servers a week later and if we don't make that time frame oh well we can update teh announcement14:56
clarkbfungi: re the release notes -37 quirk zuul addressed that by labelling those as "In Development" set via the :unreleased-version-title: value to the reno release-notes sphinx extension15:06
clarkbhttps://codesearch.opendev.org/?q=unreleased-version-title&i=nope&literal=nope&files=&excludeFiles=&repos= maybe openstack should consider adopting that15:07
* JayF sciencing this with ironic release notes15:10
JayFHm, I either did it wrong or misunderstood twhat that means15:14
clarkbJayF: https://zuul-ci.org/docs/zuul/latest/releasenotes.html#in-development it should do that instead of 11.3.0-37 or whatever15:15
JayFI assume this isn't enough, is what I mean  https://www.irccloud.com/pastebin/abdeczED/15:16
JayFnothing changed in the built output15:16
clarkbyou set it when you call the extension. My codesearch link above has examples15:16
JayFOH15:17
clarkbthere may be a way to use conf.py too but that isn't how anyone else has done it15:17
JayFI'm sorry, I probably don't misdo this if not PTG brained :| 15:17
JayFI ran out of brain sometime midday Wednesday ;) 15:17
gouthamrwoah meetpad recordings can be longer than 60 mins? :) pleasant change!15:18
clarkbgouthamr: I think its limited by your browser's max file size for writing15:19
clarkbthe estimate is 60 minutes to be on the safe side15:19
gouthamroh, i never knew that.. 15:19
fungiclarkb: JayF: yeah, we do the same thing in bindep too: https://opendev.org/opendev/bindep/raw/branch/master/doc/source/releasenotes.rst15:19
clarkbfungi: ya codesearch found a number of examples. reno does it for itself too15:19
fungigouthamr: right, starting a new recording hourly 1. helps you exclude the dead air for hourly breaks, and 2. avoids having the recording end unexpectedly when it reaches your browser's limit15:20
gouthamrfungi: yes totally, i forgot to end a recording, and it kept running so was pleasantly surprised 15:26
clarkbgouthamr: I want to say the limit is 1gb but I haevn't found any documentation of that from chrome directly. That means you could theoretically watch the file size and wait for it to near that limit before stopping15:30
clarkbbut again I am not 100% certain of that limit15:30
clarkbhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_aee/openstack/aee2dc3b790c4c53b88d434786c23bb3/bridge99.opendev.org/screenshots/etherpad-pad.png success15:34
clarkbwe should probably still hold a node and sanity check things work as expected with chat and editor colors and so on15:35
clarkband all of tha should wait for the ptg to complete15:35
JayFthank you! it looks much better, will propose it to Ironic https://usercontent.irccloud-cdn.com/file/IMxIU3Ia/image.png15:41
clarkbhttps://docs.openstack.org/releasenotes/ironic/unreleased.html for comparison15:44
clarkbhttps://docs.openstack.org/releasenotes/ironic/2024.2.html or maybe that is better comparison since it shows a more confusing case of unreleased code having a version15:45
clarkbyour old anchors may break too but I think that is fine as every new commit breaks the anchors anyway so this is an improvement that makes them stable15:45
clarkbok https://review.opendev.org/c/opendev/system-config/+/946637 passes testing after adding review03 to the backup servers list15:50
opendevreviewTim Burke proposed opendev/irc-meetings master: swift: Fix meeting cadence  https://review.opendev.org/c/opendev/irc-meetings/+/94693815:57
opendevreviewMerged opendev/irc-meetings master: swift: Fix meeting cadence  https://review.opendev.org/c/opendev/irc-meetings/+/94693816:23
clarkbfungi: do you think you might have time to look at the review03 inventory change? ianw weighed in on the older patchset and said it looked fine and the new patchset was a minimal change17:46
clarkbif you think it is mergeable I expect ot be around all day today and can help monitor17:48
fungichecking17:50
clarkbthe discussion on https://etherpad.opendev.org/p/i_vt63v18c3RKX2VyCs3 is related too17:51
clarkbessentially the idea is we add a new gerrit server that should get configured but not turn on any services17:53
clarkbthen we can synchronize things between servers and turn things on for testing. Then we can schedule a downtmie to do an actual switch synchronization and migrate servers17:54
fungiis there a pending change for post-cutover things like reenabling reeplication? i don't see it as a todo step in the pad either17:54
clarkbno not yet17:55
fungii assume most other stuff will be handled by moving it from review-staging to review hostgroup17:55
clarkball review-staging changes is the manage-projects playbook17:56
clarkbthat playbook excludes the review-staging group17:56
clarkbbut yes one of the things we will need to do as part of the actual move is configure replication on the new server17:56
clarkbwe don't configure it now because we don't want the new server accidentally overwriting git content on giteas17:57
fungiso where are things like gerrit init/startup and git cg cron disabled for it?17:57
fungis/cg/gc/17:57
clarkbthe gerrit role disables gerrit init and startup by default17:57
clarkbthe gc cron won't be disabled I don't think17:57
fungioh, okay so not something explicit here17:57
clarkbhttps://opendev.org/opendev/system-config/src/branch/master/playbooks/roles/gerrit/defaults/main.yaml#L5-L817:58
fungioh, never mind, the commit message mentioned gerrit reindexing and my mind substituted git gc17:58
clarkbhttps://review.opendev.org/c/opendev/system-config/+/946637/3/inventory/service/host_vars/review03.opendev.org.yaml is a copy from review02 with the cert names updated and replication removed17:59
clarkbthen we're relying on defaults otherwise17:59
clarkbthough it just occurred to me before we land that we need to make sure secrets on bridge are set up for it17:59
fungiso the things the commit message says it doesn't do are things the gerrit role already doesn't do17:59
clarkbwhich I even have as a pre step in the ehteprad. I'm going to go look at that now17:59
clarkbfungi: yes, unless explicitly enabled18:00
clarkbwe do use those features for the test job and maybe when we rename repos with the playbook. I'm not sure about renaming repos18:00
fungithat explains why they didn't seem to be explicitly disabled (other than the empty replication config)18:00
clarkbI put it in the commti message to call out that is the expected behavior. But reviewers should double check that expectation is carried through by the ansible18:03
clarkblooks like we use host specific vars for secrets rather than group vars18:04
clarkblooking at the existing vars for the old server I think we want to just make a straight port over18:05
clarkbso I'll do that now18:05
clarkbwe have host keys lsited for the old gitea servers. I will clear those out. There is also some old info in there for github replication that we shouldn't need and openstack watch but I think cleaning that up should happen separately to this effrot. Enough moving parts already18:06
clarkbok secret vars should be in place now. I also checked that review02 doesn't show up as a string in any of those vars that would need updating (it doesn't)18:10
clarkbfungi: looks like you +2'd I guess if you'r comfortable with those assertions about how this is safe and the secret vars check out to you we can probably proceed?18:12
fungiyes18:13
fungii didn't know whether you were waiting for more feedback from anyone else18:13
clarkbI mean it is the sort of thing that more feedback on is always nice to have18:14
clarkbbut I'm also concerned that if I wait for more I'll be waiting for a long time18:14
fungii'm fine with moving ahead so we can make progress sooner18:14
clarkband ianw did review the change earlier18:14
clarkbcalled out https://review.opendev.org/c/opendev/system-config/+/783183 as a similar one the last time we did this18:15
clarkbI do notice the host vars in ^ had a lot more content than I added for review0318:15
clarkblet me track down where those are now set18:15
clarkbI think the bulk of them migrated into https://opendev.org/opendev/system-config/src/branch/master/inventory/service/group_vars/review.yaml and gerrit_database_type is not h2 we use mariadb18:16
clarkbso that explains that on18:17
fungigood improvement, we've centralized the stuff that can be safelty18:17
fungisafely18:17
clarkbya18:17
clarkblunch is fast approaching. We can sit on it until then in case any other brain light bulbs go off or anyone else reviews it then approve after18:17
fungisgtm18:18
clarkbafter it applies I think the main things to check are that the service is actually down, that it didn't magically conjure a replication config and that if/when manage-projects runs it ignores this server as expected. If it doesn't ignore the server then we'll have manage-projects running from both review02 and review03 against review0218:18
clarkbI suspect 90% of the time that would be fine (updating acls or nooping daily). The main issues would be creating new projects18:19
clarkbso maybe we add it to inventory and avoid creating new projects until afte we've confirmed review03 is ignored as expected18:19
clarkband I'm more than happy for people to poke holes in this approach/plan18:20
clarkbI'd rather get it right and be prepared then rush in and deal with unexpected issues18:20
clarkbside note the servier id uuid value must match between the wto servers for gerrit to treat the notedb content from the old server as valid18:20
clarkbI guess this way you can move a repo into a new gerrit and leave its old notedb content behind if you don't want to port the changes in?18:21
clarkbfungi: I see now the comment in the groups file about review-staging says it disables replication, but I can't find any evidence of it doing that18:30
clarkbthe only thing I can see it doing is excludingservers in review-staging from running manage-projects18:30
fungimaybe it used to18:37
fungilike in the pre-plugin days or something18:38
clarkbpossible18:38
clarkbI think the way to do that would be to check if we are in the review-staging group and use that to write out or not the replication config?18:38
clarkbanyway writing an empty list of replication targets should be sufficient18:39
fungithat would be the most sensible approach18:39
fungibut this also works18:39
fungiand yeah, i confirm that the only reference to the review-staging group is its exclusion for tasts in the manage-projects playbook18:40
fungiso i don't see any way that part of the comment can be correct18:41
clarkbor maybe that was the intention then was never implemented as the empty list approach should be sufficient18:41
fungiappears that comment was added with https://review.opendev.org/c/opendev/system-config/+/780698 in 2021 which only implemented the bits we have now18:42
clarkbok I'll pop out for lunch in a few minutes. Then we can approve at 19:45 UTC probably if there are no other new concerns18:45
clarkbinfra-root ^ fyi that is the plan for adding review03 to the inventory18:46
fungiperfect18:46
clarkbraise concerns now if you have them :)18:46
clarkbas an extra sanity check i quickly checked if gerrit_replication is defined in secret vars (it is not). Also it looks like we will write out the replication config file but it should only contain the top level options and no replication targets19:28
clarkbso that all continues to look good to me19:28
clarkbfungi: I'm done eating a little early. Happy for that to be approved now if we're ready. We have a bit of time until it merges too if anything else comes up.19:30
fungiapproved19:31
clarkbshoudl finish up right around 1900 UTC19:38
fungii've got a summit session to lead starting at 2100 utc, but that's plenty of time to help check stuff19:39
clarkbespecially with our much quicker runtimes19:39
fungiso very, very nice...19:40
fungioh, actually when you said "should finish up right around 1900" it was already 19:39 utc19:55
fungiguessing you meant 20:0019:55
clarkboh yes I did19:56
fungibut yeah, it's on track to merge in about another 5 minutes per zuul's estimate. that'll put it behind the hourly jobs, so deploy is unlikely to happen until closer to 20:20 i'm gussing19:57
fungiguessing19:57
clarkbhourlies sjust queued up so this will go after them20:01
opendevreviewMerged opendev/system-config master: Add new Noble review03 to the inventory  https://review.opendev.org/c/opendev/system-config/+/94663720:08
clarkbhourlies are just finishing up too so that should start almost immediately20:08
clarkbyup there it goes20:09
clarkbservice-review and manage-projects are near the end20:09
clarkbso far backups have been configured and there is an LE cert20:35
clarkbthe job to actually configure it as a gerrit just started20:35
fungiyeah, and infra-prod-manage-projects is going now20:39
fungiwhich should skip the server20:39
clarkbya we need to look at logs on bridge to confirm20:39
clarkbfwiw review03 is running apache but not the backend services according to docker ps -a20:39
clarkbso I think review03 did as expected20:40
fungiand if manage-projects tries to run on it, we should see the job fail anyway20:40
fungias the api isn't up20:40
clarkbfungi: no, I noted this in the etherpad but manage-projects is configured to talk to review.o.o not localhost20:41
fungiah, right, so it would connect from 03 to 0320:41
fungier, to 0220:41
clarkbso it would talk to review02 which is potentially problematic if we have review02 and review03 both running manage-projcst at the same time. I think it is ok in the noop case and maybe even in the update acls case20:41
clarkbthe create a new project case is the one that worries me, but this run should noop and we can confirm it is skipped entirely in the safe noop case20:42
clarkbmanage projects log on bridge lgtm20:42
clarkbthere are tasks for review02 but not for review03 and the play summary doesn't even include review0320:43
clarkbeverything I've seen so far looks good to me20:43
clarkbthe next step will be syncing data and potentially starting up gerrit to test (I need to think about how safe that is if we resync later. I think it is fine if we overwrite on the target which is scary but something we probably have to do anyway)20:44
clarkbmaybe tomorrow we can start piecing together the sync20:44
clarkbfungi: before we call this done it would be good if you can double check the manage project log just to confirm20:44
fungiyeah, i have it open already20:45
fungithe play recap shows it ran against the 6 gitea servers and review02, but no mention of review0320:46
fungiso bridge didn't contact the new server for that20:47
clarkbthat was my read too. searching for review03 doesn't show anything20:47
clarkband if you check the timestamp on the file its from 20:42 which is new enough to have review03 in the inventory (just calling that out as old logs would not have review03 in them as the server didn't exist then)20:47
fungiagreed20:48
fungiwell, i mean, i was also tailing it as the job ran20:48
clarkbanother good way to check that :)20:48
clarkbso ya I think we're in good shape to finish modling this new server into the new review20:49
clarkbbut you've got a ptg session in 10 minutes so I'm good with pausing here and picking it up again tomorrow20:49
clarkbin the meantime I'm going to work on holding a test etherpad server for that etherpad upgrade20:49
fungicool, i'll be running a ptg session starting in a few minutes20:51
fungibut can probably take a look at etherpad upgrade test results in a little over an hour20:51
opendevreviewClark Boylan proposed opendev/system-config master: DNM force etherpad failure to hold node  https://review.opendev.org/c/opendev/system-config/+/84097220:51
clarkband maybe we upgrade etherpad tomorrow after the ptg. Removing meetpad servers from the emergency file will alos upgrade meetpad when the ptg is over20:52
fungiyeah, that'd be great20:54
clarkbthe held etherpad test server will be at 213.32.76.19121:24
clarkbtimburke: was the swift epoxy release the first one without python2.7 support?21:39
fungii half expected there to already be content in the clarkb-test pad on the held node22:12
fungihttps://etherpad.opendev.org/p/testing has surprising content22:12
fungioh, i bet that's something we inject via testinfra22:13
fungibased on the timestamps in the timeslider22:14
fungibingo: https://opendev.org/opendev/system-config/src/branch/master/testinfra/test_etherpad.py#L5822:14
clarkbyes it is22:15
clarkbsorry I'm doing a small errand but then will test the held node too22:15
fungino worries, take all the time you need22:15
fungii just wanted to poke at it before my evening gets in full swing22:15
clarkbare you using the testing pad then?22:18
fungihttps://etherpad.opendev.org/p/fungi22:18
fungiordered lists aren't incrementing22:19
fungican you try an ordered list test too, make sure it's not something up with my browser?22:20
clarkbsure22:21
clarkbI think it works but I used incognito tabs to avoid caching problems since we're hijacking /etc/hosts22:22
clarkbI shutdown the crhome tab. I think this is working22:24
fungiokay, that's weird, when i followed an unordered list with an ordered list it resumed an earlier ordered list test22:24
clarkbi wonder if the existing server does that22:25
clarkbI can confirm I get the same behavior22:25
clarkblet me jump off the test server and check if this happens on the existing server22:26
clarkbhttps://etherpad.opendev.org/p/opendev-server-replacement-sprint bottom of that pad reproduces the behavior so this isn't a new bug22:27
fungiyep, good enough by me then22:28
clarkbI'll take it if thats the worst issue we can find :)22:28
fungiso i think we're still on track to upgrade after the ptg22:28
fungino obvious blockers22:29
clarkb++22:29
clarkbjitsi meet made a new release not too long ago too. We would've updated twice22:29
clarkbI'm glad we put the hosts in the don't touch for now list22:29
fungiyep22:30
fungiclarkb: i reproduced the other ordered list behavior i saw on the version we're currently running too: https://etherpad.opendev.org/p/testing22:36
fungii think it wants to continue ordered lists which are interrupted by an unordered list, but when there is no prior ordered list present it gets... confused? maybe?22:37
clarkbyou think its the same issue in both cases?22:45
clarkbfungi: https://github.com/ether/etherpad-lite/issues/516022:50
clarkblooks like john has had good weather :)22:51
clarkbthat is the first issue. Not claer to me if it is the same issue as numbers continuing on though. Probably are related at least22:51
fungiyeah, my guess is the two are related23:02
fungilooks like he implemented a testcase, but no fix23:04

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