Monday, 2026-10-05

shermanmran into a bit of a *fun* bug, it seems that federated accounts can't auth with system scope in keystone right now. https://review.opendev.org/c/openstack/keystone/+/97978902:35
TheJuliashermanm: are you planning on attending the PTG? Asking because we have been talking of maybe non-keystone backends03:17
shermanmmaybe, it's unfortunately a travel-heavy week for me but I can try to drop in03:19
opendevreviewJacob Anders proposed openstack/sushy master: settings: use SettingsObject ETag for updates  https://review.opendev.org/c/openstack/sushy/+/100874205:49
opendevreviewJacob Anders proposed openstack/sushy master: settings: use SettingsObject ETag for updates  https://review.opendev.org/c/openstack/sushy/+/100667105:52
kubajjGood morning Ironic! o/06:16
*** kukacz_ is now known as kukacz08:18
kukaczhi folks, does anyone have experience with Dell iDRAC 8 blades incomplete loading ISO image of IPA using virtual media mount from remote share? The issue looks so that the boot process on server starts, loads some bytes from Ironic httpd (visible in Ironic logs) and then stops. Both UEFI and legacy BIOS.10:46
mnasiadkakukacz: I’ve seen the same some time ago, iDRAC 8 doesn’t seem to be state of the art ;-)11:38
kukacz@mnasiadka, sure it doesn't. I understand Redfish was just introduced into iDRAC in that relase. Do you maybe remember any hints or workarounds that could potentially help to bring redfish/vmedia working there?11:50
mnasiadkakukacz: I ended up retrying provisioning forever and it worked after Nth time, but I only had 3 servers with idrac 8 to provision (and sort of one time) - so it wasn’t that problematic11:50
kukaczthanks! Well, repeated provisioning does not seem to work in my case.11:58
kukaczit seems to be somehow related to http requests with large offset seeks in the remote image11:59
kukaczAI helped build a single-use ISO with all content ordered in the access sequence, which worked for legacy BIOS boot11:59
kukaczthe same did not work with UEFI though. Anyway, that's far from a reliable permanent solution.12:01
TheJuliagood morning13:01
TheJuliakukacz: When booting, does the reading start after the OS gets booted?13:02
TheJuliakukacz: what version of firmware on the idrac8 ?13:02
TheJuliakukacz: another question: do you have keepalive enabled or disabled in the endpoint serving up the iso? Wait, you said remote share, are you using some other backing protocol?13:03
TheJuliashermanm: fyi, https://etherpad.opendev.org/p/ironic-ptg-2027.113:06
kukaczTheJulia, good morning! It's latest available idrac8 fw 2.86.86.86. Keepalive disabled. It's IrSO managed Ironic instance I am using as part of metal3/BaremetalOperator setup for CAPI k8s clusters.13:10
sathieuHello,13:11
kukaczTheJulia, and it's standard Ironic httpd endpoint serving the image using redfish-controlled vmedia setup. It's basically http URL the idrac uses for accessing the image, sending series of http request.13:11
TheJuliaI've heard some odd things from 2.86.86.86, but given idrac8s also all exited support windows back in ... 2020-2021 afaik and they announced EoS for updates, I wouldn't expect any new releases either, known version being >=2.70.70.70.13:12
TheJuliahello sathieu 13:12
TheJuliakukacz: I'd honestly look to see if keepalive changes the behavior at all, but UEFI on dell gear with idrac8 is also super weird and painful. :(13:13
sathieuI plan to use Ironic Standalone Networking. Is it possible to shut an interface while in tenant network, and shut another one when in -for example- provisioning network ?13:14
kukaczTheJulia, sure I was afraid of that. Just asking if someone here might have a known workaround. So you mean the version 2.70.70.70 has been confirmed to work in similar setup?13:14
sathieuI'm asking this, because we have different network switches for admin stuff (like provisioning) and end-user traffic. I want to use only one at a time.13:15
TheJuliakukacz: 2.70.70.70 was the first known and dell validated version. It was also announced to be the very last idrac8 drop at one point, and they have done a couple more since then for some unknown reasons. 13:15
TheJuliaI know in that, some oddities have appeared as well13:16
TheJuliasathieu: That is basically a entirely different model of use. I guess one might be able to achieve it with trait based networking, but provisioning/clearing is largely geared at reconfiguring all ports while moving vlans around where it sounds like you want a model where your maintaining separate staticly configured vlans and wanting toggle the machine back and forth utilizing "shut/no shut", which is just not in the model today. I 13:18
TheJuliaguess I'd more so want to understand why maintaining separate network fabrics that way when why not just use a specific vlan?13:18
kukaczTheJulia, what do you expect from enabling the keepalived? I am not very familiar with that component - I thought of keepalived only as an VRRP implementation handling LB IP assignment to healthy endpoint. 13:19
TheJuliakukacz: not keepalived, http keepalive13:19
TheJuliahttps://en.wikipedia.org/wiki/HTTP_persistent_connection13:20
kukaczTheJulia, aha, sorry. missed that. I'll check that.13:20
TheJuliaI don't know if it supports it, but apps can get weird if they are expecting keepalive to work and sockets are getting closed13:20
* TheJulia did some work on an early WAF where we found browsers and proxies which would do fun things like "expect keepalive to always work"13:21
TheJulia(so, very, much fun.13:21
TheJulia)13:21
sathieuwe have different network fabric to physically isolate networks. If a vulnerability is found on a network fabric that can allow to send a packet to another network.13:22
TheJuliaso, I guess what you need then is enhancement to be able to do specific filtering for such port selection then, unfortunately I don't think that exists today13:23
TheJuliaalegacy: clif: ^^13:24
sathieuI think we'll create an unrouted vlan, and move the port there13:24
TheJuliaironic-cores, if you have any questions/concerns about the schedule for the PTG, raise it before the meeting if possible: https://etherpad.opendev.org/p/ironic-ptg-2027.113:25
TheJuliasathieu: that should work, fwiw, clif and alegacy are deep in the networking areas, but its also a little early for them still13:26
clif TheJulia: I'm not fully awake, but you could set the category on every port to distinguish between tenant/provisioning/etc and then TBN can filter based on that?13:28
clifor is this port selection taking place at a point where tbn does not currently apply?13:29
TheJuliaclif: dunno, its not in my memory recall, which is why I tagged you :(13:30
TheJuliaclif: sathieu likely needs to explore TBN13:31
TheJulia(Trait Based Networking)13:31
sathieuok, thanks. I will read more about TBN.13:32
* TheJulia attempts to wake up with more coffee13:33
kukaczTheJulia, did you have any specific keepalive enabling parameter on mind? I am not finding any real switch or parameter in Ironic and iDRAC docs and interfaces.13:35
TheJuliakukacz: I was thinking in the http server. If not encrypted you *could* likely take a look at a packet capture and see if its trying to use a socket the server has closed out13:36
kukaczTheJulia, it is TLS encrypted actually. Though I did not find any TLS/certificate related issues in the http traffic (httpd logs only), I haven't tried disabling TLS yet.13:39
TheJuliaMight be worth a try, and would allow you to take a look under the "http cover"13:47
alegacysathieu: just want to make sure I understand...  you want to only program and enable nic1 during provisioning (w/ nic2 disabled at the switch), and then later only program and enable nic2 while then node is active (with nic1 disabled at the switch)?  whereas today, nic1 and nic2 are programmed/enabled for provisioning, and also for final deployment.13:47
TheJuliafwiw, it feels like a fundimentally different network_interface model to me13:49
TheJuliasince its sort of toggling from one side to another13:49
alegacyI could see maybe a middle ground where we could say only the primary nic is used for prov/insp/rescue/servicing/etc... but secondary nics are also used for tenant networks.13:55
opendevreviewMichal Nasiadka proposed openstack/bifrost master: Add experimental arm support for Ubuntu/CentOS  https://review.opendev.org/c/openstack/bifrost/+/100880414:02
opendevreviewMichal Nasiadka proposed openstack/bifrost master: Add experimental arm support for Ubuntu/CentOS  https://review.opendev.org/c/openstack/bifrost/+/100880414:03
opendevreviewMichal Nasiadka proposed openstack/bifrost master: Add experimental arm support for Ubuntu/CentOS  https://review.opendev.org/c/openstack/bifrost/+/100880414:04
opendevreviewMichal Nasiadka proposed openstack/bifrost master: Add experimental arm support for Ubuntu/CentOS  https://review.opendev.org/c/openstack/bifrost/+/100880414:12
opendevreviewMichal Nasiadka proposed openstack/bifrost master: Add experimental support for ARM64 hosts on Ubuntu/CentOS  https://review.opendev.org/c/openstack/bifrost/+/100880414:13
TheJuliaalegacy: I guess it all boils down to the overall expected operating model14:14
opendevreviewMichal Nasiadka proposed openstack/bifrost master: Experimental support for ARM64 hosts on Ubuntu/CentOS  https://review.opendev.org/c/openstack/bifrost/+/100880414:14
alegacyTheJulia: agreed.  14:16
JayFTheJulia: fwiw tbn is entirely in the neutron network interface14:35
JayFYou don't need inference magic for standalone networking since you can just declaratively say what you want, how ironic14:35
JayF**in Ironic 14:35
TheJuliatrue, I guess as long as shutdown is set, one could manually toggle it all out in standalone just as long as you never allow non-administrative access to ironic14:36
JayFIt certainly is an interesting idea to use left-side and right-side interfaces for this. It's probably a pretty cheap way to retrofit something that doesn't have smart switches.14:37
JayFCertainly not something that any of our models currently cover14:37
JayFBut even if you were trying to do this without smart switches, someone in-band being able to "up" the provisioning interface would kill any security benefit14:38
TheJulia... switches which are not smart these days?!14:45
TheJulialooks like there are some limited SMB 16-ish port switches which are not considered "unmanaged", 2.5g line rate, so semi-reasonable I guess14:48
opendevreviewTakashi Kajinami proposed openstack/networking-generic-switch master: Drop sys_platform marker for win32 system  https://review.opendev.org/c/openstack/networking-generic-switch/+/100881214:51
sathieualegacy: yes14:56
sathieuI want nic1 for prov/insp/rescue/servicing/... and nic2 for tenant network. But one at a time14:57
JayFsathieu: What is the motivational factor behind wanting to use the separate NICs? Security? Performance?14:58
sathieuSecurity14:59
sathieuActually, this is a recommandation of our security experts to have a physically different network15:00
TheJuliaThere is a class of user who doesn't view logical delineation as sufficient security controls for switch, but even in the environment I worked like a decade we finally got vlans to be acceptable approaches15:00
TheJuliaWe meeting today?15:01
JayFYeah, this is one of those things where picking that kinda architecture would make it different enough I'd worry more about the gaps it creates than the ones it closes15:01
JayFyup, idr who is running it15:01
TheJulia#startmeeting ironic15:01
opendevmeetMeeting started Mon Oct  5 15:01:40 2026 UTC and is due to finish in 60 minutes.  The chair is TheJulia. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'ironic'15:01
kubajjo/15:01
TheJuliaI think, it might be me? Or someone else want to?15:01
JayF#topic Announcements/Reminders15:02
Mahnooro/15:03
JayF#note We released OpenStack 2026.2 last week. Good job.15:03
TheJulia#chair JayF 15:03
opendevmeetCurrent chairs: JayF TheJulia15:03
JayF#topic Announcements/Reminders15:03
JayF#note We released OpenStack 2026.2 last week. Good job.15:03
JayF#note Thanks to cardoe for repping Ironic at the OpenInfra Live15:03
JayF#note PTG is next week! Please take time to rest up this week, review the etherpad, and bring your brains!15:03
JayF#link https://etherpad.opendev.org/p/ironic-ptg-2027.115:03
cido/15:04
estherd[m]o/15:04
JayFI'd especially ask core reviewers and approvers, or generally anyone who is expert in a subsystem, to  look at the architectural sharing portion scheduled for 1400 UTC Wednesday15:04
JayFand volunteer to teach a short 10 minute session on that subsystem15:04
JayFfeel free to add one if you think it's needed, either as one you can give or one you need to hear15:05
JayFTheJulia: fwiw IDK who was signed up to run the meeting, but I'd rather JFDI than figure it out :D 15:05
JayFAny other comments about PTG? 15:05
TheJuliaJayF: I appreciate it, I'm dealing with very unhappy sinuses15:05
JayFTheJulia: we had a special meeting of the unhappy club at 4am this morning over here, when the smoke alarm ran low on battery and the dog ran high on panic :D 15:06
JayFI'm going to hope folks read the PTG notes even though it [crickets] in here :D 15:07
MahnoorI read your Friday msg about architectural session, Jay, I will add any questions/topics I can upfront 15:07
JayF#topic Working Group Updates15:07
JayFI doubt there's a meaningful update for anything here.15:07
JayFAsync IO working group is likely doing PTG planning15:07
JayFIronic coresec team has nothing public to report; I'll note that the moratorium on advisories is lifted since the release is done15:07
JayFspeak up quickly if you have something to add here15:08
* TheJulia calls for proceeding15:09
JayFNo discussion topics, skipping.15:09
JayF#topic Bug Deputy Updates15:09
JayFTheJulia: is listed as the bug deputy15:09
TheJuliaI think Mahnoor took care of the past week, I took a look at items the week before15:09
MahnoorYep, I took a look on Friday, updated the agenda notes15:10
TheJuliaThanks Mahnoor!15:11
MahnoorJulia was looking at older items to try and lighten the backlog, I believe?15:11
MahnoorNo problem :)15:11
TheJuliaYup, I closed out some older items which didn't get closed out15:11
MahnoorThats nice, thank you!15:11
JayFI suggest we just forgo a bug deputy the next two weeks15:12
JayFso contributors can focus on ptg15:12
TheJulia++15:12
cid++15:13
JayF#note No bug deputy assigned until post PTG.15:13
JayFThere are two RFEs listed for review; unsure if they are old?15:14
JayF#link https://bugs.launchpad.net/ironic/+bug/216851915:14
TheJulia1-2 weeks, accordingly15:14
JayF2168519 seems like an obvious enhancement15:14
JayFbut I do think we should talk some about the shape of the change in that RFE, moreso than we have been15:15
TheJuliaI think that one is reasonable, however... its an entirely different tool/operator model and I'm unsure if any of us can just magically do so15:15
JayFis this another interface? Making container interface different in all cases?15:15
TheJulialikely different runtime interface driver which dicates local configuration modeling15:15
JayFI would suggest we put off officially approving the RFE until those questions are answered; I think this config is already pretty complex and am nervous about which dimension this would grow off of15:15
TheJuliasince its local networking, which is a bit weird.15:15
TheJuliayeah, without a bit more detail, that one is... difficult15:16
JayFyeah if it's a different implementation of the interface, I'm +215:16
JayFif it's container with 15 flags to flip just right to make it more secure... eh15:16
TheJuliaDifferent networking style on the host, where kolla launches containers directly from a runtime15:16
JayFack, I'll mark it approved and make a comment saying this should be a net-new interface15:17
JayF(and we're OK with it being kolla-specific, I'd assume)15:17
TheJulialikely, I don't remember offhand the slicing of the driver15:17
TheJuliabut yeah, If they want to post a patch, I'm good with that15:17
JayF#link https://bugs.launchpad.net/ironic/+bug/216895615:18
JayFThis one... (sorry kubajj) -- I am kinda -1 on15:18
kubajjI understand your point15:19
JayFoh, this isn't the one I thought it was? 15:19
kubajjI think it is15:19
JayFI think this desc was edited to be more palatable :)15:19
JayFand it is more palatable now lol15:19
kubajjyes, John has made some changes15:19
JayFI would prefer a model where we actually set cleaning and provisioning network *to the same neutron network*15:20
TheJuliaits actually super similar to what rackspace did ages ago, except it doesn't pre-bake an image automatically15:20
JayFif that security boundary is being broken, why erect it at all in this use case?15:20
kubajjyes, that would be great, but apparently, we have to deal with cleaning network as dirty15:20
JayFTheJulia: clif actually wrote that code, and it was quite a bit different (mainly because Ironic would just let agents heartbeta forever regardless of state)15:21
TheJuliaI sort of like the idea, your staging the hosts as on, heartbeating, waiting for the deploy request on the provisioning network, which better aligns with GPU capacitors15:21
JayFoh yeah15:21
* JayF is really anchored to that original writing15:21
JayFthis never puts an unclean machine on the provisioning network15:21
* TheJulia hands JayF moar coffee15:22
TheJuliayup15:22
JayFso it actually preserves the security barrier15:22
kubajjI hope it doesn't - that's what I tried to go for :D15:22
JayFthis feels OK? but I am nervous about something like this which can have serious security impacts15:22
JayFand bluntly is a feature so shiny everyone will want it yesterday15:23
JayFI wonder if we should spec it just so we can get a best case "1.0" release on it15:23
JayFbecause this is a switch half of our users are gonna wanna flip15:23
JayFkubajj: I review a smidge more aggressively when I know my downstream is gonna love a feature b/c it means I'm gonna be subjected to a finger-waggle if it doesn't work :D 15:23
kubajjJayF: that's why we wanted to discuss it at the PTG - spec is also up for review, happy to take your feedback15:25
JayFi really do need coffee, it's linked from the bug too15:25
JayFI'll leave that tab open to review it. After I've had coffee and breakfast. /me points to earlier message about 4am wakeups as a lame excuse15:26
kubajjno worries15:26
JayFsince that's got a spec, no decision to be made in meeting15:26
JayF#topic Open Discussion15:26
kubajjthanks for having a look15:26
JayFAnything for Open Discussion?15:26
JayFOne note: goes without saying there's no meeting next week15:26
JayFI'll email about it15:26
TheJuliaI sent a note to the mailing list regarding the ptg etherpad15:26
TheJuliaseparately, I also added two items to the ops etherpad (https://etherpad.opendev.org/p/ops-devs-qanda-2026)15:27
JayFthanks15:27
JayFAnyone wanna volunteer to chair the October 19th 2026 meeting (post-PTG)15:28
TheJuliaI think the schedule is fairly solid, I had to shuffle things a little because of timing with Cinder and proposed what seemed to be a possible time window15:29
TheJuliaI can15:29
JayF#action TheJulia to chair October 19 meeting. October 12 meeting cancelled.15:29
JayFThanks all for coming to the meeting, gonna close it up.15:31
JayF#endmeeting15:31
opendevmeetMeeting ended Mon Oct  5 15:31:20 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:31
opendevmeetMinutes:        https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-10-05-15.01.html15:31
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-10-05-15.01.txt15:31
opendevmeetLog:            https://meetings.opendev.org/meetings/ironic/2026/ironic.2026-10-05-15.01.log.html15:31
cardoeclif: trying to mess further with TBN and I'm stuck...16:41
cardoeSo if I've manually created a port group before and I wanna attach it... I'm not sure how to do that.16:41
cardoehttps://www.irccloud.com/pastebin/YOuRNQFO/16:42
cardoeThat's the entirety of my TBN config right now.16:42
cardoeopenstack baremetal node vif attach be5191a4-3001-475b-adb2-3ea37cc21b2b db4a3edf-a4b1-4297-9d88-c83308ab5989 --portgroup-uuid e14bf067-ace0-439b-8c32-e185a18227c916:43
cardoeIs what I'm running16:43
cardoehttps://www.irccloud.com/pastebin/h0L0g2eA/16:43
cardoeIt's only ever selecting one of the two ports that make up that port group and never the port group itself.16:44
cardoeAlso looking at https://docs.openstack.org/ironic/latest/references/trait-based-networking/tbn-config-file.html#trait-layout the documented example is impossible for it to work. port groups don't have a vendor field which is what lead to the bug I reported.16:45
JayFcardoe: attach_portgroup is a separate action IIRC16:45
* JayF checks docs16:46
JayF> attach_portgroup - Attach (portgroup, network) pairs that pass this action’s filter expression.16:46
JayFyep, just below your link there16:46
cardoehrm.. okay well the documented example couldn't ever work then. Cause the example has you using attach_port for a portgroup.16:46
JayFlol16:46
JayFvalid16:46
clif:(16:46
cliflet's fix the docs!16:46
cardoeThat works for me.16:47
cardoeI pointed my folks at the docs.16:47
cardoefwiw https://review.opendev.org/c/openstack/ironic/+/1008516 is what I even needed to run to not hit the 500 error16:47
cardoeSo we're testing stable/2026.1 plus that patch right now.16:47
cardoeJust trying to iterate through how we can roll out TBN.16:48
clifI'm +2 on it, let's get someone else on it16:48
* cardoe pokes JayF 16:48
clifI'm excited16:48
JayFcardoe: I don't think we have a way to express (when reviewing 100851), I want a portgroup consisting of ports made by $vendor16:48
clifI'll fix those docs, the example *is* wrong now that I re-read it16:49
JayFcardoe: which is a design issue we can address, but is a downside of the fix path chosen16:49
JayF(another fix path could be: evaluate port.vendor as the vendor of the ports that are members, with an error if the port vendors mismatch)16:49
cardoeYou don't have a way to express that.16:49
cardoeBut right now it throws a 500 error even if you're not using a vendor at all.16:49
cardoeWe only use category right now. We have some ports with a category of "network" and others that are unset.16:50
cardoeThat's our only test case16:50
cardoeor I should say... dip of our toe in the TBN waters16:50
JayFyeah really if you need to care about vendor of the individual nics16:52
JayFyou should be using group-and-attach16:52
JayFotherwise you can just put some metadata on your portgroup to match16:52
clifdynamic portgroups ~_^17:01
cardoeYeah I haven't even gotten to dynamic portgroups with the team.17:02
cardoehttps://www.irccloud.com/pastebin/lKP1f6dV/17:04
cardoeThat's what I'm gonna have them re-test with.17:04
cardoeMy intention is to have them update the docs and work with dynamic portgroups.17:06
opendevreviewMerged openstack/ironic master: Fix TBN Portgroup creation accessing nonexistent vendor field  https://review.opendev.org/c/openstack/ironic/+/100851617:46
cardoewould something like "openstack baremetal port group add/remove" make sense as commands to add a port to a port group?17:51
cardoeApparently it wasn't apparently that "openstack baremetal port set --port-group <uuid> <uuid>" was the process.17:51
cardoeI'm not talking about replacing just in addition to for user experience.17:52
cardoeadd/remove could take 1 port group and 1 or more ports to add17:53
cardoewhat about "openstack baremetal node list --instance-id <uuid>" or should it be --instance-uuid? We've got a --instance-name flag.18:02
JayFI think --instance <uuid-or-name> works, iirc?18:06
opendevreviewMerged openstack/ironic master: Make TBN comparisons against unset variables never match  https://review.opendev.org/c/openstack/ironic/+/100851718:15
cardoeJayF: nope the flag is --instance-name and it doesn't filter uuid18:34
cardoeWell getting closer with TBN and port groups... Unable to complete operation on port 06edec49-b86b-4359-b61a-32e996c44c9e, port is already bound, port type: other, old_mac fa:16:3e:98:28:d2, new_mac 14:23:f3:f5:24:a118:35
cardoeThat's what you get back from the vif attach call18:35
cardoeBut it actually did work in the end.18:35
cardoeit just returns an error message.18:36
cardoeAnd nova treats the error as a failure.18:36
JayFthat usually means the vif had already been attached or something18:36
JayFI would be 100% sure that wasn't an enviornmental leftover from previous failures18:36
JayFTheJulia: sorry, I -1'd https://review.opendev.org/c/openstack/ironic/+/1008314/1#message-9c7a254416d30720dc83aff53db59be1385f01a1 -- if you want me to execute the change to the error message I request, I can19:27
JayFI'm basically thinking: if I have access to start deployments in ironic, I can extract the key_id for any image I want19:28
TheJuliaThe assumption there is that the risk is someone somehow can't see the field, I guess it maeks sense to yank the bit in the error, if you have time that woudl be awesome since I'm about to jump on a meeting and honestly I'd rather be in bed since I've got a cold/evil sinus thing going on19:29
JayFyep I'll patch it, that's why I offered19:30
TheJuliamuch appreciated19:30
* TheJulia goes and joins last call of the day19:30
JayFit's mildly farfetched but at this point I don't wanna add any more potential shenanigans19:30
TheJuliafair19:30
opendevreviewJay Faulkner proposed openstack/ironic master: Reject Glance encrypted images during validation  https://review.opendev.org/c/openstack/ironic/+/100831419:36
*** darmach5 is now known as darmach21:04
*** Unknown123 is now known as Mike--21:04
opendevreviewDoug Goldstein proposed openstack/ironic stable/2026.2: Fix TBN Portgroup creation accessing nonexistent vendor field  https://review.opendev.org/c/openstack/ironic/+/100888723:36
opendevreviewDoug Goldstein proposed openstack/ironic stable/2026.1: Fix TBN Portgroup creation accessing nonexistent vendor field  https://review.opendev.org/c/openstack/ironic/+/100888823:37

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