Tuesday, 2025-07-08

ykarelthanks fungi clarkb 03:51
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:13
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:18
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:19
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:36
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:37
opendevreviewClark Boylan proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429904:42
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:42
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:46
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346004:47
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426504:55
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426504:56
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: limit-log-files: allow unlimited files  https://review.opendev.org/c/zuul/zuul-jobs/+/95385404:59
opendevreviewLukas Kranz proposed zuul/zuul-jobs master: limit-log-files: allow unlimited files  https://review.opendev.org/c/zuul/zuul-jobs/+/95385404:59
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426505:32
*** liuxie is now known as liushy06:06
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429907:08
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346007:08
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426507:08
opendevreviewDr. Jens Harbott proposed opendev/zuul-providers master: Add debian-trixie build  https://review.opendev.org/c/opendev/zuul-providers/+/95147107:15
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429907:31
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346007:31
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426507:31
mnasiadkaclarkb: I took the liberty to update your patch, the whole stack up to RL10 looks green now08:50
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429909:12
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346009:12
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426509:12
noonedeadpunkhey folks! It seems that for some reason we got debian-bullseye jobs quite broken now: https://zuul.opendev.org/t/openstack/build/0bf15350542c440899581cd1b90c73cc09:58
noonedeadpunkI wonder if that could be due to merge of https://review.opendev.org/c/zuul/zuul-jobs/+/95428009:59
noonedeadpunkas we were relying on backports being absent there: https://opendev.org/openstack/openstack-ansible/src/branch/master/zuul.d/jobs.yaml#L4209:59
noonedeadpunkI think we need a hold here to figure out on how to workaround difference in "plain" image with CI image10:01
noonedeadpunkand bookworm for the same change passes nicely: https://zuul.opendev.org/t/openstack/build/5539b78bfa4d4c19a13cf37666f6bc2210:08
jrossernoonedeadpunk: i dont think 954280 is merged yet10:48
noonedeadpunkoh, I was sure I saw it as merged.... but it's obviously not10:53
noonedeadpunkmy bad10:53
noonedeadpunkbut it could be that we'd still need some hold... as etc folder is not gathered for some reason, so apt update failure is not clear at all11:00
funginoonedeadpunk: no, backports have ~always been enabled in our images (going back at least 7-8 years as far as i was able to trace), but when we switched to building images with zuul jobs recently the default package mirror baked into the images switched to not being reachable from most clouds. normally that isn't a problem because jobs swap the package mirror hostname out to the one13:08
fungifor the region where the nodes are booted, but we had a useless toggle in that role that allowed jobs to skip updating the mirror hostname for the backports suite sources, leading to that error13:08
fungiin the prior nodepool-built images, that problem was overlooked because apt updates were hitting a reachable mirror address for the backports package indices even if they were in a different cloud provider on the other side of the planet13:10
noonedeadpunkyeah, I somehow saw patch being merged while it's not, so we're having an unrelated issue with bullseye right now13:32
funginoonedeadpunk: have a link to the failing build?13:43
noonedeadpunkhttps://zuul.opendev.org/t/openstack/build/0bf15350542c440899581cd1b90c73cc13:49
noonedeadpunksure, posted it in a first message13:49
noonedeadpunk`Failed to update apt cache: unknown reason`13:49
fungiah, hard to know for sure if it doesn't log the stdout from the underlying commands it's running13:50
fungiso it certainly could be the same problem13:51
noonedeadpunkbookworm does pass at the same time13:53
fungidid it run in rax-dfw?13:53
fungiif it did, it would be able to reach the baked-in mirror address13:54
opendevreviewElod Illes proposed openstack/project-config master: [release-tools] Improve tagging logs  https://review.opendev.org/c/openstack/project-config/+/95434013:54
fungiclarkb: i actually thought of a question for https://review.opendev.org/954280 (see comments)13:59
noonedeadpunkyeah, so https://review.opendev.org/c/openstack/openstack-ansible/+/954339 seems to work indeed14:40
noonedeadpunkso it indeed might be related14:40
fungiworth noting that option never did what the documentation implied, it wasn't actually disabling the backports source, it was just skipping updating it to use the local mirror14:46
clarkbmnasiadka: thanks for frickler's suggestion maybe we do that in a followup since the stack is now green? I left that in a comment on my change14:46
clarkbfungi: I've responded to your question on 95428014:48
mnasiadkaclarkb: can post a followup on top14:55
clarkbmnasiadka: before you do I just posted a note on the EL 10 changes14:57
clarkbmnasiadka: if we decide to udpate those changes then maybe we should update the parent too. Otherwise it can all go in followups I think14:57
clarkbI can go either way now14:57
mnasiadkaclarkb: nested virt rl10 labels would probably be only for naming compatibility from what I understand - because rax classic is the only one that doesn’t support it hardware wise?15:07
clarkbmnasiadka: correct. I think the question is whether or not we feel that explicit naming convention is useful information to convey15:07
clarkbits possible that we think it is redundant and we don't need to update anything15:07
clarkbcorvus: ^ you may have an opinion as yuo've been driving much of the bootstrapping work in niz and deciding what needs to stay and what doesn't15:08
corvusi think i lean toward keeping it.  because .... technically it's orthogonal, it just happens that the only cloud that doesn't support nested virt is the only cloud that doesn't have recent enough cpu flags to run el1015:11
corvusbut i do not feel strongly about that :)15:12
mnasiadkalet me update it, I have a feeling we might omit questions from people using nested-virt labels why is it missing for rl10 ;)15:12
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429915:13
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346015:13
mnasiadkacorvus, clarkb: I see centos 9 stream only has 8GB nested virt label - should I stick to that?15:15
mnasiadkaor 8 and 16?15:15
clarkbmnasiadka: ya I think the nested virt labels are sticking to the legacy format for now at least so only the 8GB is fine I think15:15
mnasiadkaah, there's only 8G nested-virt flavor15:16
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346015:16
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426515:16
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346015:18
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426515:18
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426515:20
mnasiadkaclarkb: I think that should be it ^^15:20
clarkback I'll rereview after the board meeting15:20
corvusi installed python3-virtualenv on zk01 in order to create a personal venv to run zk-shell15:50
corvus...which is borked: ModuleNotFoundError: No module named 'distutils'15:51
clarkbcorvus: that is because python3.12 no longer includes setuptools by default (which vendors distutils)15:51
clarkbcorvus: I think you can fix that by installing setuptools in the virtualenv15:51
corvusthat helps, thanks15:52
fungiyeah, for pbr we recently started listing setuptools explicitly as a runtime requirement (install-requires) because you can't assume it's present any longer15:55
fungianything directly relying on setuptools or things that got moved into it from stdlib (distutils, pkg_resources, et cetera) should explicitly declare a setuptools dependency these days15:56
clarkbmnasiadka: there is a bug in the package normalization change update15:58
clarkbmnasiadka: you can see it in CI job results for the rocky 10 change15:58
clarkbbut I also left a comment15:58
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429915:59
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346015:59
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426516:00
mnasiadkaugh, missed that when applying frickler’s version16:00
corvusthe bug fixed by https://review.opendev.org/954358 has a request stuck.. i will try to manually unstick it.16:03
corvusi fixed it by dequeing the associated change16:05
corvuslooking for more problems, i see a node that zuul thinks has been building for 5 days...  the cloud also thinks that.  so zuul is right, but missing a timeout.16:13
corvushttps://review.opendev.org/954360 should take care of that16:33
stephenfinclarkb: fungi: doesn't have to be a today thing, but if we're able to keep the pbr review train moving along slowly I'd appreciate it https://review.opendev.org/c/openstack/pbr/+/95404116:34
fungiabsolutely! thanks for hacking on it16:35
stephenfinfwiw, I am working on adding a PEP-517 backend and parsing of a tool.pbr section from pyproject.toml, since that seems to be the preferred way to extend setuptools going forward16:35
clarkbI'll put it on the list for reviews this afternoon after the morning block of meetings16:35
corvuslooks like two requests hit the ready-node-assignment race.  i dequeued the change for the second one as well.16:37
corvusi'm going to leave the request for the should-be-timed-out node because that should be self-correcting once https://review.opendev.org/954360 merges and we restart with that.16:38
stephenfinthe only snag I've hit so far is that the finalize_distribution_options hookpoint that e.g. setuptools-scm uses is called *before* setuptools starts pulling stuff from pyproject.toml, meaning we need to implement some degree of parsing this ourselves and can't just rely on setuptools populating distribution for us :(16:38
stephenfinIt should probably have been called initialize_distribution_options...16:38
mnasiadkahmm, I think the rocky9 image is still from 27th May17:07
mnasiadkacorvus: what's the usual workflow? I see that periodic-image-build pipeline did go through at 2AM - but there was no promote job being run after that?17:08
corvusmnasiadka: here's the rocky 9 image status: https://zuul.opendev.org/t/opendev/image/rockylinux-917:12
mnasiadkaah, I didn't scroll down17:12
corvusah yeah, should be sorted by time, recent at bottom17:13
corvusoh and we only need the promote job for gate; the dedicated image-build pipelines create the uploads directly when the buildset is finished17:17
mnasiadkanice17:18
mnasiadkahttps://review.opendev.org/c/opendev/zuul-providers/+/954299 should be good to go finally, the stacked on top centos and rocky patches are now finishing arm64 jobs (converting images from what I see)17:19
opendevreviewMerged opendev/zuul-providers master: Add debian-trixie build  https://review.opendev.org/c/opendev/zuul-providers/+/95147117:23
corvusmnasiadka: ^ oof, conflict just merged17:25
mnasiadkaclarkb, corvus: Although it still seems that Kayobe is missing the cirros image - https://zuul.opendev.org/t/openstack/build/fd2ad8dfcd4b458f9e70bc619a8cfb6f/log/primary/ansible/seed-deploy#13531 - any chance it used the old image?17:25
mnasiadkacorvus: oh boy17:25
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429917:25
fungisorry!17:26
fungi(for approving the conflict i mean)17:26
corvusmnasiadka: https://review.opendev.org/954299 is wip17:27
corvusdoes it automatically do that if you rebase ttw?17:27
mnasiadkayes17:28
mnasiadkajust updating it - sometimes it's faster for me to use the web interface17:28
clarkbI guess it does that beacuse all of the conflict markers are put into the files in the rebase patchset17:28
corvushttps://zuul.opendev.org/t/openstack/build/fd2ad8dfcd4b458f9e70bc619a8cfb6f/log/zuul-info/zuul-info.primary.txt#6  looks like it's the old image17:28
fungihaving not really used gerrit's remote rebase often, i didn't realize they'd changed that17:29
corvusoh heh yeah the conflict markers are in there17:29
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429917:29
fungineat, so maybe only happens if it's a nontrivial rebase?17:29
clarkbya I think it must consider that a staging ground for fixingthem via the web ui17:29
fungiit used to just refuse to rebase in those circumstances, so i guess i'll consider that a sort of feature17:29
mnasiadkabut now clarkb needs to mark it as active since I'm not the owner :)17:30
clarkbon it17:30
clarkbdone17:30
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346017:31
corvusmnasiadka: yeah,  that job ran a few hours before the upload of the new image started.  i have a pending update to the images page that will show the completion time for the image upload; but for now, we can see that it even predates the start of the upload.17:31
opendevreviewMichal Nasiadka proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426517:31
corvusfungi: https://review.opendev.org/954299 could use a +3 from you17:32
priteauRegarding the rocky9 image, I think something must have happened on June 30 or July 1. Before this time, we were using images built on the same day, but now jobs always use an image from end of may17:32
priteauDid something change in the image selection logic?17:32
mnasiadkanodepool to zuul-launcher switch?17:32
clarkbmnasiadka: priteau yes that was the change17:33
priteauThis? https://review.opendev.org/c/opendev/zuul-providers/+/95272117:33
clarkbsince there was the bug in the zuul-launcher image builds that didn't include cirros image caching on images other than ubuntu17:33
mnasiadkapriteau: yup, this17:33
corvusnew rocky 9 images are uploading now17:34
priteauindeed, but they don't appear to be used by our jobs. Do we need to change nodeset?17:35
corvusno i mean they are literally being uploaded to the cloud providers, but that takes like an hour17:35
priteauOK, I will try again later17:35
fungibeing uploaded *now*17:35
priteauSo it is expected that we switched to a rocky9 image built on May 27, following this 952721 change?17:36
mnasiadkayes, because there were some other problems that caused no newer uploads of these images - but that was fixed sort of yesterday I think - see https://opendev.org/opendev/zuul-providers/commit/1ed3cf6514d863ccca74f5c5d1e265486eed749c17:37
priteauI had missed that this zuul-launcher migration was happening, thanks17:38
mnasiadkaand https://opendev.org/opendev/zuul-providers/commit/d492a86f2fbdb16b2db495015b330dcf41accfab17:38
fungipriteau: we tried really hard to make it as seamless as possible, there wasn't supposed to be any user-facing impact from the transition, but ran into several bugs after starting to switch the openstack tenant that we didn't hit with the other zuul tenants unfortunately17:41
fungior at least that we didn't spot when doing them first17:41
fungiwe actually rolled back the switch for the openstack tenant once, this is the second attempt17:42
clarkbthe changes allow us to test changes to the image builds before we publish them. It also allows you to have nodesets with nodes from different resource provider types. It should be a nice benefit over time but we're helping find all the corner cases before everyone is expected to run zuul this way17:44
corvusaiui, the may 27 image is still acceptable; it's just missing a cached file.  if it wasn't, we could have deleted it at any time in accordance with our normal practice.17:45
clarkbcorvus: correct17:45
clarkbwe intended to cache the file (which is now corrected) but also the job doesn't properly fall back to pulling the file if not present in the cache17:46
clarkband we may proceed wtih removing that file from the cache due to its age at some point in the future17:46
mnasiadkapriteau: I assume it would be wise to check for existence of the file and download it if it's not judging by what clarkb is saying17:47
fungiyes, that's what devstack does, for example17:49
fungibecause if you run it locally then there's a good chance you won't have a copy of that file cached initially, but subseuent runs can take advantage of not having to re-download it then17:49
clarkband it allows us to have infrequently run stable jobs continue working as we cleanup old resources on the images17:50
fungithat was the original reason devstack did that, and we supplemented that behavior by simply pre-warming the cache in our test node images17:50
corvusmnasiadka: i got my wires crossed on https://zuul.opendev.org/t/openstack/build/fd2ad8dfcd4b458f9e70bc619a8cfb6f/log/zuul-info/zuul-info.primary.txt -- that build started 3 minutes after the rocky9 image from the nightly update finished uploading; but the node was launched for that build 5 minutes before it finished uploading.17:56
corvusmnasiadka: so, yeah, missed it by '' <-- that much :)17:57
mnasiadkanice17:57
mnasiadkacorvus: but yes,  some timestamps in zuul images tab would be helpful for end users like me ;-)17:57
mnasiadka(timestamps when these images got imported on a cloud)17:58
corvusyep, i'm expecting https://review.opendev.org/954063 to get reviewed tomorrow...17:59
corvusbut if you want, you can visit https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_980/zuul/980496d1b44d4243aebcbf129ac57014/npm/html/ and use that change now before it merges18:00
corvusi confirmed that does show the upload finished time... the only extra piece of information i have from the logs is when the node creation started.  but, with only a 3 minutes difference, it's a pretty good guess it started with the old image.18:01
mnasiadkathat's surely enough18:01
corvusoh, hrm.... so about those nested-virt labels... apparently the labels we used with nodepool are "nested-virt-ubuntu-noble" not "ubuntu-noble-nested-virt"18:14
clarkboops18:15
corvusi guess i will need to switch those around for the legacy labels at least... but do we want to switch the order for the new labels?18:15
clarkbI do think the new order (distro-attribute) makes more sense to me18:16
clarkbsince distro is the primary thing people care about when considering a platform. then its the details18:16
opendevreviewJames E. Blair proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429918:21
opendevreviewJames E. Blair proposed opendev/zuul-providers master: Correct nested-virt nodepool labels  https://review.opendev.org/c/opendev/zuul-providers/+/95436818:21
corvusoh no sorry about that18:21
opendevreviewJames E. Blair proposed opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429918:22
opendevreviewJames E. Blair proposed opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346018:23
opendevreviewJames E. Blair proposed opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426518:23
opendevreviewJames E. Blair proposed opendev/zuul-providers master: Correct nested-virt nodepool labels  https://review.opendev.org/c/opendev/zuul-providers/+/95436818:25
corvusokay that's all fixed.  i stacked the nested-virt fix on the end of that stack since it conflicted.18:26
opendevreviewJames E. Blair proposed opendev/zuul-providers master: Correct nested-virt nodepool labels  https://review.opendev.org/c/opendev/zuul-providers/+/95436818:28
priteaucorvus: our jobs are working now, thanks!18:32
fungiawesome18:32
noonedeadpunkfungi: I have a question about this one: https://opendev.org/openstack/openstack-zuul-jobs/commit/70fa0bd649fe39ee36130bbfeeefc08325fcfc6c19:27
noonedeadpunkor well...19:27
fungiwhat's the question?19:27
noonedeadpunkI found answer :)19:27
noonedeadpunkbut it;s basically https://zuul.opendev.org/t/openstack/build/8c144f3894cf41a9a3db8323ac6199f719:27
noonedeadpunkand the job on bionic for some reason19:27
noonedeadpunkso it has very old git19:28
fungioh!19:28
noonedeadpunkand quite some are affected https://zuul.opendev.org/t/openstack/builds?job_name=propose-translation-update&pipeline=periodic&skip=019:28
fungiyes, i didn't anticipate that we still had any jobs running old enough git that they don't support the --trailer cli option19:28
fungiyeah, i suspect only the translation jobs are still running on bionic, because of zanata only working with very old java19:29
noonedeadpunkyeah https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L118119:29
noonedeadpunkbut I heard smth of ubuntu support of openjdk 8 on some later releases... not sure though19:30
fungii can try to put together a patch to check the git version or platform and then skip that option19:30
noonedeadpunkI have openjdk-8-jre-headless on noble fwiw19:32
noonedeadpunkhttps://paste.openstack.org/show/bEg0RFbMGoQcIc0HYJYu/19:32
fungiooh19:33
noonedeadpunkwhich is exactly what we need? https://opendev.org/openstack/openstack-zuul-jobs/src/commit/70fa0bd649fe39ee36130bbfeeefc08325fcfc6c/roles/prepare-zanata-client/vars/Debian.yaml#L119:33
noonedeadpunkso, like19:33
noonedeadpunkshould I try just updating nodeset?19:33
clarkbthat seems promising. And ya updating the nodeset is where I would start19:33
fungiabsolutely19:34
noonedeadpunkit's just that I guess we will see result only on periodic19:34
noonedeadpunkand if it would fly19:34
fungithat's the best possible outcome short of finishing the weblate migration19:34
noonedeadpunkbut then I wonder if we're really stick with Zanata on bionic as server...19:34
noonedeadpunkanyway, let's start from client19:34
fungiyeah, deploying a new zanata server is possible, but would be a lot of work that we may just avoid for a little longer until weblate is the thing19:35
clarkbswapping the zanata os doesn't necessarily get you the runtime framework (wildfly/jboss) nor does it update zanata itself19:36
clarkbI don't personally think the effort involved there is worth the minor improvement19:36
noonedeadpunkugh, there're still some jobs with Xenial even...19:38
noonedeadpunkok, I needed to rebase :)19:38
opendevreviewDmitriy Rabotyagov proposed openstack/project-config master: Switch translate proposal jobs to noble  https://review.opendev.org/c/openstack/project-config/+/95437019:41
fungitoo bad that won't get tested speculatively19:42
noonedeadpunkyeah19:42
noonedeadpunkas the job is post-review19:42
noonedeadpunk(as require secrets)19:43
fungiclarkb: i'm going to pop out for a quick dinner before i finish up quarterly planning paperwork, but will be around in an hour-ish to talk about cla removal from the gerrit image if that works for you19:43
clarkbfungi: yup it should. I can dig up lunch in that rough same block of time19:43
fungiperfect19:44
clarkbfungi: I've rechecked https://review.opendev.org/c/opendev/system-config/+/882900 as it is a bit older and want to amke sure it is still working today. That change moves gerrit images to quay.io20:46
clarkbfungi: I think at the very least we could land that change and restart to cover the quay.io move and the zuul status tab updates. But also I think cleaning up the cla resources in the gerrit image may be able to be consolidated into that restart as well since all three items are largely independent of one another the chance that one of them impacts another is low20:47
fungiclarkb: makes sense20:51
clarkbhttps://opendev.org/opendev/system-config/src/branch/master/playbooks/zuul/gerrit/run.yaml#L37-L56 is the code that we need to clean up to stop including the cla files in gerrit20:51
clarkbI guess my main questions are do we need to remove cla configuration from gerrit on the config side first (I think so otherwise we'll be pointing at files that don't exist but maybe this is ok) and if so what is the timeline we're thinking about for that20:52
fungiwe can't really take the clas out of gerrit until we remove enforcement in remaining acls, and i want to give readers of service-announce a bit of time to react and submit changes to add dco enforcement or whatever, thinking like a week lead time20:52
clarkbfungi: do we know which projects haven't updated yet? I'm guessing its stuff in x/?20:52
fungiwill know in a moment...20:52
fungi(stand by)20:53
corvus[hold music plays]20:53
fungi265 acl files in total20:55
fungi210 are in the x namespace20:55
fungiother namespaces include: cfn, opendev, openinfra, performa, recordsansible, sardonic, windmill20:57
clarkbwindmill is effectively eol. I wonder what opendev repos are affected. I suspect we can just change openinfra20:58
clarkbre cfn I responded to them about the "corrupt" git repo and never heard back...20:58
clarkbanyway this list seems mostly reasonable20:58
clarkbI suspect that gerrit will force us to unconfigure all the enforce cla rules before removing the cla from config too but I'm not sure of that20:59
fungichange on the way20:59
fungijust composing the commit message now20:59
opendevreviewJeremy Stanley proposed openstack/project-config master: Remove CLA enforcement from all projects and lock  https://review.opendev.org/c/openstack/project-config/+/95437421:04
fungiclarkb: ^21:04
fungii'll do the actual config removal and cleanup as a child of that21:06
clarkbfungi: for the openinfra/ projects should they be switched to dco?21:11
clarkbI think for everything else removal makes sense given the commit message21:11
opendevreviewJeremy Stanley proposed opendev/system-config master: Stop installing and configuring CLAs  https://review.opendev.org/c/opendev/system-config/+/95437621:13
clarkband I guess https://review.opendev.org/c/opendev/system-config/+/954376/1/doc/source/gerrit.rst implies a manual step between the two changes (not a big deal just calling that out)21:14
fungiclarkb: i'll propose a separate change to add dco enforcement to the openinfra namespace projects after i confer with foundation staff21:14
fungiyeah21:14
clarkback that can be a child of the removal and merging them together shoudl avoid any unexpected behaviors21:15
fungialso just noticed i need to add a depends-on to that one21:15
* mordred would vote for things to just require GPG signed commits, but knows he's lost that battle in the general developer ecosystem mindspace21:15
fungidifferent repo21:15
clarkbthe only other consideration I have is that I'm out most of next week so maybe we want to try and land the gerrit image affecting changes on the 21st?21:15
fungimordred: we can just create our own theme park. with blackjack et cetera21:16
clarkbwe'll definitely want to do a gerrit restart after the changes land so want to do that when we think we'll be able to restart the service too21:16
fungiyeah21:16
opendevreviewJeremy Stanley proposed opendev/system-config master: Stop installing and configuring CLAs  https://review.opendev.org/c/opendev/system-config/+/95437621:16
fungidepends-on to the mass acl change added, and set to wip for now21:17
mordredfungi: fungi: https://bojackhorseman.fandom.com/wiki/Disneyland like this?21:17
opendevreviewIan Y. Choi proposed openstack/project-config master: Move to use prepare-weblate-client job  https://review.opendev.org/c/openstack/project-config/+/95437721:17
fungimordred: i was going for a futurama reference, but absolutely sure21:18
clarkbfungi: we could also aim for the 18th and if it doesn't happen then do the 21st21:18
clarkbmaybe thats best21:18
clarkb(I'm just worried I'll be busy catching back up again on the 18th but maybe it will be fine)21:18
mordredfungi: Hooray ... question mark?21:18
mordredSorry - we can all blame mtreinish for my Bojack addiction21:19
clarkbI think I have a new season of futurama  Istill need to watch21:20
clarkbmaybe I'll watch that alongside the new king of the hill when it comes out21:20
clarkbto summarize we'll land https://review.opendev.org/c/opendev/system-config/+/882900 and https://review.opendev.org/c/opendev/system-config/+/954376 and their parent change(s) on the 18th or shortly before with a plan to restart gerrit on the 18th to pick up the new zuul status stuff, quay.io image hosting, and cla file removals. IF the 18th is too busy we'll defer to the 21st21:22
clarkbin the maen time fungi will announce the CLA removal which gives ~10 days of notice21:22
clarkbfungi: ^ is that the plan?21:22
fungiwfm, yep21:23
mordredclarkb: have y'all watched the Great North yet? if not, highly recommend adding it to your adult cartoon rotation21:23
fungii'll try to get something out to service-announce today or tomorrow21:23
clarkbfungi: perfect, thanks!21:24
* clarkb scribbles some notes for the 18th21:24
opendevreviewMerged opendev/zuul-providers master: Normalize infra-package-needs packages on current releases  https://review.opendev.org/c/opendev/zuul-providers/+/95429921:32
opendevreviewMerged opendev/zuul-providers master: Add CentOS Stream 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95346021:32
opendevreviewMerged opendev/zuul-providers master: Add Rocky Linux 10 builds  https://review.opendev.org/c/opendev/zuul-providers/+/95426521:32
corvusclarkb: fungi can you +3 https://review.opendev.org/954368 ?  (nested virt fix as discussed earlier)21:33
fungilooking21:37
clarkb+2 from me21:39
fungiand approved21:40
opendevreviewMerged opendev/zuul-providers master: Correct nested-virt nodepool labels  https://review.opendev.org/c/opendev/zuul-providers/+/95436821:40
opendevreviewMerged openstack/project-config master: Switch translate proposal jobs to noble  https://review.opendev.org/c/openstack/project-config/+/95437022:46
funginoonedeadpunk: ^ i'll try to check the daily runs when i wake up, but i expect you'll be around far earlier22:48
noonedeadpunkyeah, we have some translations pending22:52
noonedeadpunkso we either see a patch incoming or not :)22:52
fungiand if not, i'll rectify it tomorrow22:53
noonedeadpunkwill check on it as well if not so no worrie22:54
clarkbstephenfin: I properly reviewed the first half or so of the pbr stack. I think in general things are fine but I noticed some small bugs here and there which I noted. Then as I ran out of steam in the later half of the stack I tried to leave higher level observations. I'm not opposed to any of the deprecations you are adding but as noted I think we may want to decide early (as part of23:00
clarkbthis work) what the removal timeline is for that if at all and then try to make that clear within the code23:00
clarkbstephenfin: PBR has at times been a honey pot for people making easy changes to "clean up" things not undersatnding its support timeframes are different than openstack's proper because old openstack still exists23:00
fungialso part of the timeframe planning needs to include release checkpoints23:01
clarkbstephenfin: anyway I'd like to capture a minimal "this is what deprecation means for pbr" if we can. I think from my perspecitve we decprecate things to encourage peopel to change to the modern canonical options but we don't necessarily remove them if they may have been in use and we can continue to support the old packages23:01
fungihow many releases are we going to split this work across? which ones need to be major version bumps?23:02
clarkbstephenfin: the reason I have that position is the instant we stop accepting summary instead of description for packages we'll break every single package that used the old version23:02
clarkbfungi: major versions bumps aren't useful here due to how pbr works23:02
clarkbthe old packages on old python with old pip and setuptools are going to get the latest pbr version when you try to manipulate those sdists23:02
fungii think it's still a useful means of communicating backward-incompatible changes, even if it can't be used to delay their effects23:03
clarkbwell my point is that we shouldn't release them in the first place if they are backward incompatible :)23:03
fungialso not entirely true wrt old versions of python, if we're careful about setting supported python versions, but it would depend on the specifics23:04
fungiwe've dropped support for some pbr features already in recent years23:04
clarkbI think what I would suggest if we want to ultimately remove that code is that we make a PBR2 or PBRng package that removes that stuff and then packages can convert to it23:04
clarkbthen we leave old pbr alone23:04
fungiand those are backward-incompatible changes23:04
fungior were23:05
clarkbfungi: but only because we couldn't support them anymorewithout copying large chunks of setuptools23:05
clarkbI'm talking about summary ~= description23:05
clarkbbreaking that is silly imo23:05
clarkbits trivial to support forever23:05
fungiwell, yes that's the sort of thing we could just carry a forever alias on23:05
clarkband almost certainly packages will break if we stop23:05
fungiyou're clearly further down (or up?) the stack of changes than i am23:06
fungiso i'm speaking in generalities23:06
clarkbya I am too fwiw. I think each deprecation and potential removal will need its own consdieration. What I mostly want to do is firmly assert that pbr doesn't use openstack deprecation process23:06
clarkbwhich most people who push packages to pbr to delete deprecated things assume23:07
fungii don't yet know what the pending removal of scriptwriter and eventually pkg_resources is going to mean for features in pbr, at least not yet23:07
clarkbI think stephenfin has fixed all but one pkg_resources usage in that stack23:07
clarkbso hopefully that one is largely a non issue23:07
fungioh wow, that's sooner thani anticipated23:07
clarkband if we ignore wsgiscripts then pip apparently writes cli scripts without the costly entrypoint scanning and that is largely a non issue for everyone but openstack (which relies on wsgiscript)23:08
clarkbanyway I think the main thing is we recognize that deprecation doesnt' start a 12 month clock. Some things may be deprecated and exist forever. Others might be cleaned up. We have to use careful judgement23:08
clarkbwhich is different than deprecating something in nova23:09
fungiagreed, there is no absolute correlation between "deprecated" and "will be removed at some point"23:13
fungideprecated just means there's a better/newer/preferred alternative23:13
funginot necessarily pressure to stop doing things the old way if they can be kept working23:14
clarkbyup and I do think taking stock of them from our side and deciding if a PBRng makes sense is another useful side effect23:14
clarkbits possible we reach a point where that makes sense and one signal for that could be the amount of deprecated code we're needing to maintain23:15
clarkbmy fear with doing that is that og PBR is likely to break due to future setuptools changes so now we're fixingtwo code bases instead of one23:16
clarkband I'm not sure that is simpler overall23:16
clarkbbut it may still be worthwhile in the future particularly when packages have greater control over the setuptools version they use (via pyproject.toml for example023:16
clarkbI'll also try to properly review the second half of that stack tomorrow23:26

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