Friday, 2026-06-12

opendevreviewSteve Baker proposed openstack/ironic master: Register oslo.service opts in prepare_command for spawn workers  https://review.opendev.org/c/openstack/ironic/+/99306200:20
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add RestconfSwitch base class for HTTP transport  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288707:24
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add RestconfOpenConfigSwitch driver  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288807:24
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add RESTCONF documentation  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288907:24
opendevreviewPierre Riteau proposed openstack/tenks master: Switch to 2026.1 upper constraints temporarily  https://review.opendev.org/c/openstack/tenks/+/99308208:04
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Rename netconf_models to yang_models  https://review.opendev.org/c/openstack/networking-generic-switch/+/99309009:06
dtantsurJayF: s/metal3/standalone/ please. You make it sound like we're developing metal3-exclusive features, which is not the case.10:37
dtantsurJayF: someone needs to check if non-neutron networking can be used with neutron DHCP plugin. Fortunately, we never got to deprecating DHCP plugins :)10:37
dtantsurLet's see if Claude can be this "someone"10:39
dtantsurJayF: Claude thinks you're out of luck: https://paste.opendev.org/show/byDtqdtE2bMNZxcp25As/ (I have *not* verified any of the claims here)10:47
dtantsurI'm curious why you wouldn't use n-g-s as an ML2 plugin if you have Neutron anyway though.10:47
opendevreviewMithun Krishnan Umesan proposed openstack/networking-baremetal master: Upgrade OVN SSL connections to TLS 1.3 with hybrid PQC key exchange  https://review.opendev.org/c/openstack/networking-baremetal/+/99249511:53
opendevreviewVerification of a change to openstack/ironic unmaintained/2023.1 failed: security: Use sandbox rendering for jinja2  https://review.opendev.org/c/openstack/ironic/+/98777811:54
opendevreviewPierre Riteau proposed openstack/tenks master: Switch to 2026.1 upper constraints temporarily  https://review.opendev.org/c/openstack/tenks/+/99308212:18
*** dking is now known as Guest1123112:20
*** Guest11231 is now known as dking12:21
dkingdtantsur: Would you happen to be in this morning?12:26
dtantsurdking: hi! sorry, was having lunch.12:52
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.2: ci: Pin setuptools to a range that still ships  https://review.opendev.org/c/openstack/ironic-python-agent/+/99310712:55
dkingdtantsur: No worries. Thank you for responding. I never did get a response in slack, and I was wondering whether I could get some help regarding errors regarding the "baremetal-operator-controller-manager-metrics-"  service. 13:04
dtantsurdking: yeah, a lot of Ericsson folks are absent, so the slack is a bit quiet13:04
dkingdtantsur: After we upgraded our BMO a while ago, we started getting errors for the metrics service, and when I looked it it, it seems it was due to kube-rbac-proxy and the way the certificates are handled. It looks like I would need to know how to get the cert file that the manager is using.13:10
dtantsurdking: from what to what version?13:16
dkingThe old version was quite old. Currently, we're doing BMO v0.12.0 and kube-rbac-proxy at v0.15.0.13:20
TheJuliadtantsur: I think he might be pondering a world without neutron13:23
dtantsurTheJulia: then how is it different from Metal3 case?13:23
TheJuliaOutside of the ecochamber, neutron folks seem to be blissfully unaware of neutron network modeling perceptions and how that is driving the way folks are looking at it13:24
dtantsurechochambers--13:24
TheJuliadtantsur: they wouldn't be using metal3 at all, its pure standalone with whatever wrapper they determine they need for their use case13:24
TheJuliaat least, that is the way I'm reading the discussion now13:25
dtantsurTheJulia: sure, sure, but JayF is claiming the current implementation is done with Metal3 in mind, and it's.. not?13:25
dtantsurIf the message is "we need a standalone IPAM", I'm all for it :)13:25
TheJuliaI'd argue it might not be our place, most shops have their own IPAMs already13:25
TheJuliathe big challenge neutron had prior was that it insisted on being the IPAM as well13:26
TheJuliaand many operators were like "I already have processes, tools, and procedures13:26
TheJulia"13:26
dtantsurTrue. But if you have IPAM, all you need is a glue to populate network_data in two places, right?13:26
dtantsur(which is exactly the same problem we have in Metal3 btw)13:26
TheJuliaor one place through ironic13:27
TheJuliaspecifically record recording for data generation13:27
TheJuliarealistically, the risk of jumping to modeling conclusions is where we're at and Jay is still trying to get his bearings and perception. We don't know his constraints/requirements either13:28
TheJulia(I guess I'm saying it might be a better dialog to have when Jay is awake/alive/caffinated)13:29
* TheJulia begins the sacred task of caffination13:30
TheJuliaI wonder if https://www.teepublic.com/hoodie/2624841-i-am-one-with-the-coffee-and-the-coffee-is-with-me can be on a t-shirt....13:32
dtantsur++ would be great13:32
dtantsurdking: https://github.com/metal3-io/baremetal-operator/pull/2102. Kill kube-rbac-proxy with fire, it seems.13:39
dkingdtantsur: Well, that would do it. I suppose that we need to update and make sure that we have the right CRDs. Thank you very much.13:51
JayFdtantsur: It's clearly built for a DHCP-first environment OR an environment with a coordinating higher level tool -- our interfaces are structured in a way where it's nearly impossible for a instance-deployer to setup their own static IPs without intimate knowledge of the node's networking 13:56
JayFdtantsur: I abbreviated that to "built for metal3"13:56
TheJuliamore like dhcp-less && coordinated at a higher level13:57
dtantsurJayF: I'm just pointing out that Ironic standalone is entirely like that. We've never had a solid IPAM story, with or without switch management.13:57
JayFand based on your observations (Which match what I would expect given my rapid-digging yesterday) it doesn't even come with the DHCP server :)13:57
JayFdtantsur: I'm not wanting Ironic to IPAM.13:58
JayFdtantsur: I want to feed ironic an IP/netmask/dns server in the same port.extra as the switchport, and then Ironic injecting that into the network_data13:58
TheJuliayou want to simplify the carrying of data down to something like a vif then ?13:58
JayFthis doesn't make Ironic the IPAM, it turns "tenant" IPs into something that -- if you use that capability -- are provisioned at the same time the port is13:58
TheJuliaso the ipam/inventory management has and maintains it ?13:59
JayFso later deployments don't need network details13:59
dtantsurUnderstood. I think what you're talking about is yet another thing we skipped by going down the port.extra path.13:59
JayFIt would 1000% be outta scope for Ironic to care about what the IP address field (for instance) has, other than making sure it's an IP13:59
TheJuliaat a cursory level, its not a bad idea13:59
JayFdtantsur: yeah none of this chat is "we built a bad thing" or even "we built half a thing", if anything it's more like "we build enough good stuff that now my folks are interested and asking me to find the sharp edges for our use case" :D 14:00
* dtantsur nods14:01
dtantsurIt's the same for us. While metal3 has an IPAM, it's bolted on CAPI API and is barely usable without it.14:01
dtantsurAnd it does not integrate with node.network_data for inspection/provisioning14:01
dtantsurMidcycle topic?14:01
JayFMany places I've worked have had kinda a hub/spoke model for clouds. One big central cloud, a bunch of smaller satellite sites for various use cases14:02
JayFCDN, networking geography, etc14:02
dtantsurMy place too :)14:02
JayFI think Ironic+Ironic Networking is about 5 feet from becoming the best tool for that use case :D 14:02
JayF(for the smaller, satellite sites)14:03
JayFand yes, americans use imperial measurements for story points, too /s 14:03
dtantsurWe need to up the game and use different measurements themselves instead of story points!14:05
dtantsurlike, instead of S/M/L, you get inch, foot, yard, mile, whatever14:05
JayFso if something's really small, it can be a task, then we'll move up to story, epic, project, program, company, nation-state, civilization, planet, universe14:07
JayFlol14:07
dtantsurROFL14:07
TheJuliaso where does the retirement catameran sit in that list?14:12
TheJuliais that a program?!?14:12
JayFlisten, that's a ServiceNOW term14:13
JayFwe only use JIRA in this house14:13
JayF /s14:13
JayFeveryone knows ServiceNOW goes from bicycle->transgalactic generational spacecraft (transportation devices by size)14:13
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add NetconfOpenConfigSwitch driver  https://review.opendev.org/c/openstack/networking-generic-switch/+/99006114:21
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add NETCONF OpenConfig driver documentation  https://review.opendev.org/c/openstack/networking-generic-switch/+/99006214:21
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add trunk subport for  NETCONF OpenConfig driver  https://review.opendev.org/c/openstack/networking-generic-switch/+/99145814:21
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Netconf: Document Neutron trunk port support  https://review.opendev.org/c/openstack/networking-generic-switch/+/99145914:21
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Refactor: extract OpenConfigModelMixin  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288414:22
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add to_restconf_dict() methods to OpenConfig model  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288514:22
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: restconf: add path helpers and resource_path util  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288614:22
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add RestconfSwitch base class for HTTP transport  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288714:22
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add RestconfOpenConfigSwitch driver  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288814:22
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Add RESTCONF documentation  https://review.opendev.org/c/openstack/networking-generic-switch/+/99288914:22
opendevreviewHarald Jensås proposed openstack/networking-generic-switch master: Rename netconf_models to yang_models  https://review.opendev.org/c/openstack/networking-generic-switch/+/99309014:22
clifJayF: https://review.opendev.org/c/openstack/ironic-python-agent/+/993107 does this look right?14:28
clifIt passes, but the test that failed the backport is not represented in the tests run on that change14:28
JayFoooh14:28
JayFTake your backport, add a trailer: "Depends-on: https://[snip]/993107"14:28
JayFand it'll stack em14:29
hjensasWork should be measured in volume, fluid ounce, gill, *pint*, quart, gallon :)14:29
JayFoh, nevermind, that's wrong14:29
JayFit won't work in the same repo14:29
JayFyou'll have to actually stack them (git review -d [ci fix], git review -x [stable fix], git review)14:29
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.2: ci: Pin setuptools to a range that still ships  https://review.opendev.org/c/openstack/ironic-python-agent/+/99310714:32
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.2: Add a flag to disable installing bootloaders  https://review.opendev.org/c/openstack/ironic-python-agent/+/99302014:32
clifso I'll have to stack each backport on top of this change14:32
JayFwell, if it works14:33
clifyea14:33
JayFwe can just push through the CI change first14:33
JayFthen recheck your stable changes14:33
JayFI only ever really stack them to validate it's the fix needed14:33
clifthat works14:33
JayFgiven you are just testing for the docs job, if you don't wanna wait 2 hours for integration tests, go zuul.opendev.org -> openstack [status] -> put the change # 993020 in the box and hit enter14:36
JayFyou can see tests run and when you see docs go green, you can proliferate the fixes down14:36
opendevreviewHimanshu Roy proposed openstack/ironic master: Add releasenote for disallow-steps feature  https://review.opendev.org/c/openstack/ironic/+/99313114:46
opendevreviewHimanshu Roy proposed openstack/ironic master: Add releasenote for disallow-steps feature  https://review.opendev.org/c/openstack/ironic/+/99313114:47
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.1: Add a flag to disable installing bootloaders  https://review.opendev.org/c/openstack/ironic-python-agent/+/99302415:01
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.1: ci: Pin setuptools to a range that still ships  https://review.opendev.org/c/openstack/ironic-python-agent/+/99313615:01
opendevreviewWill Szumski proposed openstack/tenks master: CI: Make aarch64 jobs experimental  https://review.opendev.org/c/openstack/tenks/+/99313815:07
opendevreviewWill Szumski proposed openstack/tenks master: CI: Make aarch64 jobs experimental  https://review.opendev.org/c/openstack/tenks/+/99313815:13
clifI must've missed something because this failed with the same issue https://zuul.opendev.org/t/openstack/build/4c35b76d54fb4c6386ca0fadd674af1815:21
clifit looks like the setuptools it grabbed was 82.0.0 so it falls in line with the range set15:23
dtantsurFailed to send baremetal.port.create.start notification for port f64d726b-9e9e-4a2a-844b-34062a15b2e5 with level info, notification method PortCRUDNotification, payload method PortCRUDPayload, error Object port doesn't have the field "available_for_dynamic_portgroup" required for populating notification schema key "available_for_dynamic_portgroup"15:28
dtantsurNoticed ^^ in metal3 logs, anyone has a clue?15:28
clifthat's a new field we added in relation to trait based networking15:36
clifdid migrations run?15:39
clifiirc the change to add it followed the exact same structure as adding the new vendor and category fields to port{group}s15:40
TheJuliaIt maybe that code expects the field on the notification…. That seems like a bug15:44
clifcould this be related to release_mapping shenanigans?15:44
TheJuliaMore likely, different interfaces somehow playing into the flow resulting in that15:45
TheJuliaBut, interesting notifications are on apparently?!15:45
clif33.0 doesn't have the latest port version listed, which is what includes 'available_for_dynamic_portgroup' in port15:45
TheJuliaDmitry is likely running 37.015:46
clifoh for some reason I was looking at an old version of release_mappings15:50
clifnot master15:50
dtantsuryeah, I'm very close to master16:00
cardoeso what's ironic?16:05
cardoein other words, I'm finally at my desk16:06
opendevreviewMerged openstack/tenks master: CI: Make aarch64 jobs experimental  https://review.opendev.org/c/openstack/tenks/+/99313816:07
opendevreviewPierre Riteau proposed openstack/tenks master: Switch to 2026.1 upper constraints temporarily  https://review.opendev.org/c/openstack/tenks/+/99308216:14
opendevreviewMerged openstack/ironic-python-agent stable/2025.2: ci: Pin setuptools to a range that still ships  https://review.opendev.org/c/openstack/ironic-python-agent/+/99310716:21
TheJuliacardoe: welcome back!16:22
TheJuliacardoe: we've assigned all work to you, congrats!16:22
TheJulia</joking!>16:22
cardoe<insert I'm in danger meme>16:36
TheJulialol16:40
TheJuliaso, I'd really love to discuss nvmeof, if that doesn't make you want to pack up and run for the hills16:45
cardoeNot for installation like the current implementation is for I assume16:47
JayFIt kinda does :). But mainly from a "we gotta be careful to not create security vulns while resolving them" standpoint16:47
* dtantsur tries to switch from Go to Python16:49
dtantsurc'mon brain, you can do it16:49
* TheJulia offers dtantsur chocolate chip cookies16:51
dtantsurcoooookiiies!16:51
TheJuliacardoe: Kind of what JayF said, I guess I've got a number of challenges I've sort of drifted into in my mind and I would <3 a slightly wider discussion with folks doing simlar or interested in similar to see what thought are. For example, it looks like HPE gear entirely lacks the ability to set credentials for NVMeoF/TCP.... *facepalm*16:52
TheJuliaWhere as dell, has undocumented and confusing fields16:53
TheJuliaAnd I get it, its sort of emerging case stuff16:53
* TheJulia is splunking through HPE BMCs at the moment17:22
* TheJulia thinks we scared cardoe away17:36
dtantsurIt's been an exhausting week, see you on Monday o/17:50
TheJuliahave a good weekend!17:53
opendevreviewMerged openstack/ironic stable/2026.1: fix: skip storage controllers without Volumes link  https://review.opendev.org/c/openstack/ironic/+/99011618:14
clifJayF: I think we need to patch ironic-python-agent-builder too to pin back its setuptools?18:15
clifhttps://zuul.opendev.org/t/openstack/build/882ec0fb6a8444328acb31d6a755e6c1/log/job-output.txt#25182 here you can see it downloading setuptools-82.0.1 which is beyond what is pinned in ipa tox.ini18:19
clifand it errors out in setuptools with ModuleNotFoundError: No module named 'pkg_resources' again18:19
TheJuliaugh18:20
clifthe joyous work continues18:23
TheJuliawe need something like "ad astra per aspera" as our motto ;)18:25
opendevreviewClif Houck proposed openstack/ironic-python-agent-builder stable/2025.2: ci: Pin setuptools to a range that still ships  https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/99315818:26
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.1: Add a flag to disable installing bootloaders  https://review.opendev.org/c/openstack/ironic-python-agent/+/99302418:27
cliferg that's wrong18:27
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.1: Add a flag to disable installing bootloaders  https://review.opendev.org/c/openstack/ironic-python-agent/+/99302418:27
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.2: Add a flag to disable installing bootloaders  https://review.opendev.org/c/openstack/ironic-python-agent/+/99302018:28
opendevreviewJulia Kreger proposed openstack/ironic-specs master: Crazy idea: RCOE Enabled BMaaS  https://review.opendev.org/c/openstack/ironic-specs/+/99041318:30
JayFclif: keep going down the rabbithole, I assure you it will eventually end and you can climb back up the chain of fixes :| 18:37
clifare there other repos I should be aware of that may need their setuptools pinned back?18:37
opendevreviewMerged openstack/tenks master: Switch to 2026.1 upper constraints temporarily  https://review.opendev.org/c/openstack/tenks/+/99308218:38
clifdo y'all know how build-tinyipa.sh gets its requirements.txt or how to pin back what it downloads?19:03
clifit looks like I'd have to pin back setuptools inside ipa-builder's requirements.txt in order to have that take effect for build-tinyipa.sh19:05
clifbut that doesn't follow the shape of the change for ironic and IPA, is that OK?19:05
clifor maybe I'd have to do it inside IPA's requirements.txt19:06
clifis that kosher?19:08
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.2: Add a flag to disable installing bootloaders  https://review.opendev.org/c/openstack/ironic-python-agent/+/99302019:12
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.2: Pin setuptools inside requirements.txt  https://review.opendev.org/c/openstack/ironic-python-agent/+/99316419:12
JayFclif: If we were going to pin in requirements.txt, it's better to do it in ipa-builder IMO19:20
clifhow?19:20
clifmodify the copy of IPA's requirements.txt it makes?19:21
JayFooooh19:21
JayFI see what you're saying19:21
JayFIPA-builder is "installable" as a python application as well19:21
JayFso I was looking in the wrong spot19:22
JayFclif: so 2025.2, is it tinyipa only or tinyipa+dib builds?19:22
clifnot sure, I'm just running down the error I'm currently seeing in CI19:23
JayFOK this appears to be in build-tinyipa19:24
cardoeTheJulia: so NVMe?19:24
JayFhttps://opendev.org/openstack/ironic-python-agent-builder/src/branch/stable/2025.2/tinyipa/build-tinyipa.sh#L14519:25
JayFwe are already munging the requirements.txt there19:25
JayFI'd be tempted to make that add a setuptools pin19:25
TheJuliaheh, so my brain is so on nvme that I thought I read that line as starting at nvmexpress.org and ending with build-tinyipa19:26
clifcopying == munging?19:26
TheJuliainquiring minds, why are we still building tinyipa on 2025.2? Didn't we kill it by then?!19:26
JayFwell, tbh, I misread the LN:147 code as being modifications to that library19:27
JayFTheJulia: I haven't asked that question, I'm just reading logs and troubleshooting while eating lunch19:27
TheJuliaI was just nomming celery because apparently I need to not eat or eat like a rabbit only and exercise more than I already do :(19:28
* TheJulia rages at doctors ignoring issues19:28
* TheJulia regains composure19:28
JayFclif: I think that's still a good place to do it even though we aren't modifying it directly there, but TheJulia's implied question of "can we just kill tinyipa based jobs on 2025.2" is a good one19:29
JayFthe problem with that is that if we published tinyipa for 2025.219:29
JayFdon't we owe people an updated ramdisk?19:29
* TheJulia is all for declaring it as tinyipa's ides of march19:29
JayFeven if we have been screaming to not use it outside of CI for a decade19:29
* TheJulia wonders if weveryone has their Pugio's ready!19:30
TheJuliaheh19:30
TheJuliacardoe: yeah, so I'm trying to rationalize into what would be best to exist upstream for NVMeoF/TCP support19:34
TheJuliapart of what I'm also stuggling to rationalize is a model where everything makes sense and is also cross-vendor19:36
TheJuliabut... maybe that means I just need to push the DMTF harder19:36
JayFI think we have plenty of evidence now that implementing features on half-ass-implementations of Redfish interfaces just lead to Ironic getting blamed when things go wrong...19:37
JayFThat leads me to a path of instead of working really hard to make something that barely works work, maybe convince the DMTF to do something about the half-ass implementations first19:37
TheJuliaI honestly think I'm kind of okay with dell's model but getting it to a better place across vendors is the needful19:38
TheJuliaWell my challenge is customers wanting to get on a track now so that train can arrive in say, 18 months19:38
TheJuliabecause I think they grok just how long that takes19:38
JayFI mean, I can understand the pressures of that, but they need to get the vendors+DMTF on board before us :/ 19:39
JayFand/or pad that number if it's now your job lol19:39
TheJuliawell, where the DMTF least left it as an an oem oriented bios setting, only 2 vendors even do that, hpe being even more weirdly so19:39
TheJuliaAnd I think that was sort of their base mistake19:40
TheJuliabecause the vendors didn't really take full initiative19:40
TheJuliaAlso, emerging technology19:40
TheJuliaadding authentication requriements when "storage" is just a "storage network and it works"19:40
TheJuliais dramatic shifts too19:40
TheJuliabut yeah, table stakes and if its now my job...19:41
TheJuliadunno19:41
opendevreviewClif Houck proposed openstack/ironic-python-agent-builder stable/2025.2: Pin setuptools in the requirements.txt copied from IPA  https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/99317619:41
opendevreviewClif Houck proposed openstack/ironic-python-agent stable/2025.2: Add a flag to disable installing bootloaders  https://review.opendev.org/c/openstack/ironic-python-agent/+/99302019:43
cardoeTheJulia: meetpad?19:45
cardoeAnd then we can summarize?19:45
TheJuliasure, fwiw, I've been noodling a spec on the topic19:45
* TheJulia sends claude on a mission which may take a while19:46
TheJuliahttps://meetpad.opendev.org/ironic-nvme19:47
JayFTheJulia: I've just gotten a pretty strong signal from users, my downstream and others, that they have been trained to avoid advanced features that interact with redfish because you cannot trust they will work with new hardware19:50
JayFthat's not exactly "our fault", but we are the messengers of that bad news everytime, and we're often also the folks who said "look at the cool thing we can do"19:51
JayFIDK how to manage that, but I think in the past we just haven't at all, and IDK how much longer that'll be OK19:51
JayFclif: TheJulia: dtantsur: RFR https://review.opendev.org/c/openstack/security-doc/+/993182 --- after review, I intend to announce this on Monday.20:46
TheJuliaYeah, I'm not super thrilled with one of the vendors right now20:46
TheJuliaregarding their redfish20:46
JayF^ do not review is wrong20:48
JayFthis belongs in a different OSSA, I have no idea why my notes said to revise this one20:48
JayFclif: TheJulia: dtantsur: attempt #2: [OSSA-2026-017] Errata 1: fix parsing edge cases  https://review.opendev.org/c/openstack/ossa/+/993185 actually errata'ing the correct change /o\20:59
JayFhttps://review.opendev.org/c/openstack/ironic/+/986418 could use a +2a21:21
TheJuliaso, cardoe has convinced me that maybe a first pass on anti-redfish is the way21:22
TheJuliabut I still have a reminder for DMTF discussion21:22
TheJulia:)21:22
cardoeyeah absolutely think we'll need some DMTF follow on here21:22
cardoeBut we came to the conclusion that first pass might be the secondary volume attachment flowing smoothly and storing the data because that'll unlock the primitives for the redfish way.21:23
cardoeJayF: I gave it a +221:23
TheJuliaand fwiw, I have made them aware that this is a focus area, so we shall see21:23
JayFhttps://review.opendev.org/c/openstack/ironic/+/991384 and the one under it needs approval too21:24
JayFhttps://review.opendev.org/c/openstack/ironic/+/991385 (the one under it)21:24
JayFI'm probably going to hang it up here, I'll babysit the um/202x.1 branches and recheck/fix until we get to everything being merged there21:24
cardoeWhen you get some time next week, JayF if you can gimme some feedback on https://review.opendev.org/c/openstack/ironic/+/98623321:24
JayFI suspect my monday is going to be eaten working with clif to similarly clean up ipa :( 21:25
JayFcardoe: +2a21:25
clifJayF: it failed successfully: Failed to install a bootloader when deploying node 699e1929-2f0e-4042-bcde-015b154040dd: Install of legacy BIOS bootloaders disabled by CONF.enable_bios_bootloader_install as part of CVE-2026-43003 mitigation.21:50
clifunless I need to flip the backport to defaulting to allow installing a bootloader21:51
JayFclif: so two choices here:22:06
JayFclif: 1) Create a change for that branch, subject prefix [stable-only] [ci], that adds the ability to flip that config in devstack via env variable, and set that env variable on jobs that need the partition image support enabled22:07
JayFclif: 2) Remove the partition image job.22:07
JayFTheJulia: ^ how much do we care about partition image integration testing on 2025.2?22:08
JayF(and older)22:08
TheJuliaI don't22:08
* TheJulia fires up the torch and hands it to cliff22:08
TheJuliaclif22:08
TheJulia"Can't be stuck if it is molten"22:09
JayFclif: Feel free to do a [stable-only] [ci] Disable partition image testing change and remove those jobs from the check and gate queues in zuul.d/ironic-jobs.yaml22:09
TheJulia+++++++22:09
JayFif you want a gold star22:09
JayFpush a version of the backport with the default flipped22:09
JayFand ensure it passes CI22:09
JayF(as a throwaway, testing-only change in CI)22:10
JayF(not suggesting you change the default in a merged version)22:10
clifI think this is a job for monday clif if nobody minds22:11
clifsince its past five on a friday22:11
JayFI think I said I was calling it a day around :41 minutes ago :D 22:11
JayFit's just like, the midwest/southern goodbye 22:11
JayFnow I'm actually going to close IRC and have a friday evening o/ 22:12
clifo/ glhf22:16
opendevreviewMerged openstack/ironic unmaintained/2023.1: security: move file url validation up into deploy_utils main path  https://review.opendev.org/c/openstack/ironic/+/98848022:20
TheJuliaI'm heading out in a little bit myself22:24
opendevreviewMerged openstack/ironic unmaintained/2023.1: security: validate molds url against swift in keystone catalog  https://review.opendev.org/c/openstack/ironic/+/98681722:31
opendevreviewVerification of a change to openstack/ironic unmaintained/2023.1 failed: Shell-quote console command passed to `socat`  https://review.opendev.org/c/openstack/ironic/+/98641822:31
opendevreviewMerged openstack/ironic master: doc: highlight firmware interface and deprecate management for updates  https://review.opendev.org/c/openstack/ironic/+/98623323:09
opendevreviewMerged openstack/ironic unmaintained/2024.1: security: directory transversal ISO9660 support  https://review.opendev.org/c/openstack/ironic/+/99138423:09
opendevreviewMerged openstack/ironic unmaintained/2024.1: security: disable driver_info level pxe_template override  https://review.opendev.org/c/openstack/ironic/+/99138523:18
opendevreviewMerged openstack/ironic master: api: Add schema for events API  https://review.opendev.org/c/openstack/ironic/+/95988023:44

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