15:00:00 #startmeeting ironic 15:00:00 Meeting started Mon Mar 23 15:00:00 2026 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:00 The meeting name has been set to 'ironic' 15:00:16 Gooooood morning and welcome to the Ironic meeting. We're operating under the OpenInfra Code of Conduct as usual. 15:00:24 I'll give a minute or five for people to trickle in. 15:00:29 o/ 15:00:36 o/ 15:02:13 o/ 15:03:03 o/ 15:03:18 o/ 15:03:43 Olamide Ojo proposed openstack/ironic master: Improve reference consistency of the intel-ipmi file https://review.opendev.org/c/openstack/ironic/+/981789 15:04:06 Looks like weak quorum if quorum at all :) 15:04:17 I hope folks are off enjoying the downtime between releases, at least 15:04:23 #topic Announcements/Reminders 15:04:33 #link https://tinyurl.com/ironic-weekly-prio-dash 15:04:42 Please review changes hashtagged ironic-week-prio 15:04:59 If you have patches ready for review, passing CI, good to go, add hashtag "ironic-week-prio" to get them onto this dashboard 15:05:06 #link https://releases.openstack.org/gazpacho/schedule.html 15:05:18 We spent 6 months making a cold soup, and it's here :) 15:05:43 This is R-1 week: last chance to cut any releases. 15:05:51 There is an open question in the agenda: is all our stuff released? 15:06:00 I don't know the answer for this for sure, I hope it's "yes"? 15:06:04 Weak quorum for sure 15:06:19 I saw we cut off a lot of branches last week 15:06:29 I can double check, riccardo is at kubecon this week 15:06:49 Ironic, IPA, IPA-B all branches 15:06:57 I'll spot-check the networking repos 15:07:18 NGS/NBM both branched 15:07:33 and the prometheus exporter 15:07:45 if we remembered IPE; we remembered everything 🤞 15:08:00 XD 15:08:04 fair enough 15:08:25 nothing https://review.opendev.org/q/repo:openstack/releases+status:open here for ironic 15:08:28 so I call us good 15:08:38 branched means what in this context? these are release candidate branches? 15:08:51 🎉 15:08:52 I'm looking for `stable/2026.1` branches 15:09:00 it means we have cut a release and indicated it is a part of the stable release 15:09:33 does that mean the release is 'live' or does it now go through a release process? 15:09:36 for any of the projects that use a cycle-* model, that's the indicator that they've "branched". In cycle-with-rc (Ironic does NOT use this on any projects), the release from that stable/2026.1 branche could be an RC 15:10:01 In cycle-with-intermediary (Ironic projects, most of them), the release for the 2026.1 release is cut atomically with the branch 15:10:41 so at this point, all cycle-* deliverables (I think everything in Ironic sans virtualbmc/sushy-tools/clients) should have a stable/2026.1 branch, and in Ironic's case, that implies release automation already cut the release 15:11:22 clif: to be as specific as possible: https://opendev.org/openstack/releases/commit/e4ea04eff8d543f16447bc2b25a55aa4ffca549f this change led to both the releases and the branch cut 15:11:38 clif: iurygregory: Really, we should *also* validate the SHAs there map to the correct commits for the releases 15:11:52 and that we don't need to backport anything into stable/2026.1 branch 15:12:04 ++ 15:12:36 if those aren't a new enough commit, we backport stuff and add a key to that releases list with x.y.z+1 release and another sha 15:12:36 thanks for the rundown 15:12:39 I will check things 15:13:13 (or x.y+1.z or whatever based on changes, but generally for stable it should be patch releases only unless something exceptional is going on) 15:13:31 That ends OpenStack Ironic Release Engineering 101, please study for the final exam Tomorrow /s 15:13:35 #topic Working Group Updates 15:13:46 We have Async IO here and VXLAN. I think stuff is mostly done? 15:14:23 I'd suggest https://etherpad.opendev.org/p/ironic-asyncio and https://review.opendev.org/c/openstack/ironic-specs/+/972754 are good places to read if you're interested in asyncio+ironic. 15:14:30 Anything on any of our working groups before I move on? 15:15:17 Moving on. 15:15:23 #topic Discussion Topics 15:15:30 PTG is the only item here. 15:15:37 #link https://etherpad.opendev.org/p/ironic-ptg-2026.2#L16 15:15:47 cid has put together a rough/high level time allocation proposal for topics 15:15:58 please review it, if you have any concerns/questions/etc please work with cid 15:16:23 also as usual please make sure to take the time needed to review the PTG doc, participate in discussions/research async so we can reserve PTG time for discussing contention points :) 15:17:10 ++ 15:17:49 Alright. Our weak quorum is showing :D 15:17:53 #topic Bug Deputy Updates 15:18:01 I intend to update the Mailing list within the week 15:18:19 Mahnoor was the bug deputy last week. It looks like we have three new bugs that were in and triaged in NBM/NGS. 15:18:27 Mahnoor: anything to comment here? 15:19:43 I think it's public holiday for her, not sure she is around 15:19:52 Ah, she did mention that didn't she. 15:20:09 Full update is in the agenda, given the number of NGS/NBM patches floating around I'd be surprised if those aren't fixed or in progress already. 15:20:39 Who wants to be the bug deputy next week? 15:20:55 pick me 15:21:27 aight, cool, clif is the bug deputy for next week 15:21:49 and by next week, you mean... this week? 15:21:54 Mon-Mon 15:22:06 March 23 - March 30? 15:22:11 just make sure before you EOD on Friday, or Monday prior to meeting, you update agenda with results https://wiki.openstack.org/wiki/Meetings/Ironic 15:22:12 yep 15:22:43 PTG Review topic is empty, skipping. 15:22:48 #topic Open Discussion 15:22:58 Anything on anyones' mind that wasn't on the agenda? 15:23:21 I have one 15:23:44 #link https://bugs.launchpad.net/ironic/+bug/2141926 15:24:18 It reads straightforward, and you just brought it up in open discussion 15:24:24 what's the hidden tiger? :D 15:24:33 tl;dr basically some HPE has a chance to fail the updates because the PLDM channel may not be ready 15:24:49 I want to hear thoughts on the implementation before pushing upstream hehe 15:25:18 it seems like an extremely straightforward fix to me, but I don't know what I don't know 15:25:26 e.g. if hardware exists that this isn't true for 15:25:37 https://paste.opendev.org/show/b1YINYtLDLJKZtD5Nfms/ 15:25:46 this is a fix we tested downstream 15:26:47 would there be value in for line 20 15:26:51 making the default True? 15:27:05 So that if that attr is missing, we treat it similarly to how we did before? 15:27:16 not sure if using Updatable parameters is the right way to check, to me this would add much more overhead, since most vendors currently doesn't implement a reference to the right firmware_inventory 15:28:03 I think that is a good concern to raise at code review, but given it's needed for hardware compat, I think you'll need this code, the only question is if the behavior is optional/gated by a driver_info flag 15:28:16 JayF, at least according to the redfish docs the Updatable parameters would tell us if we can update that via redfish 15:28:18 unless you know some secretly better way to fix it you're hiding :D 15:28:22 nothing else 15:28:35 iurygregory: I'm saying existing code doesn't require that to exist; new code does. Has that attr always been in the standard? 15:28:50 iurygregory: with stuff like this, I just think defensively because I don't know the full array of hardware variety in the world 15:28:54 yeah, the att is in the standard 15:29:17 I only think its a bit overkill look at all entries in firmware inventory to find the right one 15:29:25 yeah 15:29:39 but like, we do a lot of overkill at times because hardware is terrible :) 15:29:57 like, new hardware might have this fixed and have the reference to the firmware_inventory and we could check things 15:30:22 even still the old gear that needs this code would exist though 15:30:33 IDK; I'd push it up and bring up your concerns in a self-review 15:30:46 curious if hjensas or dtantsur might have more expert feedback in that area for ya 15:31:52 gotcha 15:31:58 will do that JayF o/ 15:32:24 Any other items for Open Discussion? 15:34:39 Aight, last thing: who wants to volunteer to run the meeting next week? 15:34:58 i can run the meeting 15:34:59 These since-DST-8am meetings are trivial for me to keep running if nobody wants to; just offering the chair if desired. 15:35:11 Cool. You can have it Iury :) I'll be around and can backup if needed 15:35:21 #action iurygregory to chair the meeting next week 15:35:22 ack o/ 15:35:25 Thanks all o/ 15:35:26 #endmeeting