Friday, 2025-06-13

opendevreviewOpenStack Proposal Bot proposed openstack/project-config master: Normalize projects.yaml  https://review.opendev.org/c/openstack/project-config/+/95200602:26
opendevreviewtianyutong proposed openstack/project-config master: Allow branch creation for heterogeneous-distributed-training-framework  https://review.opendev.org/c/openstack/project-config/+/95253902:33
*** elodilles_ooo is now known as elodilles06:08
opendevreviewtianyutong proposed openstack/project-config master: Enable release team to create branches and signed tags  https://review.opendev.org/c/openstack/project-config/+/95254706:18
opendevreviewMichal Nasiadka proposed openstack/diskimage-builder master: Add Rocky Linux 10 support to rocky-container element  https://review.opendev.org/c/openstack/diskimage-builder/+/95254806:25
opendevreviewMichal Nasiadka proposed openstack/diskimage-builder master: Add Rocky Linux 10 support to rocky-container element  https://review.opendev.org/c/openstack/diskimage-builder/+/95254806:34
tonybI didn't make any real progress today on the DIB+devstack work.   I found a bunch of stuff I missed pulling over from nodepool so I'm further behind than I thought :/06:45
opendevreviewtianyutong proposed openstack/project-config master: Enable release team to create branches  https://review.opendev.org/c/openstack/project-config/+/95255406:47
opendevreviewtianyutong proposed openstack/project-config master: Allow branch creation for heterogeneous-distributed-training-framework  https://review.opendev.org/c/openstack/project-config/+/95255507:14
ianwtonyb: thanks a ton for working on it.  if it were easy, it would have happened already, so i really appreciate you digging into it to keep things alive07:22
tonyball good.   I "blame" corvus for upholding the "only one general purpose devstack role" line.  :⁠-⁠P07:43
*** darmach8 is now known as darmach11:42
opendevreviewMerged openstack/project-config master: Allow branch creation for heterogeneous-distributed-training-framework  https://review.opendev.org/c/openstack/project-config/+/95253912:50
corvuslol "blame" gladly accepted :)13:40
opendevreviewJames E. Blair proposed opendev/zuul-providers master: DNM: noop test change  https://review.opendev.org/c/opendev/zuul-providers/+/95257613:43
corvushttps://zuul.opendev.org/t/opendev/nodeset-requests13:44
corvusoops, looks like we're not deleting fulfilled noop requests13:44
corvusgood news is the new web ui for deleting nodeset requests works13:45
corvusokay, wrote changes that should address that.  i'm not going to manually cleanup the rest because one of the changes i wrote should automatically clean them up.14:45
fungigonna go grab lunch, back in a while14:50
clarkb`The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.`15:05
clarkbI don't understand15:05
clarkbcorvus: fyi ^ I saw that in nodepool build failures but I think the real issue is that pip is scanning all of these ibm packages to try and find the most appropriate version and its looking for requirements.txt files in those tarballs and one of them does not have that file? https://zuul.opendev.org/t/zuul/build/28e0c4720fae47918f49c42cba4f94bf/log/job-output.txt#104115:08
clarkbcorvus: that same error has broken the nodepool image builds. I think the solution here is to add that dep with a lower version bound15:09
clarkbI'll work on a change momentarily15:09
clarkbbut also removing pkg_resources is going to break many package on pypi15:09
clarkbpackages that we and others don't have control over but that we all rely on15:09
clarkbpossibly even pbr too... I guess the PBR compatibility cleanups are becoming more and more important. Its just frustrating that we can't assume older packages (for some values of not that old) will continue to build in the near future15:10
clarkbremote:   https://review.opendev.org/c/zuul/nodepool/+/952587 Give IBM cloud deps recent lower bounds15:19
clarkbI think this will hopefully unblock the dib tests for comparison to the new dib testing framework15:19
corvusthose ibm packages have been a source of a number of issues relating to how many of them get scanned and how slow it is... maybe that will help in general.15:26
corvusi think zuul hase the same deps, want to try bumping them there too?15:26
clarkbcorvus: can do15:28
clarkbremote:   https://review.opendev.org/c/zuul/zuul/+/952592 Set lower bounds on IBM cloud deps15:31
frickleroh, nice, likely we'll have to cap setuptools for most stable branches, then15:31
clarkbfrickler: ya I'm not sure what we can do about pkg_resources going away. That seems like a very major change15:31
clarkbI assume they want everyone using the new library which doesn't do everything pkg_resources does. import metadata or whatever it is called. Probably can update in many places but some may be problematic15:32
frickler"Some useful APIs are also provided by packaging" from https://setuptools.pypa.io/en/latest/pkg_resources.html. but yeah, python in general seems like a pretty unstable environment these days more than ever15:42
*** dhill is now known as Guest1810015:44
clarkbtonyb: fwiw the dib testing update did successfully boot and test a ubuntu node15:50
clarkbtonyb: I think the framework there is sound we've just got a few improvements to make (like qcow2 -> raw and the stuff ianw has suggested etc) and then sort out the weird platform issues. It might be worthwhile to avoid alma linux for now and focus on centos and rocky on the rpm distro side of things since we have more exposure and experience with them15:52
clarkbI wonder if the existing testing for alma linux is using glean. In any case getting nodepool fixed should allow us to recheck and get some data we can compare to15:53
clarkbcorvus: I think the node request leak cleanups are failing in ci15:57
corvusboo.  i only ran the affected tests locally15:58
clarkblooks like  tests.unit.test_gerrit.TestGerritCherryPickWeb.test_gerrit_cherry_pick_web_with_update_queue is what failed in one of them.15:58
clarkbI wonder if that is just an order problem independent of the changes. Looks like a mismatch of job run history maybe15:59
corvuspasses locally15:59
corvusooh there's a missing git add15:59
corvus(which explains the other failures)16:00
corvusfixed16:00
clarkbcorvus: that failed in 81 (the parent too) but you updated 82. Not sure if we needed the fix in the parent?16:01
corvusthe cherry pick test?  that's unrelated16:01
clarkbya. Got it16:02
clarkbwasn't sure if you meant the missing git add affected that somehow. I understand now. The child was broken. The parent hit something in the random number generator of the test suite16:02
corvusexactly16:06
fungifrickler: pinning setuptools versions may not even be possible in relevant ways unless those branches are already using pyproject.toml to define their build-system.requires lists16:12
clarkbnodepool image builds now fail on gcc: internal compiler error: Segmentation fault signal terminated program cc1 during yappi compilation16:58
clarkbI'm going to look at that now I guess. Will probably need the fix for thta and the ibm deps fix in one change16:59
clarkbok this is an arm only problem17:00
clarkbI don't see any upstream bug for this in yappi. Also this must be fairly recent possibly due to updates in debian? I want to say bookworm got a big update a month or two ago17:03
clarkbDebian 12.11 was released on May 17th, 202517:09
clarkbI suspect this is when it broke but don't know for sure17:09
fungido we have any rough window for when the build broke?17:42
clarkbI haven't looked yet been more focused on just fixing it17:45
clarkbhttps://zuul.opendev.org/t/zuul/builds?job_name=nodepool-build-image&skip=017:47
fungijust wondering if i can match it up to debian updates. if we're upgrading debian packages from the updates channel rather than just sticking with the point release versions, then the point release itself would be a non-event since it's just copying packages from updates to main stable17:47
clarkbthis seems to indicate that the problems are not consistent. Its possible that timing issues with running emulated arm triggers the gcc segfault inconsistently17:47
clarkbI think the ibm issue was not platform specific though and may be related to more recent package releases for that family of packages17:48
fungiyeah, looks like it passed once today17:48
fungior was that the fix you're working on?17:49
clarkbfungi: yes the pass included the ibm fixup but not the yappi fix17:49
clarkbfungi: so yappi segfault is inconsistent. I think the ibm problem was consistent17:49
fungigot it17:49
clarkbibm problem is very recent (last couple of days). yappi compile error may be older17:49
fungilooks like it was mostly passing yesterday and earlier in the week17:50
clarkbthere were failures with dib builds too which I think is a different job we can corss check with17:50
fungiyeah, the sample size here is small with lots of big holes17:50
fungihard to draw much of a conclusion17:51
clarkbhttps://zuul.opendev.org/t/openstack/builds?job_name=nodepool-build-image-siblings&skip=017:51
clarkbI suspect sometime yesterday it broke17:51
clarkblatest round of tests with the last patchset are looking good if anyone wants to review that change now (952587)18:28
fungilgtm, thanks!18:34
opendevreviewClark Boylan proposed openstack/diskimage-builder master: Add new openstack/devstack based functional testing  https://review.opendev.org/c/openstack/diskimage-builder/+/94994218:51
clarkbI added a deepnds on to the nodepool fix on ^ so that we can get data to compare to18:51

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