Monday, 2026-03-23

opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: PLDM channel not initialized after BMC update  https://review.opendev.org/c/openstack/ironic/+/97670600:00
opendevreviewKaran Anand proposed openstack/python-ironicclient master: Add type annotations to `ironicclient/osc/v1/baremetal_volume_connector.py`  https://review.opendev.org/c/openstack/python-ironicclient/+/98169700:40
opendevreviewKaran Anand proposed openstack/python-ironicclient master: Add type annotations to `ironicclient/osc/v1/baremetal_allocation.py`  https://review.opendev.org/c/openstack/python-ironicclient/+/98169800:40
opendevreviewKaran Anand proposed openstack/python-ironicclient master: Add type annotations to `ironicclient/osc/v1/baremetal_inspection_rule.py`  https://review.opendev.org/c/openstack/python-ironicclient/+/98169900:41
opendevreviewJacob Anders proposed openstack/sushy master: Revert "Skipping UsbCd workaround on Supermicro ARS-111GL-NHR"  https://review.opendev.org/c/openstack/sushy/+/98108900:58
janderscardoe ^ should address your (very valid) concern. Well spotted.01:01
amanHi everyone! I’m Aman, an Outreachy applicant interested in the Ironic project, especially around node history APIs. I’m currently exploring the project and working on the initial tasks. Looking forward to learning and contributing.06:39
hroyhello and welcome outreachy applicants, we will soon share share details for next steps. In the meantime feel free to go through the project documentation06:58
FreemanBoss[m]Alright. Thank you hroy ./07:55
opendevreviewOlamide Ojo proposed openstack/ironic master: write tasks as clear, step-by-step procedures for enrollment file.  https://review.opendev.org/c/openstack/ironic/+/98171108:48
*** jayita10[m] is now known as JayitaPramanik[m]09:26
opendevreviewOlamide Ojo proposed openstack/ironic master: write tasks as clear, step-by-step procedures for troubleshooting file  https://review.opendev.org/c/openstack/ironic/+/98172210:04
opendevreviewOlamide Ojo proposed openstack/ironic master: write tasks as clear, step-by-step procedures for troubleshooting file  https://review.opendev.org/c/openstack/ironic/+/98172210:06
opendevreviewOlamide Ojo proposed openstack/ironic master: write tasks as clear, step-by-step procedures for enrollment file.  https://review.opendev.org/c/openstack/ironic/+/98171110:46
*** sonalisk is now known as tempo11:30
*** sonalisk_ is now known as sonalisk11:30
iurygregorygood morning ironic12:21
opendevreviewOlamide Ojo proposed openstack/ironic master: write task as clear, step-by-step procedure for configuration file  https://review.opendev.org/c/openstack/ironic/+/98175512:31
opendevreviewOlamide Ojo proposed openstack/ironic master: write task as clear, step-by-step procedures for upgrade-guide file  https://review.opendev.org/c/openstack/ironic/+/98178114:31
clifgm o/14:34
JayF#startmeeting ironic 15:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'ironic'15:00
JayFGooooood morning and welcome to the Ironic meeting. We're operating under the OpenInfra Code of Conduct as usual.15:00
JayFI'll give a minute or five for people to trickle in.15:00
iurygregoryo/15:00
mumesan[m]o/15:00
clifo/15:02
cido/15:03
FreemanBoss[m]o/15:03
opendevreviewOlamide Ojo proposed openstack/ironic master: Improve reference consistency of the intel-ipmi file  https://review.opendev.org/c/openstack/ironic/+/98178915:03
JayFLooks like weak quorum if quorum at all :)15:04
JayFI hope folks are off enjoying the downtime between releases, at least15:04
JayF#topic Announcements/Reminders15:04
JayF#link https://tinyurl.com/ironic-weekly-prio-dash15:04
JayFPlease review changes hashtagged ironic-week-prio15:04
JayFIf you have patches ready for review, passing CI, good to go, add hashtag "ironic-week-prio" to get them onto this dashboard15:04
JayF#link https://releases.openstack.org/gazpacho/schedule.html15:05
JayFWe spent 6 months making a cold soup, and it's here :) 15:05
JayFThis is R-1 week: last chance to cut any releases.15:05
JayFThere is an open question in the agenda: is all our stuff released?15:05
JayFI don't know the answer for this for sure, I hope it's "yes"?15:06
cidWeak quorum for sure15:06
iurygregoryI saw we cut off a lot of branches last week15:06
iurygregoryI can double check, riccardo is at kubecon this week15:06
JayFIronic, IPA, IPA-B all branches15:06
JayFI'll spot-check the networking repos15:06
JayFNGS/NBM both branched15:07
JayFand the prometheus exporter15:07
JayFif we remembered IPE; we remembered everything 🤞15:07
iurygregoryXD15:08
iurygregoryfair enough15:08
JayFnothing https://review.opendev.org/q/repo:openstack/releases+status:open here for ironic15:08
JayFso I call us good15:08
clifbranched means what in this context? these are release candidate branches?15:08
cardoe🎉15:08
JayFI'm looking for `stable/2026.1` branches15:08
JayFit means we have cut a release and indicated it is a part of the stable release15:09
clifdoes that mean the release is 'live' or does it now go through a release process?15:09
JayFfor 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 RC15:09
JayFIn cycle-with-intermediary (Ironic projects, most of them), the release for the 2026.1 release is cut atomically with the branch15:10
JayFso 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 release15:10
JayFclif: to be as specific as possible: https://opendev.org/openstack/releases/commit/e4ea04eff8d543f16447bc2b25a55aa4ffca549f this change led to both the releases and the branch cut15:11
JayFclif: iurygregory: Really, we should *also* validate the SHAs there map to the correct commits for the releases15:11
JayFand that we don't need to backport anything into stable/2026.1 branch15:11
iurygregory++15:12
JayFif 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 sha15:12
clifthanks for the rundown15:12
iurygregoryI will check things15:12
JayF(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
JayFThat ends OpenStack Ironic Release Engineering 101, please study for the final exam Tomorrow /s15:13
JayF#topic Working Group Updates15:13
JayFWe have Async IO here and VXLAN. I think stuff is mostly done?15:13
JayFI'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
JayFAnything on any of our working groups before I move on?15:14
JayFMoving on.15:15
JayF#topic Discussion Topics15:15
JayFPTG is the only item here.15:15
JayF#link https://etherpad.opendev.org/p/ironic-ptg-2026.2#L1615:15
JayFcid has put together a rough/high level time allocation proposal for topics15:15
JayFplease review it, if you have any concerns/questions/etc please work with cid 15:15
JayFalso 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:16
cid++15:17
JayFAlright. Our weak quorum is showing :D 15:17
JayF#topic Bug Deputy Updates15:17
cidI intend to update the Mailing list within the week15:18
JayFMahnoor was the bug deputy last week. It looks like we have three new bugs that were in and triaged in NBM/NGS.15:18
JayFMahnoor: anything to comment here?15:18
iurygregoryI think it's public holiday for her, not sure she is around15:19
JayFAh, she did mention that didn't she.15:19
JayFFull 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
JayFWho wants to be the bug deputy next week?15:20
clifpick me15:20
JayFaight, cool, clif is the bug deputy for next week15:21
clifand by next week, you mean... this week?15:21
JayFMon-Mon15:21
clifMarch 23 - March 30?15:22
JayFjust make sure before you EOD on Friday, or Monday prior to meeting, you update agenda with results https://wiki.openstack.org/wiki/Meetings/Ironic15:22
JayFyep15:22
JayFPTG Review topic is empty, skipping.15:22
JayF#topic Open Discussion15:22
JayFAnything on anyones' mind that wasn't on the agenda?15:22
iurygregoryI have one15:23
iurygregory#link https://bugs.launchpad.net/ironic/+bug/214192615:23
JayFIt reads straightforward, and you just brought it up in open discussion15:24
JayFwhat's the hidden tiger? :D 15:24
iurygregorytl;dr basically some HPE has a chance to fail the updates because the PLDM channel may not be ready15:24
iurygregoryI want to hear thoughts on the implementation before pushing upstream hehe15:24
JayFit seems like an extremely straightforward fix to me, but I don't know what I don't know15:25
JayFe.g. if hardware exists that this isn't true for15:25
iurygregoryhttps://paste.opendev.org/show/b1YINYtLDLJKZtD5Nfms/15:25
iurygregorythis is a fix we tested downstream15:25
JayFwould there be value in for line 20 15:26
JayFmaking the default True?15:26
JayFSo that if that attr is missing, we treat it similarly to how we did before?15:27
iurygregorynot 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_inventory15:27
JayFI 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 flag15:28
iurygregoryJayF, at least according to the redfish docs the Updatable parameters would tell us if we can update that via redfish15:28
JayFunless you know some secretly better way to fix it you're hiding :D 15:28
iurygregorynothing else15:28
JayFiurygregory: I'm saying existing code doesn't require that to exist; new code does. Has that attr always been in the standard?15:28
JayFiurygregory: with stuff like this, I just think defensively because I don't know the full array of hardware variety in the world15:28
iurygregoryyeah, the att is in the standard15:28
iurygregoryI only think its a bit overkill look at all entries in firmware inventory to find the right one15:29
JayFyeah15:29
JayFbut like, we do a lot of overkill at times because hardware is terrible :)15:29
iurygregorylike, new hardware might have this fixed and have the reference to the firmware_inventory and we could check things15:29
JayFeven still the old gear that needs this code would exist though15:30
JayFIDK; I'd push it up and bring up your concerns in a self-review15:30
JayFcurious if hjensas or dtantsur might have more expert feedback in that area for ya15:30
iurygregorygotcha15:31
iurygregorywill do that JayF o/15:31
JayFAny other items for Open Discussion?15:32
JayFAight, last thing: who wants to volunteer to run the meeting next week?15:34
iurygregoryi can run the meeting15:34
JayFThese since-DST-8am meetings are trivial for me to keep running if nobody wants to; just offering the chair if desired.15:34
JayFCool. You can have it Iury :) I'll be around and can backup if needed15:35
JayF#action iurygregory to chair the meeting next week15:35
iurygregoryack o/15:35
JayFThanks all o/15:35
JayF#endmeeting15:35
opendevmeetMeeting ended Mon Mar 23 15:35:26 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:35
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-03-23-15.00.html15:35
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-03-23-15.00.txt15:35
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-03-23-15.00.log.html15:35
mumesan[m]o/15:35
JayFhttps://wiki.openstack.org/wiki/Meetings/Ironic updated for the 3/30 meeting15:43
opendevreviewOlamide Ojo proposed openstack/ironic master: Improve reference consistency of the drivers file  https://review.opendev.org/c/openstack/ironic/+/98179815:49
opendevreviewMerged openstack/sushy master: Revert "Skipping UsbCd workaround on Supermicro ARS-111GL-NHR"  https://review.opendev.org/c/openstack/sushy/+/98108916:13
opendevreviewDoug Goldstein proposed openstack/python-ironicclient master: add node trait add/remove commands and deprecate node add/remove trait  https://review.opendev.org/c/openstack/python-ironicclient/+/98180516:30
opendevreviewcid proposed openstack/ironic master: Fix pickle error when oslo.service uses spawn mode  https://review.opendev.org/c/openstack/ironic/+/97726616:47
opendevreviewcid proposed openstack/ironic master: Make CONF picklable for oslo.service's spawn probe  https://review.opendev.org/c/openstack/ironic/+/97878916:47
opendevreviewOlamide Ojo proposed openstack/ironic master: write tasks as clear, step-by-step procedures.  https://review.opendev.org/c/openstack/ironic/+/98180716:51
JayFchatter in #openstack-nova in nova meeting around ironic/nova-compute slowness16:56
JayFhttps://meetings.opendev.org/meetings/nova/2026/nova.2026-03-23-16.00.log.html#l-96 if folks wanna read it17:10
JayFtl;dr sean found some really gnarly stuff in the resource tracker in general17:10
JayFbut we need to validate against ironic; I'm going to spike on trying to make it easy to setup ironic in devstack with fake-driver nodes17:11
DELLHello Team19:44
chinnisreeaddagallaHi everyone! I'm Chinni Sree, an Outreachy 2026 applicant for the "Extend Ironic Node Deployment History API" project. I am excited to contribute and looking forward to learning from the community! Could anyone please guide me on how to start contributing? Are there any beginner-friendly issues I can work on?21:18
comfortoyewole[m]Welcome Chinnisreeaddagalla!21:23
comfortoyewole[m]you can start by following the instructions the mentors provided in this doc.21:23
comfortoyewole[m]https://docs.google.com/document/d/12SsPvSXdjNNw4C9IbkJGpW9qXwZYiZbENEgwgx815b4/edit?usp=sharing21:23
chinnisreeaddagallaThank you for the warm welcome! I truly appreciate the guidance. I have already begun working on the initial tasks and will continue to make progress. 21:27
Anishere_MariamHi everyone 👋 My name is Anishere Mariam Adeola. I’m currently working on the OpenStack Ironic Outreachy tasks. I’ve been exploring Bifrost and learning how bare metal provisioning works.  Looking forward to learning from the community and contributing!21:41

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