Friday, 2026-03-20

opendevreviewJacob Anders proposed openstack/sushy master: Revert "Skipping UsbCd workaround on Supermicro ARS-111GL-NHR"  https://review.opendev.org/c/openstack/sushy/+/98108900:10
cardoeAnyone on that's got some boxes they'd be happy to share a "openstack baremetal node -f yaml $NODE_ID > node.yaml" and "openstack baremetal node inventory save -o inventory.json $NODE_ID". Feel free to sanitize first.02:39
opendevreviewDoug Goldstein proposed openstack/ironic master: Add Zuul job to test inspection rules tester  https://review.opendev.org/c/openstack/ironic/+/98142303:04
opendevreviewDoug Goldstein proposed openstack/ironic master: add GitHub Action for inspection rules testing  https://review.opendev.org/c/openstack/ironic/+/98142403:04
cardoeGlimmr_: I just ported our GitHub Action to the Ironic repo. And made a Zuul test for running it in Gerrit. That should give you an idea how you can use that. If we do in fact have a bug, let's add some test data with an example rule to exercise the bug.03:07
cardoeOne of the things we're still lacking is one more thing of "expected" so like the rule can succeed against the node but need to check that it mutated the data correctly.03:08
cardoeA number of the hooks can probably be re-implemented as rules in the engine and we can validate this stuff ahead of time.03:09
cardoeIf we're cool with it I can toss a couple of machines into that.03:21
cardoeWe're not actually using rules yet but I think it's got a lot of promise.03:25
rpittaugood morning ironic! happy friday ! o/06:51
abongalegood morning ironic 0/07:37
fricklerthat ESP copying idea is really nice indeed08:25
opendevreviewVictor proposed openstack/ironic master: Record VIF attach/detach failures in node history  https://review.opendev.org/c/openstack/ironic/+/98145908:43
victor_obi_Good day! I am looking at bug #2100707 (Node history API alignment). Is this a suitable task for me to attempt as a contribution right now, or is there a specific roadmap for this issue that I should be aware of?. Thank you.09:05
opendevreviewVictor proposed openstack/ironic master: Log node history on vif_attach and vif_detach failures  https://review.opendev.org/c/openstack/ironic/+/98147410:22
victor_obi_Hi, I've submitted my second patch for bug #2131973 (vif_attach/vif_detach should log failures to node history): https://review.opendev.org/c/openstack/ironic/+/981474 — took a bit longer due to sorting out some git branching issues but it's clean now. All feedbacks are appreciated.10:26
opendevreviewHarald Jensås proposed openstack/networking-baremetal master: Refactor to use guard clauses and early returns  https://review.opendev.org/c/openstack/networking-baremetal/+/98147910:48
opendevreviewHarald Jensås proposed openstack/networking-baremetal master: Add segment_id to subport binding profiles  https://review.opendev.org/c/openstack/networking-baremetal/+/98148011:13
victor_obi_Hi, I've now submitted two patches (#981399 and #981474). Are there any other node history related issues I could help with?11:25
MahnoorHello o/ I will be out on Monday, so I've left the bug deputy updates in the meeting agenda (just 2 new bugs)11:51
rpittauthanks Mahnoor :)12:13
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Use segment_id for L2VNI cleanup  https://review.opendev.org/c/openstack/networking-generic-switch/+/98150912:44
opendevreviewHarald Jensås proposed openstack/networking-baremetal master: Refactor to use guard clauses and early returns  https://review.opendev.org/c/openstack/networking-baremetal/+/98147913:03
opendevreviewHarald Jensås proposed openstack/networking-baremetal master: Simplify conditional logging for link information  https://review.opendev.org/c/openstack/networking-baremetal/+/98151413:20
cardoefrickler: ESP copying?13:46
opendevreviewHarald Jensås proposed openstack/networking-baremetal master: Fix ha_chassis_group list access in trunk manager  https://review.opendev.org/c/openstack/networking-baremetal/+/98151513:46
TheJuliacardoe: software raid + ironic + uefi13:47
cardoeAh13:47
fricklerhttps://review.opendev.org/c/openstack/ironic-python-agent/+/981403 to be more specific13:59
TheJuliaI really love the lockout/tagout spec cid, a couple items commented in-line. I feel like there is a huge question regarding do we support multiple concurrent lockouts, or singular. I guess the underlying challenge of the unknown is how we shape the rbac model and the interaction. It feels a little weird that we have the other table if its entirely singular.14:10
Glimmr_cardoe: I have looked into the tester.py you mentioned & the yaml next to it. Even with that notation it seems to not work for me, as the last error on the nodes details show(>: not supported between instances of dict and int). 14:28
Glimmr_I now start doubting it could be due to my deployment method here(kayobe), as using the example from the repo got registered on the openstack cli with {'inventory.memory.physical': None}14:28
cidTheJulia, thanks I will take a look at your comments. About handling concurrency requests, it will likely depend on how we write the API14:31
cidMy understanding is that the bulk actions API will be right endpoint for multiple lockout requests14:32
TheJuliaAre you aware of how lockout/tagout might work at a physical data center?14:32
cidI have tried to imagine it, so I do have a working picture in mind :D14:33
cardoeTheJulia: We plop a person in front of the rack and they glare at anyone that tries to touch the box?14:33
TheJuliaI'd encourage us to imagine "someone got started" and "someone else went to go join in the fight and physically put their own lock on the tag"14:33
TheJuliacardoe: Are they a blocker and are you playing "DC Lemmings" ?14:34
TheJulia... It would not be hard to update pingus to swap blocks to servers....14:34
cardoeI need to read the spec cause this does sound like something interesting for me as well. Something that's currently managed outside of Ironic entirely.14:34
cidHuh, so, multiple locks, one tag.14:36
cardoeGlimmr_: pastebin / share whatever you can to expose the bug. I'm interested in inspection rules but not yet using them. I'm trying to come up with the tester and other validation stuff so that it doesn't feel like sticking your hand into a bag of razor blades with your eyes closed.14:36
TheJuliacid: yup, In one of my comments I put an example tag link :)14:36
TheJuliacid: and yes, its physical locks.14:37
TheJulia:)14:37
cidIn the real world, multiple locks on one door mostly spell trouble14:38
TheJuliayes, it sometimes can.14:39
cidHeh. that's new information to how I imagined it would work. So thanks.14:40
TheJuliaWe're in a world with no locks, just a badge reader and some sort of biometric device next to a door of sorts.14:40
TheJuliaWhich might scream "trouble" even more, depending on one's point of view14:41
cidTheJulia, do you imagine there's a "someone" who can remove the tag and suddently all locks are gone? A master key of sort!14:41
cidVia RBAC14:41
TheJuliaI don't know, typically its everyone must individuallly remove their locks14:42
TheJuliaThat is sort of like "These people added this tag for the wrong reasons" and without interfacing with the lock appliers, its sort of taking a grinder and cutting the tag off14:42
TheJuliaThe implications could be disasterous14:42
TheJuliaGranted, we're toggling power at BMC level, so one could always lockout/tagout the BMC and then once everything is down actually cut physical power overall14:43
TheJulia(but these are super rare things, having worked in DC ops its like the last resort nightmare option)14:44
TheJuliaThe kind of nightmare where sometimes additional staff called in would bring booze14:44
cid:D, because lots of work involed. 14:45
cidMakes sense actually. No overrides14:45
TheJuliaMore so, thermal properties and overall start survivability of some devices14:46
TheJuliabecause if they didn't restart/recover, it would become a very long day/night14:46
TheJuliaa concept which might also work is to allow owner-admin or system-admin to remove all locks as well, in that case they have to accept the responsibility14:49
TheJuliabut, I don't knwo if we want to make it that complex overall14:49
TheJulia(akin to a grinder being taken to the tag14:50
JayFI can't wait for the horror story from the data center tech who gets nicked by a fan from some power drunk owner admin clearing his lock 😥😥😥😥😥14:51
TheJuliaJayF: but wait, there is more!14:53
TheJuliathat bump on the fan blade damanged the balance, and eventually the fan explodes 33.915 hours later.14:53
TheJuliacausing reduced airflow and damaged circuits! Suddenly, the mobo catches fire and FLAMES are exiting the rear of the rack, oh noes!14:54
TheJulia(silly combustible cooling fluids)14:55
* TheJulia may have had too much coffee already14:56
dtantsurWe have bootc support nowadays, right? and it works automagically through the oci support? if so, are there any public images I could try?15:12
TheJuliaoci://quay.io/podman/machine-os:5.4 ?15:14
JayFIt's even better than you. Think: a bootc image specified via oci URL on a node with the auto detect deploy interface will deploy via bootc15:14
TheJulia(I just typed that from memory, so it is likely wrong)15:14
dtantsurJayF: ah, so it needs the autodetect interface? noted15:15
dtantsurTheJulia: isn't it a normal OCI image? or did they switch to bootc?15:16
JayFNo, we have a specific bootc interface as well15:16
JayFI'm just telling you it's hooked into even more cool magic15:16
dtantsurYep, cool. That does mean that I cannot just try it in metal3 :)15:16
TheJuliadtantsur: aiui, oci + able to be bootc'ed because the layering is present for a full container15:16
TheJuliawhich can be bootc'ed15:16
dtantsurI see, thanks15:17
TheJuliathey have artifacts *and* a bootc container layered under there15:17
* dtantsur is updating metal3 docs with recent additions15:17
JayFdtantsur: Auto detect deploy interface supports falling back to direct as fallback method15:17
dtantsurIndeed, but we'll need some massaging around API versions15:17
TheJuliaI dunno which would get chosen by default since they also have mastered disk images15:17
JayFdtantsur: The entire point of that interface is to allow you to use different types of deploys without having to switch your interface, so if you have a use case that's not covered, we should talk about it15:17
TheJuliaworth trying15:17
dtantsuror autodiscover what is available15:17
dtantsur(baremetal-operator is not tied to one Ironic version)15:17
* TheJulia takes the corgi for a walk15:18
JayF(I actually took a day off today and I'm going to jump off IRC now) o/15:18
dtantsurenjoy!15:18
cardoe"tools/vnc-container/bin/start-x11vnc.sh:33:1: E004 File did not end with a newline"15:23
cardoewut? I didn't touch that15:23
cardoeI also cannot get that to reproduce locally.15:28
cardoeDo we have a way in IPA to skip dhcp-all-interfaces? Specifically skipping https://opendev.org/openstack/diskimage-builder/src/commit/6b42cb23eef0ca921ca933f354238f83a45229d8/diskimage_builder/elements/dhcp-all-interfaces/install.d/dhcp-all-interfaces.sh#L17615:30
TheJuliacid: worth posting a patch if CI is kicking it on that error, I bet if you add -r to your tox command line it would list it15:38
cidTheJulia, are you referring to the pickle change?15:42
TheJuliawell, your saying it appears to have suddenly appeared15:44
TheJuliaso...15:44
TheJuliaThat is where I'm coming from15:44
cardoeokay. re-running with -r16:02
cardoeBut I wanted to get thoughts/feels on https://review.opendev.org/c/openstack/ironic/+/98142316:02
cardoeI've been having Nidhi work on inspection rules stuff internally with the goal of using it at some point after we upgrade to Ironic 3516:03
cardoeI want to have confidence in them before deploying them.16:04
cardoeSo what I've had her do is dump a node and inventory save and then setup a CI loop across those with the rules.16:04
cardoeSo that patch brings that into Zuul. I'd contribute the same node she's used but others can add nodes over time.16:05
cardoeLike Glimmr_'s issue above he could contribute that and we could have testing to ensure that the rules work consistently.16:05
cardoe  pep8: OK (203.95=setup[63.17]+cmd[140.78] seconds)  congratulations :) (204.41 seconds)16:06
cardoeSo nope... tox -r -e pep8 didn't reproduce locally.16:06
cardoehttps://zuul.opendev.org/t/openstack/build/c71e0fabb4314949b5107e2de44a913116:06
cardoeThe file ends with a 0x0a16:10
TheJuliainteresting16:24
FreemanBoss[m]Hi everyone. I'm Habeeb Babasulaiman (also FreemanBoss). I am currently an outreachy applicant looking forward to contribute to openstack - ironic on the project: Extend Ironic deployment history api. I'm looking forward to collaborating with and learning from everyone in the community. 16:38
FreemanBoss[m]rpittau: hroy:  looking forward to your guidance my mentors. Thank you 16:38
TheJuliacardoe: we'd likely have to build an overriding element if we wnat to change/influence the behavior with ipa17:01
denver_baHi everyone, I'm Denver Baraka, (Outreachy Applicant.)17:22
dtantsurdenver_ba: hi, please email the mentors, they're not online right now :)17:27
dtantsurSpeaking of which, folks, I'll be at KubeCon EU the entire next week. Expect spotty availability.17:28
denver_baokay17:28
TheJuliadtantsur: have fun!17:36
TheJuliahmm, another person I need to talk to is at kubecon next week. Wheeeee!18:00
lesliemHey guys, I'm Leslie Mwendwa. Happy to start contributing18:54
TheJuliaWelcome!19:18
TheJuliaerr19:18
* TheJulia sighs19:18
Pointbr8kerHi all — I'm David Nwosu, an Outreachy applicant for the Ironic project. I actually applied last year (project wasn't funded then), but I'm back and excited to see it funded this time. Working through the initial tasks now — looking forward to contributing!19:25
TheJuliaWelcome!19:27
OlamiposiHello Everyone, my name is Olamiposi and I'm an outreachy contributor. I hope to make meaningful changes that will help drive the project forward!19:50
TheJuliaWelcome! As a note, we're heading into the weekend, most contributors are away until monday :)19:55
OlamiposiOh okay no problem20:12
emmanuel801234Hi everyone, I’m Emmanuel, an Outreachy applicant interested in OpenStack Ironic. Happy to be here!21:19
kelvinasante[m]Hello guys, My name Kelvin Asante from Ghana. I am looking forward to contributing to the ironic project22:08
chinnisreeaddagallaHi everyone! I'm Chinni Sree, an Outreachy applicant for the May 2026 . I'm interested in the "Extend Ironic node deployment history API" project. I have experience with Python and I'm excited to start contributing! I have completed the initial article about Ironic. 23:08
opendevreviewDavid Nwosu proposed openstack/ironic master: Separate enrollment documentation by content type  https://review.opendev.org/c/openstack/ironic/+/97560023:18
opendevreviewcid proposed openstack/ironic stable/2025.1: Make RPCService picklable for oslo.service  https://review.opendev.org/c/openstack/ironic/+/97726123:26
*** emmanuel801234 is now known as e3plexdev23:31
*** e3plexdev is now known as _3plexdev23:31

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