Thursday, 2026-03-26

chinnisreeaddagallaHi everyone, I’m trying to install Bifrost on an Ubuntu 22.04 ARM64 VM (running on Apple Silicon via UTM).00:34
chinnisreeaddagallaI was able to complete the setup and run the Ansible playbook, but I’m getting an error related to grub-efi-amd64-signed not being available.00:34
chinnisreeaddagallaFrom my understanding, this might be due to an architecture mismatch (ARM64 vs AMD64) but I wanted to confirm if Bifrost is expected to work on ARM systems or if there’s a recommended workaround.00:34
chinnisreeaddagallaAny guidance would be really helpful. Thank you!00:34
opendevreviewLennart Jern proposed openstack/sushy master: Prevent double-wrapping timeout tuple in Connector _op  https://review.opendev.org/c/openstack/sushy/+/98221910:09
opendevreviewLennart Jern proposed openstack/sushy master: Prevent double-wrapping timeout tuple in Connector _op  https://review.opendev.org/c/openstack/sushy/+/98221911:29
opendevreviewLennart Jern proposed openstack/sushy master: Prevent double-wrapping timeout tuple in Connector _op  https://review.opendev.org/c/openstack/sushy/+/98221911:35
opendevreviewMahnoor Asghar proposed openstack/ironic master: Soft power off before ejecting virtual media regardless of CONF.inspector.power_off  https://review.opendev.org/c/openstack/ironic/+/98194212:00
stephenfinJayF: RE: your question on https://review.opendev.org/c/openstack/python-ironicclient/+/981686/4/ironicclient/osc/v1/baremetal_shard.py#40, here's how I did that for OSC12:05
stephenfinhttps://review.opendev.org/c/openstack/python-openstackclient/+/97068112:06
stephenfinI suspect doing the same in ironicclient would make sense12:06
stephenfinAlso, as an aside, we'd be totally open to you merging the ironicclient OSC plugin into OSC proper, if it was an advantage. We're already planning on doing that for manila this cycle https://review.opendev.org/q/topic:%22integrate-manilaclient%22+is:open12:08
stephenfin...and neutron are already in the middle of merging their stadium project cients (TaaS, VPNaaS, etc.) into OSC12:09
JayFstephenfin: The reason we operate our plug-in as a separate entity is that it is separately installable to create a "baremetal" (no openstack) cli for our standalone users13:00
JayFThanks for the help with the shape of the types though. I knew you'd be the expert 13:01
stephenfinOh, you use the osc package for the `baremetal` client? Interesting. Most other clients with OSC plugins have a separate implementation for the "legacy" clients13:25
stephenfin(scare quotes because I realise ironic is different due to its standalone use-cases)13:26
TheJuliagood morning13:29
* TheJulia stumbles in like a complete and total zombie looking for... coffeee.13:30
JayFstephenfin: It's not the legacy client. It literally implements the exact same commands as the openstack client does for ironic, just without the openstack prefix.13:32
JayFstephenfin: and while it is annoying and irrational, a lot of standalone ironic customers get really testy if they start seeing the word openstack in places13:32
stephenfinsorry, yes, that was my point: it's not actully legacy in ironic's case13:32
JayFI was just making sure you didn't think we were keeping the ironic command alive 😂13:32
stephenfinnope, I'm aware. Ditto for Glance and Cinder, fwiw13:33
JayFI might have finally purged the last of that syntax out of my brain. I can't recall any commands anymore 😂13:33
TheJuliaJayF: syntax purged and replaced via single-process thread13:33
iurygregorygood morning ironic13:48
dkingAny BMO folks around today?14:22
opendevreviewTakashi Kajinami proposed openstack/ironic-tempest-plugin master: Add stable/2026.1 job  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/98224314:33
JayFanandkaranubc: make sure you review stephen fin's answers starting at about 5:05a PST today ^^^15:00
opendevreviewMerged openstack/sushy master: Prevent double-wrapping timeout tuple in Connector _op  https://review.opendev.org/c/openstack/sushy/+/98221915:17
opendevreviewJay Faulkner proposed openstack/ironic master: Remove the SNMP hardware type and power interface  https://review.opendev.org/c/openstack/ironic/+/98214615:17
opendevreviewJay Faulkner proposed openstack/ironic master: Remove pysnmp and related dependencies  https://review.opendev.org/c/openstack/ironic/+/98214715:17
JayFiRMC change (not re-pushed here) is marked prio and ready to merge/review15:17
JayFthis should be fixed but we'll see how devstack feels about that :D15:17
opendevreviewDoug Goldstein proposed openstack/ironic master: make target_datetime optional for set_bmc_clock step  https://review.opendev.org/c/openstack/ironic/+/98226115:21
JayFover -15k lines removal in those deprecations15:22
* JayF pushing for 0 net LOC over OpenStack career :D 15:22
JayFAlso; I'll note: used download-logs.sh + claude-code to troubleshoot SNMP CI. It's so ridiculously good at finding the issue. I had to keep it from writing a bad, naive fix, but I'm happy to do that since I didn't have to sort through those logs by hand15:23
TheJuliaSo, question, were we going to rip out ilo this cycle?16:19
TheJuliaI feel like I mentally lost track of that one16:20
JayFI'm not sure16:20
JayFI am OK to do it16:20
opendevreviewAbhishek Bongale proposed openstack/ironic-tempest-plugin master: Add conditional graphical console validation  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/98207716:42
opendevreviewAbhishek Bongale proposed openstack/ironic master: Limit interfaces to fake-graphical for testing  https://review.opendev.org/c/openstack/ironic/+/98227016:42
opendevreviewAbhishek Bongale proposed openstack/ironic master: Limit interfaces to fake-graphical for testing  https://review.opendev.org/c/openstack/ironic/+/98227016:50
cardoeWould https://review.opendev.org/c/openstack/ironic/+/982261 be okay to backport?17:08
JayFIt's a hardware compatibility fix, so I would default to yes17:09
opendevreviewcid proposed openstack/ironic-specs master: A specification for a node power lock feature  https://review.opendev.org/c/openstack/ironic-specs/+/97489418:01
JayFTheJulia: re: iLO: in 2024.1 we had a release note indicating "ilo hardware types may be deprecated in the future". In 2026.1 (backported to 2025.2), we added an upgrade check to warn of ilo driver deprecation.18:16
JayFTheJulia: so from my PoV, we have a warning of deprecation in the latest slurp, so I think we are justified in removing it this cycle --- 2025.2->2026.2 is 2 releases, spanning one slurp18:17
JayFI will email the list and ask for people to scream if they disagree18:17
TheJuliak, Thanks. I saw we didn't explictly change the supported flag in the driver, but yeah, we've been messaging it for a while19:01
cardoeSoooo runbooks20:03
cardoeWorking with https://review.opendev.org/c/openstack/ironic/+/98226120:03
cardoehttps://www.irccloud.com/pastebin/oafqmO1X/20:03
cardoeBut to let my operators use it. I've gotta call the runbook CUSTOM_RESET_BMC_CLOCK for example and add the trait CUSTOM_RESET_BMC_CLOCK.20:04
cardoeThen with automated runbook cleaning does that mean it's gonna be run every single time?20:05
cardoeSo stupid idea.... extend runbooks to have a traits column which is a set and for the migration we add the name as only element in the set. Then maybe add a column for automated_cleaning? Cause we've said before runbook based deployment could be a think too.20:09
JayFyes and very very oh god no that's not how it works20:09
JayFI think you don't grok the shape of automated cleaning via runbook20:09
cardoeI don't.20:09
JayFhttps://static.opendev.org/docs/ironic/2025.2/admin/cleaning.html#configuring-automated-cleaning-with-runbooks20:10
JayFhttps://static.opendev.org/docs/ironic/2025.2/admin/cleaning.html#cleaning-steps is where it all starts20:10
cardoePart of me wants to run the "reset_idrac" step but its very unclear what that actually does to the iDRAC... like am I gonna lose IP access?20:13
JayFdtantsur: TheJulia ^^ this is why I didn't want that step merged20:14
JayFcardoe: do not run it if you do not know the implications20:14
JayFcardoe: it's a factory reset and is breaky in some situations/environments20:14
cardoeWell it'd be helpful if we said what that did.20:14
cardoeThere's also a "known_good_state" step which sounds warm and fuzzy but I checked and it internally calls the scary "reset_idrac"20:14
cardoeSo that feels like a big foot gun just sitting there.20:15
JayFthat's why I was against merging it initially, but RH had customers with specific use cases20:15
cardoeI mean it's fine to be in there but put some comments in the docs as to what its gonna do. And if its gonna lock me out put a warning.20:16
cardoeWe've got a warning on the BIOS settings reset but not a warning on that.20:16
JayFwe should perhaps add one then? 20:16
JayFI don't go looking at the menu of our steps that often; especially out of band steps20:16
cardoeYep. And I'm gonna ask to backport that.20:16
* TheJulia reads and keeps reading becasue the discussion is going at full speed20:17
JayFTheJulia: tl;dr cardoe went "what does the giant shiny red button do" w/r/t that reset_idrac step :D 20:17
* JayF dives over to stop him from mashing the button20:17
cardoeI've got a person that's adding hardware in and coming to me every time she cannot do what she needs to do with Ironic. She doesn't have "admin" role or "system scope" btw.20:18
TheJuliaYeah, I don't remember what it does at the "RESET IT" mode, the softer mode afaik is just a "hey, restart with last known good config and refresh thyself"20:18
TheJuliailo has some scarier knobs. Wait until we have control over firmware loading/control knobs!20:19
cardoeWell "known_good_state" step just calls "clear_job_queue" and "reset_idrac". And the docs for "known_good_state" just says "reset iDRAC to known good state".20:19
cardoeWhile "reset_idrac" says "reset the iDRAC"20:19
TheJuliareset might just be "reboot"20:19
TheJuliabecause, I remember the idrac folks were having to call that a LOT with wsman20:20
cardoeWe've got a vendor command to reboot the iDRAC20:20
* TheJulia shrugs and goes "its an idrac"20:20
cardoeBut this could be a case where we have "update_firmware" in the management interface and "firmware_update" in the firmware interface.20:20
TheJuliaahh, different modes!20:21
cardoeAnyway I still think my idea of changing runbooks to have the traits as a set and not having the name be the match-y thing is good.20:21
TheJuliafor automated cleaning, maybe?20:22
JayFcardoe: Do you think you can run "N" runbooks as part of automated cleaning? Because you can't, and I think I would be -1 to that as a feature as it eliminates the value of the declarative cleaning: simplicity/easy to understand20:22
cardoeNo.20:22
JayFI am really, really confused as to what the headache is?20:22
JayFyou just want runbooks to map to N traits instead of having to add a trait to the nodes?20:22
cardoeI don't wanna put 7000 traits on every node?20:22
JayFoh, ohhhhhhhhhh20:23
JayFname = trait20:23
JayFso N runbooks = N traits20:23
JayFno way around it20:23
TheJuliaI'm super confused20:23
cardoeCUSTOM_RESET_JOBS, CUSTOM_RESET_BMC_CLOCK, CUSTOM_RESET_DELL_RAID, CUSTOM_DELL_VENDOR_ACTION_X20:23
JayFTheJulia: right now, runbook name == a trait name (e.g. CUSTOM_BLAH_BLAH)20:23
TheJuliaComputer, activate the Emergency Software Engineer!20:23
cardoeI just wanna put CUSTOM_IDRAC on those boxes20:23
JayFso if you want multiple runbooks to be valid for a node, you have to add the names of those runbooks to node traits20:23
cardoeYes.20:23
JayFwhich has an ACTUAL PERFORMANCE IMPACT in scheduling20:23
JayFf*20:23
cardoeYes20:23
TheJulia"Please state your user story"20:24
cardoe^^^^20:24
cardoeperformance!20:24
JayF"I don't want to transmit over 9000 traits everytime nova syncs up"20:24
cardoeI'm watching nova and placement lose their minds20:24
JayFcardoe: +1 to the idea generally, we'd need to spec it20:24
cardoeyes20:24
JayFcardoe: if you wanna add it to PTG, cid might have opinions too since he wrote it originally20:24
TheJulia++20:24
JayFjust add a column: traits: list(traits), migration sets trait[0]==name, future only enforces that it has a properly formatted trait, and match on that, not name20:25
opendevreviewJulia Kreger proposed openstack/sushy master: WIP: Add TLS configuration support to sushy  https://review.opendev.org/c/openstack/sushy/+/98230920:31
cardoeNow make managing my certificate via ironic work nicely.20:32
TheJuliaplease elaborate on this user story request20:34
opendevreviewJulia Kreger proposed openstack/ironic master: Add global TLS configuration for API service  https://review.opendev.org/c/openstack/ironic/+/98231221:04
opendevreviewJulia Kreger proposed openstack/ironic master: Add TLS configuration for agent communications  https://review.opendev.org/c/openstack/ironic/+/98231321:04
opendevreviewJulia Kreger proposed openstack/ironic master: WIP: Add TLS configuration support to Redfish driver  https://review.opendev.org/c/openstack/ironic/+/98231421:04
TheJuliaA lot of that is more than anything, discussion pointes to circle disucssions around21:10
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: arista: Added ERROR_MSG_PATTERNS  https://review.opendev.org/c/openstack/networking-generic-switch/+/98233922:11
opendevreviewHarald Jensås proposed openstack/networking-baremetal master: Optimize L2VNI trunk manager with caching and DRY  https://review.opendev.org/c/openstack/networking-baremetal/+/98165022:33
opendevreviewHarald Jensås proposed openstack/networking-baremetal master: Remove redundant IDL table existence checks  https://review.opendev.org/c/openstack/networking-baremetal/+/98234222:57

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