Monday, 2026-06-08

TheJuliahe wins the vacation contest00:52
opendevreviewMerged openstack/ironic master: Consolidate duplicated TLS code into ironic/common/tls_utils  https://review.opendev.org/c/openstack/ironic/+/98790903:56
opendevreviewRiccardo Pittau proposed openstack/ironic master: Fix kernel parameter parsing for quoted values and whitespace  https://review.opendev.org/c/openstack/ironic/+/99202507:16
rpittauthis ^ needs some attention :)07:17
*** elodilles_OoO is now known as elodilles08:36
opendevreviewKonstantinos Karampogias proposed openstack/ironic master: Add vendor/model/serial_number to firmware component endpoint  https://review.opendev.org/c/openstack/ironic/+/99203408:41
dtantsurrpittau: I'm really curious why both BMO and Bifrost are happy on https://review.opendev.org/c/openstack/ironic/+/99136509:35
dtantsurwhere did you notice the failure?09:35
opendevreviewKonstantinos Karampogias proposed openstack/ironic master: Add vendor/model/serial_number to firmware component endpoint  https://review.opendev.org/c/openstack/ironic/+/99203409:40
opendevreviewDmitry Tantsur proposed openstack/ironic master: DNM check standalone jobs with broken inspection  https://review.opendev.org/c/openstack/ironic/+/99220209:45
jandersTheJulia https://bugs.launchpad.net/ironic/+bug/2154614 done10:45
opendevreviewOpenStack Release Bot proposed openstack/ironic-python-agent bugfix/11.6: Update .gitreview for bugfix/11.6  https://review.opendev.org/c/openstack/ironic-python-agent/+/99220710:46
opendevreviewJacob Anders proposed openstack/ironic-specs master: Add spec for multi-component batched firmware updates  https://review.opendev.org/c/openstack/ironic-specs/+/99220810:46
opendevreviewJacob Anders proposed openstack/ironic-specs master: Add spec for multi-component batched firmware updates  https://review.opendev.org/c/openstack/ironic-specs/+/99220810:47
rpittaudtantsur: I've noticed the failure downstream11:15
dtantsurrpittau: puzzling. I don't think we even use kernel parameters downstream..11:21
dtantsurWe definitely cover inspection in standalone jobs as evident by https://review.opendev.org/c/openstack/ironic/+/99220211:22
opendevreviewJacob Anders proposed openstack/ironic-specs master: Add spec for multi-component batched firmware updates  https://review.opendev.org/c/openstack/ironic-specs/+/99220811:39
opendevreviewJacob Anders proposed openstack/ironic-specs master: Add spec for multi-component batched firmware updates  https://review.opendev.org/c/openstack/ironic-specs/+/99220811:41
opendevreviewJacob Anders proposed openstack/ironic-specs master: Add spec for multi-component batched firmware updates  https://review.opendev.org/c/openstack/ironic-specs/+/99220811:42
hjensasLast PTG we talked about gathering all "touch network devices" code in NGS. I proposed a series of changes to migrate the ML2 Netconf drive in networking-baremtal that need reviews. https://review.opendev.org/q/topic:%22netconf%2212:07
opendevreviewcid proposed openstack/ironic master: Stop skipping Redfish vmedia insert on stale BMC state  https://review.opendev.org/c/openstack/ironic/+/99092512:22
TheJuliagood morning13:12
opendevreviewKonstantinos Karampogias proposed openstack/ironic master: Add vendor/model/serial_number to firmware component endpoint  https://review.opendev.org/c/openstack/ironic/+/99203413:19
opendevreviewHarald JensĂĄs proposed openstack/networking-generic-switch master: Pass physnet VLAN segments to device drivers  https://review.opendev.org/c/openstack/networking-generic-switch/+/99051013:38
dtantsurI'm looking at BMO job logs and thinking that I"m probably going fully insane (finally): https://paste.opendev.org/show/bsrbdhKMUyzzbjJ9q6PZ/14:18
dtantsurTheJulia: any idea how references to "metalsmith" could get there ^^? O_o14:18
* TheJulia blinks14:19
TheJuliano idea, base image starting point maybe?14:20
dtantsurTheJulia: the image is built by Ironic...14:20
TheJuliavmedia attachment with sushy-tools?14:21
dtantsurTheJulia: yep14:22
dtantsurThis is *without* actual network data provided. I wonder if Ironic can set a non-sensual value in this case..14:23
TheJuliapre-baked ISO ?14:23
dtantsurTheJulia: to my best knowledge, no.. I'll double-check14:24
TheJuliaYeah, I think we retain and carry across values14:24
dtantsurTheJulia: the problem is: we also set ir_pub_id, so the start-up job loops 30 seconds before bailing and letting IPA continue14:25
dtantsurit's half a minute for each test run14:25
TheJuliayeah, seems super weird because I have no idea where that values is coming from14:26
dtantsurI don't see any reference to metalsmith anywhere. The command line seems correct.14:26
* dtantsur is finally insane, yay14:26
dtantsurIn the ironic logs, I see a reasonable publisher provided14:27
dtantsurAhhh, wait, it's a configdrive picked up from the disk. Cirros?14:29
dtantsurTheJulia: shouldn't we bail immediately on publisher_id that is not empty and does not match the expected one?14:29
TheJuliadtantsur: "finallly"?14:30
TheJuliadtantsur: oh yeah, since it looks like a disk I guess14:30
TheJuliadtantsur: likely we should do that14:30
* dtantsur files a bug14:30
dtantsurIt was quite intentional in https://opendev.org/openstack/ironic-python-agent-builder/commit/96d997f15f9f8a3c8d155a665a2ce0972d34cc61 though14:33
dtantsurRight, yeah, their reasoning is not terrible14:33
dtantsurTheJulia: maybe it's the opposite situation: we should not create a publisher ID if there is no configuration to inject?14:35
* TheJulia shrugs14:35
TheJuliaAlternatively, we should validate more aggressively that the volume *IS* a vmedia ISO I guess and not a local disk.14:36
TheJuliaremoving the publisher ID prevents us from blocking/locking out afaik14:36
dtantsurI'd not bet on all virtual media implementation doing the right thing..14:36
dtantsurright14:36
TheJuliayeah, I think my concern is if we special case it out, then we re-create the same issue we were seeking to avoid originally14:36
TheJuliaor at least, begin heading back in that direction14:37
* dtantsur thinks again14:37
dtantsurHold on, it does not make any sense. If we create a publisher ID and pass it through the kernel params, why doen's the script find the device?14:37
* dtantsur thinks more14:37
dtantsurProbably because we create a publisher ID but do not use the label config-214:38
TheJuliaI think we do use the config-2 label, but you risk a local partition already having the label14:40
TheJuliathe publisher_id is the only way we have in the code path to identify and match up volume to boot14:40
dtantsurMaybe use config-2 unconditionally?14:40
dtantsurAnyway, I've filed https://bugs.launchpad.net/ironic-python-agent-builder/+bug/2155910. I'm surely not going to find time for this too..14:41
TheJuliaoh yeah, so we should disqualify a device which is not labeled14:41
TheJuliawhich would prevent the issue youre encountering14:41
dtantsurthe problem is that the local partition is labeled and the ISO is not14:42
TheJuliathen there was no data injected?14:42
dtantsurTheJulia: no data and nothing is really broken, except that we're waiting for publisher ID that is never going to appear14:44
TheJuliaYeah, we should likely create a list of "I've seen this already, and its not it"14:45
TheJuliaand wait out the loop otherwise, but you still have the pause14:45
dtantsurOh! I think we need a short-cut in case where a device with the publisher ID exists but does not have label config-214:45
TheJuliading ding ding14:46
opendevreviewMichal Nasiadka proposed openstack/bifrost master: [WIP] Experimental support for ARM64 hosts on Debian  https://review.opendev.org/c/openstack/bifrost/+/92005714:48
TheJuliaEveryone getting caffinated?14:56
JayFI just sat down 5 minutes ago with a cuppa joe and donut from the local donut shop14:58
TheJuliayum14:58
JayFhowever I am NOT sufficiently caffinated, because their coffee machine temp is set to "surface of sun"14:58
TheJuliaIs that more or less than "Mcdonalds scald" ?14:59
JayFit's so hot it hurts to hold even with the little coffee jacket installed15:00
JayF#startmeeting ironic15:00
opendevmeetMeeting started Mon Jun  8 15:00:09 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
JayFHey all, welcome to the Ironic meeting. We're following the OpenInfra Code of Conduct.15:00
JayFAgenda is at https://wiki.openstack.org/wiki/Meetings/Ironic15:00
JayF#topic Announcements/Reminders15:00
JayFPlease review things hashtag:ironic-week-prio. Need reviews? Add that hashtag.15:00
JayF#link https://tinyurl.com/ironic-weekly-prio-dash15:00
kubajjo/15:01
JayFI'll give us a few minutes for quorum to develop15:01
rpittauo/15:01
TheJuliao/15:01
Mahnooro/15:01
* TheJulia wonders if a "qourum compiler" exists15:01
dtantsuro/15:01
mumesan[m]o/15:03
cido/15:04
JayFAlright! First up15:05
JayF#topic Working Group Updates15:05
JayFAnything to speak to here around Async IO?15:05
JayFThat's a lot of silence I'm going to take as a no.15:06
JayFThe other working group item I added here was around Security15:06
JayFfor some context; there's an Ironic "coresec" team -- myself, TheJulia, rpittau, dtantsur -- we are the folks who initially get access to security sensitive bug reports and deal with their disposition.15:07
JayFAnd we've been busy!15:07
TheJuliaexceptionally so.15:07
JayFLast week, Ironic released three OSSA (advisories) and one OSSN (note). 15:07
JayF#link https://security.openstack.org/ossa/OSSA-202615:08
JayF#undo15:08
opendevmeetRemoving item from minutes: #link https://security.openstack.org/ossa/OSSA-202615:08
JayF#link https://security.openstack.org/ossa/OSSA-2026-017.html15:08
JayF#link https://security.openstack.org/ossa/OSSA-2026-018.html15:08
JayF#link https://security.openstack.org/ossa/OSSA-2026-019.html15:08
JayF#link https://wiki.openstack.org/wiki/OSSN/OSSN-009915:09
JayFPlease let someone know if you have any issue with the fixes.15:10
JayF#topic Discussion Topics15:10
JayFImprovement to firmware updates -- PTG followup has iurygregory (not here?) and janders listed15:10
dtantsurI think the conversation happened last time15:11
MahnoorI *think* this was done last meeting, yes15:11
JayFack; moving on15:11
JayF#topic Bug Deputy Updates15:11
TheJuliaSort of did, jacob followed up with an initial spec super early this morning15:11
JayFMahnoor is listed as bug deputy15:11
JayF#undo15:12
opendevmeetRemoving item from minutes: #topic Bug Deputy Updates15:12
Mahnoor3 new bugs in ironic, and 1 RFE15:12
JayFTheJulia: the spec isn't attached to the bug in the agenda15:12
JayFMahnoor: hang on, wanna make sure janders' work gets recognized properly 15:12
Mahnoorack15:12
JayF#link https://review.opendev.org/c/openstack/ironic-specs/+/99220815:12
JayFPlease take time and review the spec posted by janders this morning :)15:13
JayFnow to kick it over to Mahnoor :D 15:13
JayF#topic Bug Deputy Updates15:13
MahnoorThere were 3 new bugs in ironic :)15:13
MahnoorI've mentioned in the notes the links15:13
JayFDo we have a volunteer to bug deputy next week?15:14
cidI don't mind.15:15
JayF#action cid is bug deputy next week15:15
cidBy the way, kudos to the coresec team on security fixes so far15:15
Mahnoor++, must be a lot15:16
cidYup :-) 15:16
JayF#topic RFE Review15:16
JayFWe have one listed in here, hopefully not stale15:16
JayF#link https://bugs.launchpad.net/ironic/+bug/215481715:17
JayFit was commented that it was a duplicate of15:17
JayF#link https://bugs.launchpad.net/ironic/+bug/209869315:17
MahnoorIts part of Outreachy, it says. But I was a little confused by multiple people working on it..and why there was a need to duplicate15:18
MahnoorIts not a crisis though :)15:18
TheJuliai, too, have been confused about this15:18
JayFa lot of the things being worked on are things we'd often ask for a spec for, too 15:19
JayFlike API changes15:19
rpittaume too, and I'm directly involved :D15:19
JayFit seemed a little weird to have a bunch of new folks drop in working on an API change we didn't have specified15:19
rpittauthat was a misunderstanding15:19
TheJuliarpittau: even better!15:19
JayFI know we are often loosey goosey with specs so I didn't wanna assume lol15:19
TheJuliaI feel like, yes, there is a validity to what multiple folks seem to be trying to drive forward15:20
TheJuliaThere are some baseline challenges though, I want them all to be successful15:20
TheJuliaobviously, that is not *always* possible15:21
rpittauwe've reduced the scope of https://review.opendev.org/c/openstack/ironic/+/98334915:21
rpittauour outreachy intern estherd[m] will work on the rest15:21
TheJuliais this just a case of others seeing the project and maybe thinking they could possibly still qualify if they go work it separately?15:21
rpittauno, it was mistaken as something open to all the outreachy candidates15:22
Mahnooror they thought it was part of the contribution phase? 🤔15:22
rpittauyeah15:22
TheJuliaoh, i see15:22
rpittaukind of15:22
JayFSo we should mark that new bug as a dupe? Or the old one?15:24
JayFWhat's the adjudication here for Mahnoor to execute15:24
rpittaunot a duplicate, we'll close the fdirst one once the relataed patch merges15:24
JayFack, okie dokie :D 15:25
rpittauthanks :)15:25
JayF#topic Open Discussion15:25
JayFAnything to discuss not on the agenda?15:25
TheJuliai've got nothing right now15:26
TheJuliaoh!15:26
TheJuliaLast call for: https://review.opendev.org/c/openstack/ironic-specs/+/95461215:26
TheJuliaAnd we can close out the  meeting then15:28
JayFnope, one more15:28
JayFWho is chairing next week?15:28
JayFDo we have a volunteer?15:28
TheJuliaI can15:29
JayFsgtm, 15:29
JayF#action TheJulia to emcee the next meeting15:29
JayFThanks all, meeting over o/15:29
JayF#endmeeting15:29
opendevmeetMeeting ended Mon Jun  8 15:29:19 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:29
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-06-08-15.00.html15:29
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-06-08-15.00.txt15:29
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-06-08-15.00.log.html15:29
rpittauthanks15:29
opendevreviewMerged openstack/ironic-specs master: Deferred Actions  https://review.opendev.org/c/openstack/ironic-specs/+/95461216:10
opendevreviewJulia Kreger proposed openstack/ironic master: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99043016:30
opendevreviewClif Houck proposed openstack/ironic master: Add a custom configuration type KernelParameterString  https://review.opendev.org/c/openstack/ironic/+/99230616:31
opendevreviewClif Houck proposed openstack/ironic master: Add kernel parameter parsing to create_boot_iso  https://review.opendev.org/c/openstack/ironic/+/99230716:31
opendevreviewClif Houck proposed openstack/ironic master: Add kernel parameter parsing to build_extra_pxe_options  https://review.opendev.org/c/openstack/ironic/+/99230816:31
opendevreviewClif Houck proposed openstack/ironic master: Rip out and replace ironic.common.utils.parse_kernel_params  https://review.opendev.org/c/openstack/ironic/+/99230916:31
opendevreviewJulia Kreger proposed openstack/ironic stable/2026.1: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99232117:23
opendevreviewJulia Kreger proposed openstack/ironic bugfix/34.0: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99232217:31
opendevreviewJulia Kreger proposed openstack/ironic bugfix/33.0: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99232317:32
opendevreviewJulia Kreger proposed openstack/ironic stable/2025.2: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99232517:35
opendevreviewJulia Kreger proposed openstack/ironic stable/2025.1: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99232617:36
opendevreviewJulia Kreger proposed openstack/ironic unmaintained/2024.1: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99233317:52
opendevreviewJulia Kreger proposed openstack/ironic unmaintained/2023.1: Security: Fix sensitive properties returned on volume targets  https://review.opendev.org/c/openstack/ironic/+/99233518:18
opendevreviewMerged openstack/ironic master: Fix kernel parameter parsing for quoted values and whitespace  https://review.opendev.org/c/openstack/ironic/+/99202518:20
TheJuliaRandom off the wall question, would it make sense to have a sort of mid-cycle long discussion call to enable mid-cycle alignment for contributors?18:33
JayFI don't hate the idea; I'd hit the list with it though so we catch contributors who are usually sleeping now18:37
TheJuliatrue18:39
opendevreviewClif Houck proposed openstack/ironic stable/2026.1: Fix kernel parameter parsing for quoted values and whitespace  https://review.opendev.org/c/openstack/ironic/+/99234018:54
opendevreviewMerged openstack/ironic-python-agent bugfix/11.6: Update .gitreview for bugfix/11.6  https://review.opendev.org/c/openstack/ironic-python-agent/+/99220719:09
opendevreviewClif Houck proposed openstack/ironic stable/2025.2: Fix kernel parameter parsing for quoted values and whitespace  https://review.opendev.org/c/openstack/ironic/+/99234119:24
opendevreviewClif Houck proposed openstack/ironic stable/2025.1: Fix kernel parameter parsing for quoted values and whitespace  https://review.opendev.org/c/openstack/ironic/+/99234519:41
opendevreviewJacob Anders proposed openstack/ironic-specs master: Add spec for multi-component batched firmware updates  https://review.opendev.org/c/openstack/ironic-specs/+/99220821:16
jandersJayF TheJulia updated https://review.opendev.org/c/openstack/ironic-specs/+/992208 (firmware updates improvement spec) to link to the RFE/bug - thanks for pointing that out21:18
janders(had the reference in the spec itself but forgot to put it on the change also)21:18
opendevreviewClif Houck proposed openstack/ironic bugfix/34.0: Fix kernel parameter parsing for quoted values and whitespace  https://review.opendev.org/c/openstack/ironic/+/99236721:40
sean-k-mooneyTheJulia: midcycels can be prodcutive, adopting a 6-10 week release cycle like the kernel would be even better IMO21:40
sean-k-mooneybut ya i have codnierd doign one in the past, it been a long time since i attened a midcycle for any of the project im in vovled with regually but my memory was they were useful21:42
TheJuliaIronic already does that, fwiw. Anyhow, I was more proposing the idea of a long video call to sync folks up because of just how insane this cycle is turning out21:42
sean-k-mooneyya i was thinkign fo proposign one for the agentic workflows repo because we didnt really have time at the ptg and we have all been too busy to get back to that topic21:43
TheJuliaAnyway, back to exercising becuase they won't let me find out if I have to report for jury duty tomorrow for a few more hours *cries*21:43
sean-k-mooneyso i would like to do something this cycle there but i feel like we need to get concenous on it first21:44
TheJuliaYeah, that is the downside of the PTG Model... without the human interaction, you really have to keep hammering items forward21:44
TheJuliabecause your also building mindshare/critical mass21:44
TheJuliaand that is even harder without the ability to hallway track and share context21:44
sean-k-mooneyyep the lack of the hallway/evening  track too do that is a downside21:44
opendevreviewClif Houck proposed openstack/ironic bugfix/33.0: Fix kernel parameter parsing for quoted values and whitespace  https://review.opendev.org/c/openstack/ironic/+/99236821:46
TheJuliaIt is interesting, because at the Summit last year, I was able to have some hallway track discussions which then got carried forward into standards bodies discussions to generally just get things to a better place overall.21:46
TheJuliaAnyway, exercise, the clock is still running21:46
sean-k-mooneyo/21:47
davidHello, I am new to Ironic but am very happy with what I have working so far with it. One of the final steps for us is getting it working with MDADM raid for the / volume. We normally use LVM here to allow resizing of partitions over the life of the instance. From what I'm seeing in the docs this isn't currently supported. Is the correct approach here to work on writing a implementation using a custom HardwareManager and building 22:11
davidwork on this project so far, it's far more advanced that any of the other bare metal management tools I've looked at over the years with Foreman/Maas.22:12
TheJuliaHi david 22:14
TheJuliadavid: I guess it sort of depends on where your coming from and how much ?pain? (is pain the right word? I'm not really sure) your willing to deal with. Ultimately RAIDing on deploy is a difficult topic made worse by ecosystem constraints outside of Ironic. For example, default bootloader binaries lacking raid support out of the box.22:16
TheJuliaWhich is sort of why RAID support is in a documented limbo of sorts, people obviously see it as a solution, but... It'ts not always the best solution and in the end its a bit harder to support project wise. Granted, there are RAID operators out there. CERN specificially does do raid boot and root volumes and uploads patches from time to time.22:17
davidTheJulia: Thanks. Currently i'm building the image with packer and kickstart files to setup the base system, packages, install mdadm, cloud init etc. Our typical deployment is just mirror two boot devices with 3 partitions on each disk. (part1: for ESP (no raid, seperate mount points and a cron rsync job to keep the ESP in sync.) part2: 2GB /boot raid1 mdadm, part3: raid1 mdadm that houses pv.0 where we make the lvm partitions fo22:24
TheJuliafair enough, that should basically work22:26
TheJuliahttps://docs.openstack.org/ironic/latest/admin/raid.html#software-raid is the latest with a nice warning that I was alluding to22:28
TheJuliaThats a little different, fwiw, but if there are mild changes which you could use to the RAID support in the agent, we could likely accept them into the codebase without too much hassle. If you want to match what you've already been doing exactly, I'd recommend a hardware manager, but I've not tried anything like that as it relates to raid.22:30
davidYup thanks, I was looking at thouse docs and came across the bullet point of "Images utilizing LVM for their root filesystem are not supported. Patches are welcome to explicitly support such functionality." Which led me to wonder why lvm root works for a non mdadm build (I have it working in my testing just fine.) but apparently doesn't when using the buildin raid support in ironic.22:31
davidThanks for pointing me in the right direction. I'll start looking at the source code and see where I land at for writing something. There's a few other features I'd love to see such as defining which disks to mdadm based on disk vendor ID/serial on a per-node basis. (We have a lot of nodes where there's 2 drives used for boot and lots of other drives used for ceph osds for example etc.)22:36
TheJuliaOh, oh!  Yeah, LVM based… I haven’t tried. I wonder if CERN has tried.22:36
davidYeah for us we use a mdadm to build a /boot. then we build another mdadm mirror out of part3 and create a LVM PV on that which we then create partitions for /var /var/log and /.22:37
TheJuliaYeah, disk selection wise, check the ironic-python-agent source. I think the software raid code is much simpler but with a device ignore model22:37

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