dtantsur | cardoe: btw, I generally give people a blank permission to update my patches for trivial things like typos, small fixes or release notes. | 06:44 |
---|---|---|
dtantsur | (will update today if nobody beats me to it) | 06:44 |
dtantsur | * blanket (wake up Dmitry!) | 06:44 |
opendevreview | Dmitry Tantsur proposed openstack/ironic master: Remove legacy Query support from _paginate_query https://review.opendev.org/c/openstack/ironic/+/891505 | 09:11 |
dtantsur | cardoe, TheJulia, JayF ^^ | 09:12 |
dtantsur | meanwhile, ironic-inspector-tempest seems quite unstable: https://zuul.opendev.org/t/openstack/builds?job_name=ironic-inspector-tempest&branch=master&skip=0 | 09:14 |
dtantsur | I don't think we can merge much into ironic-tempest-plugin before we fix it | 09:14 |
opendevreview | Mark Goddard proposed openstack/tenks master: CI: Remove CentOS Stream 8 jobs https://review.opendev.org/c/openstack/tenks/+/928774 | 09:30 |
opendevreview | Mark Goddard proposed openstack/tenks stable/2.0: CI: Remove CentOS Stream 8 jobs https://review.opendev.org/c/openstack/tenks/+/928775 | 09:33 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-lib master: Remove code already migrated to Ironic and IPA https://review.opendev.org/c/openstack/ironic-lib/+/928776 | 09:35 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-lib master: Remove the rest of the rootwrap machinery https://review.opendev.org/c/openstack/ironic-lib/+/928778 | 09:43 |
dtantsur | at least we can remove a lot of code now ^^^ | 09:45 |
dtantsur | (I specifically waited for 2024.2 to be branches first.. just in case) | 09:45 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-lib master: Remove the rest of the rootwrap machinery https://review.opendev.org/c/openstack/ironic-lib/+/928778 | 09:55 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-python-agent master: Migrate more trivial code from ironic-lib https://review.opendev.org/c/openstack/ironic-python-agent/+/928779 | 10:13 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-inspector master: Try enabling port 5050 on PUBLIC_BRIDGE https://review.opendev.org/c/openstack/ironic-inspector/+/928783 | 11:29 |
TheJulia | dtantsur: did you mean to https://review.opendev.org/c/openstack/ironic-python-agent/+/928779 while also removing some of the same files in another patch? | 13:04 |
dtantsur | TheJulia: my ironic-lib and IPA patches are disjoint: the ironic-lib removes the already migrated code, while the IPA one migrates more | 13:05 |
dtantsur | if it makes sense (also good morning) | 13:05 |
TheJulia | oh | 13:06 |
TheJulia | for some reason I thought it was ironic-lib | 13:06 |
TheJulia | clearly, more coffee required | 13:06 |
dtantsur | coffee++ | 13:06 |
dtantsur | which substance do I need to the CVE backports to OpenShift? | 13:06 |
TheJulia | coffee? lots of coffee? | 13:08 |
TheJulia | and a chart of versions to match up backports | 13:08 |
dtantsur | 4.15 was branched between stable/2023.2 and bugfix/24.0, so neither versions of patches actually apply cleanly | 13:08 |
* dtantsur head->table | 13:08 | |
dtantsur | well, maybe if I just take test_image_cache from bugfix/24.0 and the rest from stable/2023.2.... | 13:10 |
cardoe | metal3-integration seems to have failed recently a few patchsets. the machines never became ready after inspection | 13:11 |
dtantsur | 2 failures in a row, suspicious but not terrible https://zuul.opendev.org/t/openstack/builds?job_name=metal3-integration | 13:13 |
dtantsur | ha, mixing versions works! | 13:13 |
* dtantsur committing git sins | 13:13 | |
TheJulia | dtantsur: this must be a t-shirt | 13:14 |
dtantsur | totally | 13:14 |
cardoe | I'd buy it | 13:14 |
TheJulia | (of course, git's 3-way merge logic also commits sins of it's own) | 13:15 |
cardoe | semi-linear with up to date branches is the one true way | 13:15 |
cardoe | Except GitHub disagrees with me so I'm a heretic. | 13:15 |
TheJulia | if you ever go read about the merge logic, you'll want to table flip | 13:16 |
dtantsur | :D | 13:16 |
TheJulia | Being a heretic is good. | 13:16 |
dtantsur | my life has become much better since conflictStyle = diff3 | 13:16 |
dtantsur | but still | 13:16 |
TheJulia | You get awesome shirts | 13:16 |
cardoe | It'd basically Linus's quilt behavior tweaks. | 13:16 |
cardoe | Linus and Hanno Bock I think. | 13:16 |
dtantsur | On a serious note, wtf is going on in the inspector CI? | 13:19 |
opendevreview | Dmitry Tantsur proposed openstack/ironic-inspector master: DNM: get a clean CI run https://review.opendev.org/c/openstack/ironic-inspector/+/928793 | 13:20 |
TheJulia | has it gone completely sideways? | 13:24 |
TheJulia | as the british say, has it gone pear shaped? | 13:31 |
dtantsur | :D | 13:32 |
dtantsur | I've just created a test patch. What I got in https://review.opendev.org/c/openstack/ironic-inspector/+/928783 is not exactly inspiring | 13:33 |
TheJulia | If it fails, do we throw a party? | 13:33 |
dtantsur | or the table out of the window? | 13:35 |
dtantsur | so many options! | 13:35 |
TheJulia | .... we have a saying about windows in the states these days | 13:37 |
TheJulia | Parties are likely better, everyone can mosh pit by the pool and inspector can be forgotten about... right? | 13:37 |
* dtantsur is very ready to forget inspector | 13:46 | |
TheJulia | what is the outstanding item again? | 14:11 |
JayF | I know CID is working on inspection rules | 14:15 |
JayF | Or at least was helping with it in some way | 14:15 |
cardoe | You folks good with https://review.opendev.org/c/openstack/ironic/+/919779 ? | 14:17 |
cardoe | What if I made a new hashtag instead of "ironic-weekly-prio" that's like "ironic-workflow-ready"? | 14:18 |
cid | JayF: I am! Now waiting to get a little feedback on the current shape. | 14:18 |
cardoe | And I'll track more repos under the Ironic umbrella and tag anything with a core +2 and verified +1? | 14:18 |
TheJulia | LGTM, approving | 14:18 |
TheJulia | well, the doc change | 14:18 |
cardoe | https://review.opendev.org/c/openstack/ironic/+/928106 that's another one | 14:19 |
JayF | cardoe: I've considered that before, we should discuss it at the ptg though because the biggest issue would changing it will just be evangelizing the new name | 14:20 |
cardoe | I didn't understand why https://review.opendev.org/c/openstack/ironic-python-agent/+/927984 didn't merge. | 14:20 |
JayF | cardoe: I will say if we changed it, changing it to something longer seems silly | 14:20 |
cardoe | Well I can just tag +2/+1 stuff with ironic-weekly-prio? | 14:20 |
cardoe | I'm just trying to be helpful while learning the project more. | 14:22 |
JayF | If you see a patch that needs a review and is ready and is not otherwise hashtagged with that please do so | 14:22 |
JayF | cardoe: for that IPA patch, if you look at the box titled submitted together, you'll see that it is stacked on top of a patch that is not merging | 14:24 |
JayF | cardoe: this is how you stack dependent patches in the same project, multiple commits on a single branch and one git review pushes them all up | 14:25 |
cardoe | ah. been trying to figure more gerrit bits out. thanks. | 14:27 |
TheJulia | Gerrit is... different, yet exceptionally powerful | 14:31 |
JayF | Honestly I don't want to admit how many minutes I've wasted WTF ing at why a patch hasn't merged only to see that it was fat | 14:31 |
JayF | **stacked | 14:31 |
opendevreview | Merged openstack/ironic master: Deduplicate and remove invalid information for steps https://review.opendev.org/c/openstack/ironic/+/919779 | 14:31 |
TheJulia | zuul adds a different layer of power! | 14:31 |
derekh | If anybody has some spare time (if thats a thing) I'd appreciate another review on https://review.opendev.org/c/openstack/ironic/+/927828 | 14:33 |
TheJulia | what is time?! | 14:33 |
TheJulia | derekh: I feel like I'm missing a key piece, what is causing the agent attempt coming out of prepare? | 14:35 |
derekh | TheJulia, the agent is finishing inspection, moving the node out of "inspecting", our client (in my case the openshift baremetal operator) then immediately attempts to clean the node, but fails if heart beating has yet to start, in which case we need it to retry , I've some more context in the openshift bug https://issues.redhat.com/browse/OCPBUGS-33255?focusedId=25134975&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comme | 14:40 |
derekh | nt-25134975 | 14:40 |
TheJulia | okay, so an external call then | 14:40 |
TheJulia | that actually makes a lot of sense then | 14:40 |
TheJulia | Thanks! | 14:40 |
derekh | no prob | 14:41 |
TheJulia | approved | 14:41 |
derekh | thanks | 14:41 |
TheJulia | Thanks! | 14:43 |
opendevreview | cid proposed openstack/virtualpdu master: Upgrade pysnmp-lextudio https://review.opendev.org/c/openstack/virtualpdu/+/928823 | 15:28 |
opendevreview | cid proposed openstack/virtualpdu master: Upgrade pysnmp-lextudio https://review.opendev.org/c/openstack/virtualpdu/+/928823 | 15:29 |
TheJulia | JayF: fyi https://review.opendev.org/c/openstack/ironic/+/928709 | 15:37 |
JayF | I am spinning up a xena devstack today to test that | 15:37 |
TheJulia | ack, looks like the py39 test failure was transient | 15:37 |
JayF | not saying I'm making that a requirement to merge, just I don't want my downstream to get more egg on face | 15:37 |
JayF | but if you wanna wait I can get you feedback from that | 15:38 |
TheJulia | I was able to identify the delta, so I'm just pretty sure that is it | 15:39 |
TheJulia | but, by all means test | 15:39 |
TheJulia | that disable force_raw was sort of unexpected for me | 15:39 |
JayF | yeah, it matches what they were seeing | 15:39 |
JayF | so I have confidence in it too, just would rather pay 2-3 hours of my own time than more of other folks' time | 15:40 |
TheJulia | https://www.socallinuxexpo.org/scale/22x/events/open-infra-days <-- start brewing your talk ideas! | 15:47 |
JayF | oh yaay! at scale | 15:47 |
JayF | When is listed as > Sunday, August 18, 2024 - 08:00 < | 15:47 |
JayF | which seems wrong? | 15:48 |
clarkb | JayF: I called that out and expect it to get fixed soon | 15:48 |
JayF | scale itself is in March 2025, I assume that's more correct | 15:48 |
* JayF makes plans | 15:48 | |
TheJulia | plans++ | 15:51 |
JayF | I have a talk brewing I want to title something like "OpenStack is the bearer of bad news" or something along those lines, I'm going to get it ready for this | 15:58 |
JayF | basically talking about the phenomenon where if you're using OpenStack to run your infra, a large % of problems are blamed on it simply because it is effectively the monitoring system | 15:58 |
cardoe | Should the inspector hooks only trigger on the agent inspector? | 16:02 |
TheJulia | JayF: I think the counter balance to monitoring is supplying garbage | 16:04 |
TheJulia | JayF: one of the huge complaints I hear from a large operator is their users doing things which are fundimentally just don't work and they like to blame the infra instead of just fess up that they did something breaking like... decide to run a dhcp server, or supply garbage disk images | 16:05 |
TheJulia | ugh, the air quality in Southern California is awful today | 16:20 |
TheJulia | cardoe: Historically, I think they have only on that. But that raises an interesting question! | 16:22 |
JayF | TheJulia: I've thought of comparing OpenStack to a monitoring system as part of this point; it touches almost all parts of the infrastructure so it's often the canary for failure | 16:32 |
TheJulia | oh, absolutely | 16:33 |
TheJulia | we automate things which are painful | 16:33 |
TheJulia | you can wire it all manually, but do you really want to do that?! | 16:34 |
TheJulia | and is that really the right thing to do | 16:34 |
JayF | I think it's more that people compare on-prem BM cloud to e.g. AWS | 16:34 |
JayF | which is not apples to apples in terms of complexity or cost | 16:34 |
TheJulia | indeed | 16:34 |
TheJulia | I'm not comparing though, I'm more thinking people also don't undestand the size/scale/scope of the underlying interaction | 16:35 |
JayF | yeah I have an idea of a graph that looks like a spider | 16:35 |
TheJulia | Sure, you can have a VM. But if you want fancy networking... well that is a little more work. Oh you want this and that too, that is more work | 16:35 |
JayF | showing openstack crossing every network boundary, physical location boundary, etc etc | 16:35 |
TheJulia | and at some point, self-inventing in painful manual ways is not the right thing to the next person who will come along | 16:35 |
JayF | and also talking about data/control plane misconceptions: an openstack "outage" is about control, not existing devices | 16:36 |
JayF | TheJulia: I think part of the perception is that openstack /is the painful manual way/ due to how much hands-on you need to get a working (particularly Ironic with all the bits and trimmings) installation | 16:36 |
TheJulia | From a purely operational point of view, agree | 16:37 |
JayF | TheJulia: I remember two grumpy folks giving a "kids these days don't know how hard things are" two scales ago that pointed in this direction ;) | 16:37 |
TheJulia | I'm thinking from a user point of view, they don't know how the sausage is made nor know how complex the kitchenaid gears are unless they start disassembling the kitchenaid | 16:37 |
TheJulia | soon they will learn they are likely never going to get it back together | 16:37 |
TheJulia | without an expert, that is | 16:37 |
TheJulia | :) | 16:37 |
TheJulia | Oh, this worm gear goes in the other direction, and magically it all begins to work again | 16:38 |
JayF | "why does this kitchen aid make a horrible grinding noise? I've only been using it underwater for 10 years nonstop without any grease" ;) | 16:38 |
jssfr | what | 16:39 |
JayF | jssfr: we're just like, 5 layers deep in a hypothetical metaphor :D | 16:40 |
JayF | what's up? | 16:40 |
jssfr | okay, I just read the last sentence and it was so weird that I wanted to hear a story about it | 16:41 |
jssfr | but I didn't catch the metaphor part, carry on please | 16:41 |
TheJulia | Speaking of, at some point I need to rebuild my kitchenaid at the house | 16:42 |
TheJulia | .... it has the metal gears | 16:42 |
TheJulia | (yes, it is very, very old. | 16:42 |
JayF | jssfr: oh, just a metaphor for neglected, broken, sad clouds | 16:42 |
JayF | jssfr: e.g. them: "openstack is bad" me: what release? them: train! | 16:42 |
TheJulia | me: *faceplam* | 16:43 |
jssfr | haha | 16:43 |
jssfr | I can relate to train | 16:43 |
TheJulia | chooooooo chooooooo | 16:53 |
TheJulia | .... In a weird sense, I miss that hotel. | 16:55 |
JayF | ? that hotel | 17:05 |
clarkb | The Denver Stapleton Renaissance Hotel. The hotel that gave Train its name | 17:08 |
TheJulia | https://maps.app.goo.gl/A4bvqX83F1isSNWM6 | 17:14 |
TheJulia | if you look to the north you'll see train tracks | 17:14 |
TheJulia | The city is no longer Stapleton, fwiw. It is now called Central Park | 17:15 |
JayF | oh, that's cool as hell | 17:15 |
TheJulia | Back in ?2021? they voted to rename the city. | 17:15 |
JayF | reminds me of the disney hotels | 17:15 |
TheJulia | Ear Plugs were provided upon check-in. | 17:15 |
clarkb | TIL they renamed the city | 17:15 |
TheJulia | I only knew they renamed it because I was looking for a physical location to host a meeting | 17:17 |
TheJulia | wow, the fire that is causing my air quality to be awful today must be getting worse. They just called for 40 engines, 4 dozers to clear fire lines, and both another VLAT and LAT ([very] large air tanker) | 17:19 |
* TheJulia guesses this means it is "fire season" | 17:22 | |
TheJulia | https://zuul.opendev.org/t/openstack/build/5ea8b917c45e4834adeb9e0982a0e0e4 ugh | 17:24 |
clarkb | TheJulia: that is caused by having a too old version of `packaging` for your version of pip (or maybe setuptools). One or both of setuptools/pip prefer system libs to their vendored libs which can lead to this (and this is a relatively new change) | 17:27 |
clarkb | personally I don't understand why they would vendor anything at all then prefer to use other verions that might be broken when they know the vendored versions work... | 17:27 |
TheJulia | clarkb: like, since Saturday? | 17:28 |
clarkb | ya | 17:28 |
TheJulia | so, hmmm | 17:28 |
clarkb | I think it was setuptools updating on september 4 | 17:28 |
clarkb | so since a week ago ish | 17:29 |
TheJulia | changing requirements on a stable branch is really not a great idea | 17:29 |
TheJulia | eek | 17:29 |
TheJulia | well, "unmaintained" but same difference | 17:29 |
* TheJulia attempts local reproduction | 17:31 | |
clarkb | re bumping deps on stable/unmaintained branches I feel like keeping the pypa related stuff functional is a reasonable exception to that. It shouldn't affect runtime but does ensure you can keep buildingthe software. | 17:34 |
TheJulia | yeah, i guess it is a mix of factors since tests seem to run locally | 17:39 |
TheJulia | on python 3.9 from that branch | 17:39 |
TheJulia | eww, looks like I might be getting separate errors | 17:40 |
* TheJulia waits | 17:40 | |
TheJulia | hmmm | 17:40 |
TheJulia | rm -r -f .tox and retry | 17:40 |
TheJulia | hmm | 17:46 |
TheJulia | looks like we were getting fairly recent versions in CI | 17:55 |
TheJulia | tempted to try and match up to reproduce, just don't understand a different error I'm now getting on 3.9 | 17:56 |
JayF | wrong tox version? | 17:58 |
TheJulia | somehow the py39 run had a different version of ironic | 17:59 |
TheJulia | installed in it's environment | 17:59 |
TheJulia | just.. bizzare | 18:00 |
TheJulia | so yeah, upstream ran with latest setuptools, slightly older packaging. lets see what chaos it gets into | 18:01 |
TheJulia | seems to run just fine... | 18:03 |
TheJulia | hmmm | 18:03 |
TheJulia | yup, looks like it | 18:07 |
TheJulia | installing an older tox locally to try and reproduce | 18:07 |
TheJulia | I had tox 4-something locally and it was happy | 18:08 |
TheJulia | we have 3.28.0 in CI right now | 18:08 |
TheJulia | Okay, I'm feeling stumped | 18:17 |
TheJulia | clarkb: could the base OS and python libraries be an interaction regardless of versions installed? | 18:19 |
TheJulia | (as part of the execution of tox...) | 18:19 |
clarkb | if site packages are enabled in the virtualenv or perhaps if older virtualenv bundles packaging into the venv maybe? | 18:20 |
TheJulia | Doesn't look like it from my point of view, just seems weird I can't reproduce | 18:22 |
clarkb | in the example from earlier today starglingx was using contraints to pin `packaging` back to an incompatble version | 18:22 |
TheJulia | do you know what version that was? | 18:23 |
TheJulia | Collecting packaging>=20.4 (from oslo.utils>=4.5.0->-r /home/zuul/src/opendev.org/openstack/ironic/requirements.txt (line 28)) <-- upstream from the failed job | 18:24 |
clarkb | TheJulia: https://opendev.org/starlingx/root/raw/branch/master/build-tools/requirements/debian/upper-constraints.txt says packaging===20.9 | 18:24 |
TheJulia | for science, y'all | 18:28 |
TheJulia | https://review.opendev.org/c/openstack/ironic/+/928851 | 18:28 |
cardoe | Have we had a successful metal3-integration happen on ironic master today? | 18:38 |
cardoe | Don't want to wastefully retry https://review.opendev.org/c/openstack/ironic/+/928283 | 18:39 |
JayF | look at the failure, see what's up with it | 18:40 |
JayF | if it's been the same, we should -nv it and notify dmitry/riccardo | 18:41 |
TheJulia | ++ | 18:42 |
JayF | it looks like a systemmatic failure on k8s side | 18:42 |
JayF | line starting with 2024-09-09 22:07:27.904220 in https://d932237a159a818f5df3-c96838ca99c022c3211112e269bccbbb.ssl.cf5.rackcdn.com/928283/1/check/metal3-integration/1bb4f7b/job-output.txt | 18:45 |
JayF | I would +2A a patch to mark it nonvoting if we haven't seen a pass today | 18:45 |
clarkb | do you report the results of those jobs back to metal3 too? | 18:46 |
clarkb | just wondering if getting the signal going in both directions might aid in awareness when things are broken and what needs fixing | 18:46 |
JayF | we have a massive overlap in cores | 18:47 |
JayF | Iury, Dmitry, Riccardo are all on the metal3 project | 18:47 |
JayF | and I believe there are some cross-voting jobs on the metal3 side | 18:47 |
JayF | probably a little less attention being paid to it than usual due to vacations | 18:47 |
cardoe | Well Dmitry gave me this link this morning... https://zuul.opendev.org/t/openstack/builds?job_name=metal3-integration | 18:49 |
cardoe | So it's not run more than the 2 I've tried so far. | 18:49 |
JayF | so either something failed between last night and today | 18:49 |
cardoe | But it's just very long when it fails | 18:49 |
JayF | or we're unlucky | 18:49 |
JayF | it failing with such a long tail is not something I've seen before | 18:51 |
JayF | and kinda maps with the log I pointed at up there | 18:51 |
JayF | I suspects it's systemmatic and should be marked nonvoting, but a sample size of two is small. | 18:53 |
JayF | Marking it non-voting is a small change for a big benefit, I'd do it | 18:53 |
opendevreview | Verification of a change to openstack/ironic master failed: Set node "alive" when inspection finished https://review.opendev.org/c/openstack/ironic/+/927828 | 19:04 |
JayF | > metal3-integration https://zuul.opendev.org/t/openstack/build/031713c8f81b49f7bc186184e4c5f39b : TIMED_OUT in 4h 15m 36s | 19:05 |
JayF | holy yikes | 19:05 |
JayF | I am -nv'ing that | 19:05 |
opendevreview | Jay Faulkner proposed openstack/ironic master: [ci] Temporarily mark metal3-integration non-voting https://review.opendev.org/c/openstack/ironic/+/928857 | 19:07 |
JayF | I'm slightly tempted to *completely remove* the job given it's current timeout behavior will cause all jobs to take that long, even if not voting | 19:07 |
clarkb | you can drop the timeout to a lower value at the same time | 19:08 |
clarkb | but then you may get less useful signal | 19:08 |
TheJulia | it *typically* takes like 1.5 hours | 19:08 |
TheJulia | at least, that is my instant recall impression | 19:08 |
TheJulia | clarkb: packaging 21.3 == same error, trying 22.0 | 19:09 |
TheJulia | and of course, blows up requirements-check | 19:09 |
JayF | clarkb: do you know the key for that right off the top of your head? | 19:09 |
clarkb | JayF: its just timeout then a number of seconds | 19:10 |
JayF | I'm happy to cap it at like, 90 minutes. We've never seen a passing job that takes over an hour. | 19:10 |
JayF | ack | 19:10 |
JayF | same spot as voting:? | 19:10 |
clarkb | timeout: 7200 or whatever | 19:10 |
JayF | 10-4 on it | 19:10 |
clarkb | yes same level as name/description/voting/vars/etc | 19:10 |
opendevreview | Jay Faulkner proposed openstack/ironic master: [ci] Temporarily mark metal3-integration non-voting https://review.opendev.org/c/openstack/ironic/+/928857 | 19:12 |
JayF | I'm going to create release PRs for stable branches since CVE fix landed, assming they aren't already | 19:14 |
TheJulia | JayF: for what? | 19:14 |
JayF | Ironic and IPA | 19:14 |
JayF | stable/* | 19:14 |
TheJulia | for what specifcially? | 19:14 |
JayF | to cover the CVE fix | 19:15 |
JayF | we merged a fix to master, I'd like us to have it released | 19:15 |
JayF | s/master/HEAD/ | 19:15 |
TheJulia | oh, release changes | 19:15 |
TheJulia | okay | 19:15 |
TheJulia | yeah, sounds good | 19:15 |
TheJulia | I think you got me at "PRs" | 19:15 |
TheJulia | so packaging 22.0 is incompatible | 19:17 |
TheJulia | ... could we just remove python 3.9 testing? | 19:20 |
TheJulia | from yoga? | 19:20 |
TheJulia | just bizzare | 19:20 |
JayF | unmaintained/ branches are "kill it with fire" | 19:22 |
TheJulia | sort of yeah | 19:22 |
JayF | FYI > https://review.opendev.org/c/openstack/releases/+/928862 [ironic] Releases for OSSA-2024-003 | 19:24 |
TheJulia | I guess the base fundamental issue is openstack-python3-yoga-jobs is template with the base config | 19:28 |
TheJulia | xena seems to be okay | 19:29 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!