Thursday, 2024-08-22

*** bauzas_ is now known as bauzas01:17
*** bauzas_ is now known as bauzas04:10
tkajinamhmm it seems release note job is broken now ? I guess something went wrong when it was moved to noble https://zuul.opendev.org/t/openstack/build/7845d37b907b4d458cbd70828832752b06:00
tkajinamhttps://paste.opendev.org/show/bJb1vWv9OCnRmKZ8jMz7/06:25
*** bauzas_ is now known as bauzas06:29
fricklertkajinam: clarkb proposed https://review.opendev.org/c/openstack/releases/+/926860 but it seems like we would need to do that for every repo then, which doesn't sound like a good solution to me. maybe we can look into getting rid of that pcre dependency instead. or likely work around this for now by pinning that job to jammy I guess06:39
tkajinamyeah07:18
tkajinampushing the job back to jammy may be a short term solution until we find out a better solution than distributing the same bindep update07:20
opendevreviewJens Harbott proposed openstack/openstack-zuul-jobs master: Pin build-openstack-releasenotes job to jammy  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92687907:22
fricklertonyb: ^^ please have a short look if you're still around, otherwise I'll self-approve if zuul passes, since this seems to affect every openstack project07:23
opendevreviewJames Page proposed openstack/project-config master: Retire unmaintained charm repositories  https://review.opendev.org/c/openstack/project-config/+/92679107:24
fricklerhmm, got a linter failure on my fix, I thought that that had been fixed according to the backlog in #opendev, but maybe not for that repo? anyway I'm going to force-merge the fix now and look into the linter issue later07:52
opendevreviewMerged openstack/openstack-zuul-jobs master: Pin build-openstack-releasenotes job to jammy  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92687907:54
*** __ministry is now known as Guest113609:00
opendevreviewElod Illes proposed openstack/project-config master: [release-tool] Workaround for getting dist_name  https://review.opendev.org/c/openstack/project-config/+/92688509:28
opendevreviewMerged openstack/ci-log-processing master: Add url subpath for Logsender to reach OpenSearch  https://review.opendev.org/c/openstack/ci-log-processing/+/92671709:49
opendevreviewMerged openstack/project-config master: [release-tool] Workaround for getting dist_name  https://review.opendev.org/c/openstack/project-config/+/92688511:11
fungilooks like it's a dependency of whereto?12:16
fungipython-pcre is, i mean12:17
fungithe releasenotes playbook could just install the supporting packages on relevant platforms in that case12:18
fungii have a feeling the reason it worked on earlier platforms is we had pre-built and cached wheels of it but haven't done that for noble12:18
fungithe playbook workaround would only last us until projects start running their normal docs jobs on noble next cycle though12:21
fungipinning the releasenotes job back to jammy makes the most sense short-term, i guess, and we need to decide what this means more generally for the whereto utility depending on a python lib that's only distributed as a decade-old sdist yet builds c extensions. that's not good in this era12:22
fungimaybe the longer-term solution (for early next cycle) is to switch whereto to a different regular expression parser12:23
ttxwe also seem to have failures on the propose-update-constraints job now12:32
ttxSee https://lists.openstack.org/archives/list/release-job-failures@lists.openstack.org/12:32
ttxand we might need to reenqueue a few things12:33
fricklerttx: this should already be fixed, see the discussion in the release channel12:34
ttxohm wrong channel! sorry12:35
fricklerand we cannot re-enqueue those, will need to create the u-c bumps manually12:35
*** bauzas_ is now known as bauzas12:48
clarkbfrickler: re doing it for every repo that is the correct thing to do if you have the dependency because even if we built and hosted wheels in our wheel caches that is for CI only not for local developer workstations15:12
clarkband yes the dependency comes from whereto15:12
clarkbI actually think spinning things up iniitally without a wheel cache has been educational. There have been a number of things where we're relying on that when we shouldn'y be15:12
frickleryes, the wheel cache has been masking issues in the past, I wouldn't mind getting rid of it completely15:44
fricklerclarkb: btw. did you see the failure on https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/926879 ? I think I'm running out of time to look at it today15:44
frickleroh, and that's also an error I didn't notice before https://zuul.opendev.org/t/openstack/build/47e76090e20b4e768ae58933f0f921b4. I was referring to the linter failure above15:46
clarkbfrickler: the ozj linters issue is the oen that requires us to update the hacking version to latest (because it pulls in newer flake8 which works on python3.12. I can look into doing that for ozj later today (I've got a meeting then a school thing first)15:48
clarkbthe docs promote job failure is new to me. And also one I suspect isn't related to the nodeset change since it appears to be ansible setup related and we didn't change ansible15:49
clarkba quick skim would indicate the zuul artifact return data is maybe in a format that the ansible there doesn't expect?15:50
clarkblooks like we will also have to bump up the ansible and ansible-lint versions in ozj which means I think the best path forward there is to pin to jammy and update hacking, then bump ansible and ansible-lint and fix all the resulting errors15:55
clarkbthen we can unpin jammy15:55
clarkbfungi: have you see the issue in https://zuul.opendev.org/t/openstack/build/47e76090e20b4e768ae58933f0f921b4 before? That is a new oen to me and as mentioend i don't think it is related to the nodeset change15:55
frickleroh, actually that may have happened because I force-merged the change, so there wasn't a gate build that could be promoted15:55
fricklerI can propose the hacking bump for ozj though15:55
fungithat would indeed do it15:55
clarkbfrickler: oh yup that would do it15:55
opendevreviewJens Harbott proposed openstack/openstack-zuul-jobs master: Bump hacking to latest version  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92693315:57
clarkbas noted you may still need to ping to jammy beacuse now that hacking won't fail on python things it will continue to run and run ansible-lint and fail on python things later15:57
clarkbbut we can see what the CI results say about that to confirm the behavior before we assume it will occur15:58
fricklerah, yes I didn't read the last comments before submitting. but let's see CI results first15:58
frickleractually let me test this on my noble node15:58
fricklerFailed: 2021 failure(s), 46 warning(s) on 2049 files.16:15
fricklerthat's with all caps removed16:15
fricklerguess I'll pin to jammy first :-/16:18
opendevreviewJens Harbott proposed openstack/openstack-zuul-jobs master: Bump hacking to latest version  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92693316:21
fricklerthough I'm not sure ansible<6 will even work with python3.10?16:22
clarkbfrickler: we should bump ansible to >=8,<9 since that is what the jobs run with in zuul16:50
clarkband that solves that problem16:50
clarkbok now I'm off to do school things back in a bit16:51
fungiyeah, it's what we did in some of the other jobs already16:51
fungii need to disappear for a few minutes to run some quick errands but should be back within the hour16:51
fungiseems quiet here still17:40
fricklermy version of the patch passed CI, I would suggest to go with that for now. I still get ansible-lint errors for all variants I tried on noble17:45
clarkbfrickler: ya I don't think there is any way of avoiding the linter errors when running on python3.12 as we need newer version. Your patch lgtm and we can followup with linter improvements17:57
opendevreviewMerged openstack/openstack-zuul-jobs master: Bump hacking to latest version  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92693318:03
*** bauzas_ is now known as bauzas18:26
opendevreviewMaksym Medvied proposed openstack/project-config master: Mirror charm-ceph-nfs to GitHub  https://review.opendev.org/c/openstack/project-config/+/92694919:18
*** melwitt is now known as jgwentworth19:38
*** jgwentworth is now known as melwitt19:38
opendevreviewMerged openstack/project-config master: Mirror charm-ceph-nfs to GitHub  https://review.opendev.org/c/openstack/project-config/+/92694920:41
*** bauzas_ is now known as bauzas22:59
opendevreviewClark Boylan proposed openstack/openstack-zuul-jobs master: Run latest ansible-lint on Ubuntu Noble  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92697023:05
clarkbThat ^ will definitely not pass, but I don't have a noble install locally so just wanted a quick set of results that I can use to determine where to skip rules and where to apply fixes23:06
opendevreviewClark Boylan proposed openstack/project-config master: Split min ready nodes between jammy and noble  https://review.opendev.org/c/openstack/project-config/+/92697223:12
opendevreviewClark Boylan proposed openstack/openstack-zuul-jobs master: Run latest ansible-lint on Ubuntu Noble  https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/92697023:43
clarkbthat might pass assuming the list of errors on the first run was complete23:43
clarkboh except a whole bunch of extra josb run now so we'll see how that goes23:44

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