Thursday, 2024-03-07

rpittaugood morning ironic! o/08:10
rpittauadam-metal3: I went through the discussion here and from my experience I can unfortunately confirm the general slowness with iDRAC job queue and more weirdness, although that usually happens when the BMC firmware version has something "wrong"08:21
rpittaubeing a 16G I suggest to verify that you have iDRAC9 v7.00.60.00 first to exclude any known issue08:21
adam-metal3rpittau, thanks for the inofo !08:47
SvenKieskehi o/ can we get this still in for the release? it has one +2 https://review.opendev.org/c/openstack/networking-baremetal/+/903995 I didn't see any networking-baremetal release just yet, did I miss that?10:02
opendevreviewKamil Gustab proposed openstack/sushy master: Adds Ethernet Interfaces for manager.  https://review.opendev.org/c/openstack/sushy/+/90945111:41
iurygregorygood morning Ironic11:46
dtantsurSvenKieske: it's probably too early for networking-* releases12:02
SvenKieskedtantsur: I was referring to the fact that a release was demanded "ASAP" from the release team, see: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/EGD6IP3W2KFT33HJDLJNK2KM5ZXFFWM3/#IIFQQPNMEAOUUXF7XVDQJK7E5FBKKMOM12:13
SvenKieskeso I just wanted to make sure that patch makes the release, seems there are 7 days to go12:14
dtantsurHmm, maybe my internal clock is off, and you're right. JayF and rpittau are the people to talk to.12:19
opendevreviewcid proposed openstack/ironic master: Fix data length exceeding limit error  https://review.opendev.org/c/openstack/ironic/+/91097312:22
opendevreviewcid proposed openstack/ironic master: Fix data length exceeding limit error  https://review.opendev.org/c/openstack/ironic/+/91097312:25
rpittauSvenKieske: I think we're still in time, I've approved the patch13:11
rpittauonce that merges we'll add the release13:14
SvenKieskerpittau: thank you :)13:14
opendevreviewDmitry Tantsur proposed openstack/ironic master: [PoC] Verify agent TLS certificate and provide diagnostics  https://review.opendev.org/c/openstack/ironic/+/91111613:31
TheJuliaGood morning14:16
rpittauhey TheJulia :)14:16
TheJuliaQuick and easy backport: https://review.opendev.org/q/I33e76929ca9bf7869b3b4ef4d6501e692cf0a92214:21
TheJuliaAnd a tempest fix: https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/909939 :)14:21
jrossermaybe this is old news, but it looks interesting https://github.com/IBM/DPFS14:31
TheJulianeat14:32
dtantsurwow14:32
TheJuliaNot exactly what nvidia would prefer you do, *and* on an end of life card, but cool14:32
jrosseri stumbled across that becasue i have a use case for ironic + large shared dataset but we have multi-tenancy14:34
jrosserso it's all a bit /o\ to implement nicely14:34
rpittauinteresting14:34
jrosserbtw if i'm missing an obvious answer for multitenancy vs. ironic vs. shared filesystems thats self-service for users then do let me know :)14:39
TheJuliafor filesystems, that is a bit of a niche thing. :)14:40
TheJuliaFor networking, I'd <3 us to be able to program DPUs14:40
TheJuliato specific networks, but to do it securely, we would need to have OOB programming access14:41
TheJuliaand... well... the likely only way that will happen is if someone just submits patches or existing contributors suddenly have some cards14:41
TheJuliaor a company or two partners on the topic14:41
opendevreviewcid proposed openstack/ironic master: Fix data length exceeding limit error  https://review.opendev.org/c/openstack/ironic/+/91097314:44
jrosserTheJulia: do you think most of that programming is already acheived here? https://docs.openstack.org/neutron/latest/admin/ovn/smartnic_dpu.html14:47
TheJulianope14:47
jrosserah interesting14:48
TheJuliawlel14:48
TheJuliawell, actually, that looks like it has been updated14:48
TheJuliaso that *might* do the needful14:50
TheJuliajust nobody has likely pieced it together in a non-virtualized context to see if the physical function is presented to the host sufficently for use14:50
opendevreviewMerged openstack/networking-baremetal master: don't force amqp_auto_delete for quorum queues  https://review.opendev.org/c/openstack/networking-baremetal/+/90399515:06
opendevreviewSven Kieske proposed openstack/networking-baremetal stable/2023.2: don't force amqp_auto_delete for quorum queues  https://review.opendev.org/c/openstack/networking-baremetal/+/91161115:08
opendevreviewSven Kieske proposed openstack/networking-baremetal stable/2023.1: don't force amqp_auto_delete for quorum queues  https://review.opendev.org/c/openstack/networking-baremetal/+/91161215:08
opendevreviewOpenStack Release Bot proposed openstack/ironic-lib stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/ironic-lib/+/91187015:35
opendevreviewOpenStack Release Bot proposed openstack/ironic-lib stable/2024.1: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/ironic-lib/+/91187115:35
opendevreviewOpenStack Release Bot proposed openstack/metalsmith stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/metalsmith/+/91187215:35
opendevreviewOpenStack Release Bot proposed openstack/metalsmith stable/2024.1: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/metalsmith/+/91187315:35
opendevreviewOpenStack Release Bot proposed openstack/metalsmith master: Update master for stable/2024.1  https://review.opendev.org/c/openstack/metalsmith/+/91187415:35
opendevreviewOpenStack Release Bot proposed openstack/python-ironic-inspector-client stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/python-ironic-inspector-client/+/91187515:35
opendevreviewOpenStack Release Bot proposed openstack/python-ironic-inspector-client stable/2024.1: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/python-ironic-inspector-client/+/91187615:35
opendevreviewOpenStack Release Bot proposed openstack/python-ironic-inspector-client master: Update master for stable/2024.1  https://review.opendev.org/c/openstack/python-ironic-inspector-client/+/91187715:35
opendevreviewOpenStack Release Bot proposed openstack/python-ironicclient stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/python-ironicclient/+/91188215:35
opendevreviewOpenStack Release Bot proposed openstack/python-ironicclient stable/2024.1: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/python-ironicclient/+/91188415:35
opendevreviewOpenStack Release Bot proposed openstack/python-ironicclient master: Update master for stable/2024.1  https://review.opendev.org/c/openstack/python-ironicclient/+/91188615:35
opendevreviewOpenStack Release Bot proposed openstack/sushy stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/sushy/+/91188715:36
opendevreviewOpenStack Release Bot proposed openstack/sushy stable/2024.1: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/sushy/+/91188815:36
opendevreviewOpenStack Release Bot proposed openstack/sushy master: Update master for stable/2024.1  https://review.opendev.org/c/openstack/sushy/+/91188915:36
rpittaugoing to aske release of networking-baremetal once https://review.opendev.org/c/openstack/networking-baremetal/+/907552 merges15:54
opendevreviewMerged openstack/ironic-lib stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/ironic-lib/+/91187016:07
opendevreviewVerification of a change to openstack/ironic-lib stable/2024.1 failed: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/ironic-lib/+/91187116:07
opendevreviewMerged openstack/sushy stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/sushy/+/91188716:10
opendevreviewMerged openstack/sushy master: Update master for stable/2024.1  https://review.opendev.org/c/openstack/sushy/+/91188916:13
opendevreviewMerged openstack/python-ironic-inspector-client stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/python-ironic-inspector-client/+/91187516:15
opendevreviewVerification of a change to openstack/python-ironic-inspector-client stable/2024.1 failed: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/python-ironic-inspector-client/+/91187616:15
opendevreviewMerged openstack/ironic master: fix errors messaging around network mappings  https://review.opendev.org/c/openstack/ironic/+/90993816:17
opendevreviewMerged openstack/sushy stable/2024.1: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/sushy/+/91188816:19
opendevreviewMerged openstack/python-ironicclient stable/2024.1: Update .gitreview for stable/2024.1  https://review.opendev.org/c/openstack/python-ironicclient/+/91188216:20
opendevreviewVerification of a change to openstack/python-ironicclient stable/2024.1 failed: Update TOX_CONSTRAINTS_FILE for stable/2024.1  https://review.opendev.org/c/openstack/python-ironicclient/+/91188416:20
opendevreviewMerged openstack/ironic stable/2023.2: neutron: do not error if no cleaning/provisioning on launch  https://review.opendev.org/c/openstack/ironic/+/91031016:21
opendevreviewVerification of a change to openstack/ironic stable/2023.1 failed: neutron: do not error if no cleaning/provisioning on launch  https://review.opendev.org/c/openstack/ironic/+/91031116:21
opendevreviewVerification of a change to openstack/ironic-tempest-plugin master failed: Invoke tests with fake interfaces  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/90993916:27
JayFI think our gate on master is busted in a new wya16:34
JayF*way16:34
TheJuliaPlease submit liquor.16:35
JayF> E: Unable to locate package ksmtuned16:35
TheJuliaPlease submit liquor.16:35
JayFhttps://zuul.opendev.org/t/openstack/build/9a66172336da4a7880310599d250129716:35
JayFironic-tempest-functional-python316:35
TheJuliaPlease submit liquor.16:35
* TheJulia has decided, next career will be that of a bending robot16:35
JayFTheJulia: https://usercontent.irccloud-cdn.com/file/w6GFb07u/image.png16:36
clarkbJayF: the actual error is ab it higher than that16:36
clarkbCould not resolve 'mirror.dfw.rackspace.opendev.org'16:36
JayFoh phew16:37
JayFI was already digging myself down a hole16:37
JayFthanks for the rope16:37
clarkbwhich can happen for one of a million reasons. The simplest of which is dns resolution locally got broken16:37
JayFwait, I thought clouds had 100% reliable networks16:37
clarkboh I know what the problem is16:38
JayFand that no problems in computer science were dns16:38
JayFoooh, a not-random-failure is more interesting for sure :D16:38
clarkbarg this was an unexpected side effect of us testing new rax credentials to deal with their new MFA mandate that will break normal API access16:38
clarkbwe have a second set of credentials with a different cloud name and that changes everything down the line apparently. It should be mirror.dfw.rax.opendev.org16:39
TheJuliaJayF: did you ever watch futurama?16:39
JayFTheJulia: I have no strong feelings one way or the other.16:39
clarkbI'm going to revert the change but jobs will need to be rechecked. Give me a few16:39
JayFTheJulia: (that's a futurama reference, btw)16:40
TheJuliaJayF: :)16:40
TheJuliaJayF: I was thinking about the time Fry was admitted to an robot insane asylumn16:41
TheJulia"cloud networking is 100% reliable"16:41
JayFTheJulia: why do you think I took April 1-5 off? Gotta practice my stabbin'16:41
JayFTheJulia: that is like, top 5 futurama episodes for me. I also love the part (I think it's same episode?) where bender is like "I had a nightmare! There were all these 1s and 0s .... but I think I saw a 2!" "No Bender, there's no such thing as 2!"16:42
clarkbJayF: ok I manually reverted the change and jobs starting on new test nodes should be good now16:44
opendevreviewAlex Welsh proposed openstack/bifrost master: Improve downloaded deployment image support  https://review.opendev.org/c/openstack/bifrost/+/88488816:46
*** jamesdenton_ is now known as jamesdenton16:48
jamesdentonGood morning, Ironic. Question about scheduling -- if a user wanted to target a specific baremetal node for a deployment, is the best/only way to do that via a unique trait and flavor? Or is there another way?16:49
JayFSo, lets contextualize16:49
JayFyou can do that *via Ironic APIs directly*16:49
JayFbut I assume you mean scheduling thru nova?16:50
jamesdentonnova, yes16:50
JayFThen, yes. I've worked places that carried a patch to do it, but it's really not part of the OpenStack model to do it that way16:50
jamesdentonagreed16:50
JayFUsing Ironic standalone, you can target whatever node you want (and we don't really have a concept of scheduling)16:50
jamesdentonand i don't think we'd want to carry a patch, either16:50
JayFLike, I suspect direct Ironic API access might be your answer16:50
JayFbut the complexity of your environment can change that up some16:51
JayFwe support "BMaaS" without having Nova involved, node.owner sets project that owns the node, you can even use node.lessee to temporarily "lease" it out to another project16:51
jamesdentonDirect Ironic is likely the long term approach, but for now we're using Nova. Although, it might simplify things to not use Nova, i just haven't had time16:51
JayFit just gets hairy if you are making all the coordinating API calls yourself to do the needful in neutron and all that16:51
JayFwell, I'm trying to say you don't have to choose16:51
JayFtake nodes for nova, mark them as "owned" by a project, ensure nova user for ironic is scoped to that project16:52
jamesdentonok16:52
JayFnodes for direct-deploy, set owner to another project (preferably end user project), then use those separately16:52
JayFThis is not only "it works" but we explicitly support this mixed mode of operation16:52
jamesdentonoh i gotcha16:52
jamesdentonin the direct-deploy model, is it still possible leverage neutron and ml2 driver? 16:53
JayFyes; I think you might have to make some calls to neutron that nova would make yourself16:53
dtantsurJayF: nit: we do have a concept of scheduling, it's called allocation API :) 16:54
JayFjamesdenton: dtantsur and Julia do know more about this stuff than I do, I just think it's cool ;) 16:54
jamesdentonit IS cool16:54
-opendevstatus- NOTICE: Jobs that fail due to being unable to resolve mirror.dfw.rackspace.opendev.org can be rechecked. This error was an unexpected side effect of some nodepool configuration changes which have been reverted.16:54
JayFjamesdenton: basically end result is you could have "N" separate Novas, just segregated by project, none of which can see nodes from the other16:55
JayFe.g. openstack baremetal node list while scoped to project "X" only sees nodes with node.owner/node.lessee=X 16:56
JayFIDK if anyone's deployed it this way, but you shuold be able to go full baremetal multitenancy with Ironic only16:56
JayF(meaning, no Nova, not, no other openstack-y bits)16:56
jamesdentonok, i understand that model. I think the difficulty here for the teams involved is the mental shift of "this server is device 123456 and it has IP address x.x.x.x" and that lives in CORE tooling. There's no separation of the logical device number and physical device. In this new model, there would be. We don't have a way to reflect that relationship *in our existing tooling* even though the Ironic API can provide that info16:58
jamesdentonthat will change (and is changing) but a slow change, indeed16:59
JayFjamesdenton: you wanna have a sync chat about this? You know I spent almost a decade at Rackspace so I have some insights at least to how things might fit17:02
JayFjamesdenton: getting Rackspace back using and contributing to Ironic is well worth a half hour of my time :D 17:03
jamesdentonwe definitely can17:03
jamesdentoni will email you an invite and bring Kevin along17:03
JayFfun17:03
JayFif you do something especially cool, amybe I'll mail you this classic Rackspace OnMetal bear flag LOL17:04
jamesdentonOnMetal is still rocking along17:05
jamesdenton:D17:05
jamesdentonjust like you left it17:05
JayFdo I wanna know ...yeah17:05
JayFthat's mainly what I'm afraid of lol17:05
JayFI remember when I worked on a team building custom linux LBs/firewalls. I left that team to do other things at the company. Three years later I see someone working on them, ask them to run `uname -a` and see nobody has built a patched kernel for them in that period of time.17:06
JayFI'd rather something I built get torn down than bitrot :( 17:06
rpittaugood night! o/17:06
JayFo/17:06
jamesdenton<insert side-eyed monkey meme here>17:06
JayFlol exactly17:06
dtantsurJayF: hey, not sure if you saw my ping the other day, this is the TLS skew detection PoC we talked about: https://review.opendev.org/c/openstack/ironic/+/91111617:10
dtantsurI mean, one of the approaches. I don't know how to extract information from an SSLError17:10
JayFI saw the ping, but was getting massively squirreled yesterday and it fell outta my brain17:10
* dtantsur is fascinated by "squirreled"17:11
JayFlike a golden retreiever, when they see a squirrel, their attention just goes BOOM over to that17:11
JayFit's a good analogy for how some people are easily distracted. and yesterday was a day of shiny objects distracting me at every turn (like, actual things I needed to do, just little that I *planned* to do)17:12
* dtantsur has just learned he is a golden retriever17:12
JayFwe all are, we all are17:12
TheJuliawait, what do I know more about? what should I hide from?!?!?!?!17:13
TheJuliadtantsur: wait, what?!17:13
dtantsursquirrels? golden retrievers?17:14
* dtantsur got distracted and does not know any more17:14
TheJuliasquirrel?!? where!?!17:14
TheJuliajamesdenton: did nova kill the undocumented "place on compute node" hint via the command line? some folks at one point in time would just put the ComputeNode hostname which matched the ironic node uuid, but this long in the past.17:16
JayFhonestly TheJulia's talk at last summit about Ironic RBAC17:22
JayFis basically required watching for this topic17:22
TheJuliawho? what? huh? why?17:22
TheJuliaPlease hold, I need to go place a thumper and ride a sand worm away from my computer.17:23
jamesdentonTheJulia I do think that still exists as --availability-zone nova:<compute> .... might be worth trying that17:31
TheJuliaso, I'm still kind of worried about the RBAC topic17:32
JayFin what way?17:32
TheJuliawell, the mention of rbac has me wanting to go join the fremen17:33
* TheJulia might have been flying an ornothopter the last few nights and working on landing17:34
* TheJulia needs to map the wind break to a break button17:34
TheJulias/wind/wing/17:34
JayFI recommend you, also, take a week off soon LOL17:36
TheJuliaI've been thinking about doing so17:36
opendevreviewVerification of a change to openstack/networking-baremetal master failed: Bump hacking to 6.1.0  https://review.opendev.org/c/openstack/networking-baremetal/+/90755217:43
opendevreviewDmitry Tantsur proposed openstack/ironic master: Fix error handling in the virtual media attach API  https://review.opendev.org/c/openstack/ironic/+/91195217:49
dtantsura small patch for a nasty defect if anyone has time ^^17:52
TheJuliaohhh ahhh17:52
TheJuliaso whatever is calling do_virtual_media_attach was not catching any exceptions/errors?17:53
dtantsurTheJulia: it's called inside spawn_worker17:54
TheJuliaoh17:54
dtantsurthere is basically nothing above it17:54
TheJuliasigh17:54
JayFyeah17:54
TheJuliayeah, that would do it17:54
JayFconfirmed that myself just now, too17:54
dtantsurI got really bamboozled while testing my gophercloud patch for this feature17:54
dtantsurEverything is successful and then... silence? :)17:55
JayF> exc_info=not isinstance(exc, exception.IronicException) 17:55
JayFis the only thing weirding me out about that change17:55
TheJuliathat is about as bad as a customer who I have a call with tomorrow who the media attaches, but the hardware boots via pxe17:55
JayFwhy don't we want exc_info if it's an IronicException?17:55
dtantsurJayF: We do it quite often. What it says is "log traceback if unexpected (= not ironic-produced) exception"17:55
JayFack17:55
JayFthat is what I assumed re: desire but wanted to validate17:55
dtantsurthink about stuff like KeyError. Without a traceback it's impossible to debug17:56
dtantsur(it's error message is the missing key)17:56
JayFmy question would've been pointed more towards "why not always true"17:56
JayFnot the other way around :D17:56
dtantsurIdeally, our exceptions should be self-explanatory without a traceback :) otherwise, putting them in last_error is no so helpful17:56
dtantsurPython's tracebacks are helpful but also very verbose, especially now that they also print traceback for the whole exception chain17:57
TheJuliahttps://bugs.launchpad.net/ironic/+bug/2056248 <-- I wonder if such an old version of eventlet would cause an issue like that18:26
JayFI'm more thinking, bugs in graceful shutdown, perhaps18:27
TheJuliaoh, conductor-0 was working, lost connectivity to the db18:28
JayFyeah18:28
JayFthe errors from greenlet are timeouts on the socket18:28
JayFthis just looks like networking done wrong?18:28
TheJuliayeah18:28
JayFNow, I'd buy we might have some bugs where18:28
JayFif you spin up conductor, no sql server18:28
JayFsql server comes online/available some time later18:28
JayFthat's a weird case we don't test and I wouldn't be stunned to find dragons around those cases; but this ain't it18:28
TheJuliawell, it won't start without it18:32
TheJuliabut if you bounce the server, depending on log level/settings, it might never log anything depending on the sql command line18:32
TheJuliaalso interestingly enough, they have an error regarding Portgroup model being unknown.18:32
TheJuliaall very weird.18:32
Sandzwerg[m]<TheJulia> "jamesdenton: did nova kill the..." <- Still works for us but you need to know the availability zone of the node and the node UUID20:39
TheJuliaSandzwerg[m]: awesome, thanks20:40
Sandzwerg[m]We are still on xena, but from my understand stand shouldn' t change. As for OpenStack a single node is a hypervisor and, at least with enough rights, you can force a instance on a specific hypervisor20:41
Sandzwerg[m]*ironic node20:42
TheJuliaYeah, now that you mention it, I think you have to be an admin to use that option21:12
jamesdenton_well, i'm not so sure -- a nova availability-zone-list only shows the conductor nodes themselves as eligible hosts, not the individual baremetal nodes. Although, those show up in 'openstack hypervisor list'21:17
jamesdenton_throwback: https://docs.openstack.org/project-deploy-guide/tripleo-docs/zed/provisioning/node_placement.html21:42
JayFcid has a couple of his first (okay, okay, it's #2 and #3) Ironic changes up for review, https://review.opendev.org/c/openstack/ironic/+/909851 and https://review.opendev.org/c/openstack/ironic/+/910973 -- both are pretty simple reviews if you have a moment :)23:23
JayFthat node_history.user change would be good to get in C, TBH23:23
iurygregoryI probably missed since they weren't with the hashtag, will add to my list23:29
JayFI added ht to at least one of em23:29
JayFbut they weren't V+1 until this morning23:29
iurygregoryack23:29
JayFalso sorta23:29
JayFif there's something at that level we need fixed23:29
iurygregoryI'm checking 85123:29
JayFlet me/cid know and we can line it up23:29
iurygregoryack23:29
JayFhe's basically blown through my planned MLH projects :D 23:29
JayFTheJulia: https://review.opendev.org/c/openstack/ironic/+/901090 needs a rebase now; but I'm unsure if the changes here have already been wrapped in elsewhere; lmk if they are good to land and I can rebase if I'm still workin23:31
opendevreviewJay Faulkner proposed openstack/python-ironicclient master: Fix functional test run  https://review.opendev.org/c/openstack/python-ironicclient/+/90709423:33
TheJuliayeah, a rebase will be needed23:33
JayFI think IPA unit tests might be in pain too23:34
JayFgoing to make a note to look in the morning23:34
JayFhttps://review.opendev.org/c/openstack/ironic/+/900846 needs an added release note, I might make that change today if I have time as well23:35
JayFtrying to get the stragglers in since we gotta cut a release soonish23:36
opendevreviewJay Faulkner proposed openstack/ironic master: Add redfish https boot CI job  https://review.opendev.org/c/openstack/ironic/+/90109023:38
opendevreviewVerification of a change to openstack/ironic-python-agent master failed: Force constraints when installing a package during tox test  https://review.opendev.org/c/openstack/ironic-python-agent/+/90878723:41
opendevreviewJay Faulkner proposed openstack/ironic master: Fix Reopen Web Console Duplicate Sol Session  https://review.opendev.org/c/openstack/ironic/+/90084623:41
JayFI still chose to +2 900846 even though I changed it, it was only a release note. JFYI23:42
JayF901090 I will likely +2 as well, but wanna see CI results (I rebased that one)23:42
opendevreviewVerification of a change to openstack/ironic stable/2023.1 failed: neutron: do not error if no cleaning/provisioning on launch  https://review.opendev.org/c/openstack/ironic/+/91031123:46

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