Tuesday, 2025-09-09

opendevreviewBalazs Gibizer proposed openstack/nova stable/2025.1: Reproduce bug/2115905  https://review.opendev.org/c/openstack/nova/+/96024109:07
opendevreviewBalazs Gibizer proposed openstack/nova stable/2025.1: [PCI tracker]Remove non configured devs when freed  https://review.opendev.org/c/openstack/nova/+/96024209:07
opendevreviewBalazs Gibizer proposed openstack/nova stable/2025.1: [pci]Keep used dev in Placement regardless of dev_spec  https://review.opendev.org/c/openstack/nova/+/96024309:07
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.2: Reproduce bug/2115905  https://review.opendev.org/c/openstack/nova/+/96024409:14
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.2: [PCI tracker]Remove non configured devs when freed  https://review.opendev.org/c/openstack/nova/+/96024509:14
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.2: [pci]Keep used dev in Placement regardless of dev_spec  https://review.opendev.org/c/openstack/nova/+/96024609:14
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.1: Reproduce bug/2115905  https://review.opendev.org/c/openstack/nova/+/96024809:21
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.1: [PCI tracker]Remove non configured devs when freed  https://review.opendev.org/c/openstack/nova/+/96024909:21
opendevreviewBalazs Gibizer proposed openstack/nova stable/2024.1: [pci]Keep used dev in Placement regardless of dev_spec  https://review.opendev.org/c/openstack/nova/+/96025009:21
opendevreviewJohannes Kulik proposed openstack/nova master: api: Pre-query not deleted members in server groups  https://review.opendev.org/c/openstack/nova/+/95969609:41
Uggladansmith, I have seen you point above, would you like to "quickly" discuss about it at PTG ?13:30
dansmithUggla: I would like it fixed right now (i.e. stop forcing edits to my code) and yes, a quick discussion to get agreement that there should always be _some_ way to run the linters in read-only mode might be good13:38
*** benj_6 is now known as benj_13:43
opendevreviewsean mooney proposed openstack/nova master: remove hardcoded in-place config for autopep8  https://review.opendev.org/c/openstack/nova/+/96015014:01
opendevreviewsean mooney proposed openstack/nova master: refactor autopep8 pre-commit config  https://review.opendev.org/c/openstack/nova/+/96016714:01
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013014:22
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013014:26
opendevreviewsean mooney proposed openstack/nova master: Revert "Allow autopep8 to fix more things"  https://review.opendev.org/c/openstack/nova/+/96015014:51
opendevreviewsean mooney proposed openstack/nova master: refactor autopep8 pre-commit config  https://review.opendev.org/c/openstack/nova/+/96016714:51
opendevreviewsean mooney proposed openstack/nova master: renable autopep8 agressive=3  https://review.opendev.org/c/openstack/nova/+/96027414:51
UgglaNova meeting in around 40mn.15:19
bauzaselodilles: just a silly question, can we backport some patch that's merged on master branch in between RC1 and GA  ?15:43
bauzasI mean, can we merge the backport to say Epoxy branch in between RC1 and Flamingo GA?15:44
gibibauzas: thanks for asking!15:46
opendevreviewNell Jerram proposed openstack/nova master: Add managed='no' flag to libvirt XML definition for VIF type TAP  https://review.opendev.org/c/openstack/nova/+/96028415:48
elodillesbauzas: in Flamingo release, the RCs will be published as final release,15:50
bauzasthat, I know15:50
sean-k-mooneybauzas: as far as i am aware we are not ment to unless we are either ok with including them in an RC2 if its requried or we know there will now be one15:50
bauzaslemme give a specific example15:51
sean-k-mooneyif we backport before RC1 is tagged it shoudl be ok however15:51
sean-k-mooneyi.e. before the sabel tbranch is created15:51
elodillesbauzas: that means, that teams can backport bug fixes and if those are release critical, then further RCs can be proposed15:51
opendevreviewNell Jerram proposed openstack/nova master: Add managed='no' flag to libvirt XML definition for VIF type TAP  https://review.opendev.org/c/openstack/nova/+/96028415:51
elodillesbauzas: until Final RC deadline -> https://releases.openstack.org/flamingo/schedule.html15:51
bauzaselodilles: my question is specifically about  https://review.opendev.org/c/openstack/nova/+/96024215:52
elodillesi.e. until week R-115:52
bauzaselodilles: the master patch was merged in master which was Flamingo, this was proposed against Epoxy, can I +W it once we're past RC1 ?15:52
sean-k-mooneythats already merged in master before rc1 is created15:52
bauzascorrect15:52
sean-k-mooneyso it will be in stable/2025.215:53
sean-k-mooneyso i dont see why that cant proceed 15:53
sean-k-mooneythere is no chach of a regression 15:53
bauzasI was thinking we were holding stable approvals on /any/ stable branch during the RC phases, but that's probably me who's overthinking 15:53
sean-k-mooneygoing form 2025.1 to 2025.215:53
sean-k-mooneyunless it has teh poteial to impact grenade i dont hink we need too15:54
sean-k-mooneyso older banches like 2024.2 i think does not require any freeze15:54
elodillesbauzas: you can, but the question is whether it is RC critical, and if not, will it cause trouble when an RC critical issue comes up and an RC2 needs to be proposed15:54
bauzasof course once we branch 2025.2 with RC1, any master patch merged after couldn't be backported to 2025.1 as it would require to be merged first on 2025.2 which is only accepting regression fixes15:54
sean-k-mooneyelodilles: the patch in question was merged on master 4 days ago15:55
sean-k-mooneyhttps://review.opendev.org/c/openstack/nova/+/95461315:55
elodillessean-k-mooney: yes, but i guess bauzas just used it as an example :)15:55
sean-k-mooneyso in this specific example it will be included in rc1 anyway15:55
sean-k-mooneyack15:56
bauzaselodilles: not exactly an example, I'm a stable core and I was about to review that 2025.1 proposal, so I was wondering whether I should/could +W it after Thursday15:56
elodillessean-k-mooney: and of course, as you wrote, too, until RC1 is not merged, and stable/2025.2 branch is not cut, everything will be included from 'master'15:56
elodillesbauzas: i see. so the question is then, if we see that too risky to merge now, just before the flamingo release. we can postpone the backport for later time, when we are over the 2025.2 Flamingo coordinated release15:58
elodillesbauzas: so yes, the best is to keep master (and then stable/2025.2) as stable as possible, and maybe postpone every (risky) backports15:58
sean-k-mooneyim not sure if this woudl be condiered risky for what its worth at least when it comes to posibel impact on the 2025.2 release15:59
elodillesbauzas: as far as i remember you usually said that after RC1 cut stable backports to stable/<current_series> should be avoided to merge, unless they are release critical o:)15:59
sean-k-mooneyyep ^16:00
sean-k-mooneyand the bot patches16:00
elodillesso that is a nice and safe approach :)16:00
sean-k-mooneyits imporant to merge the bot patches including any translation patches that might be propsoed once the stable branhc is created16:01
bauzaselodilles: that's correct yes, that was my thinking but maybe I was overthinking it16:01
elodillessean-k-mooney: yes. as those should be pretty harmless and in fact, needed (but no need for an RC2 if those are the only merged patches on the stable branch)16:02
elodillesbauzas: it's better to be safe than sorry o:)16:03
Uggla#startmeeting nova16:03
opendevmeetMeeting started Tue Sep  9 16:03:44 2025 UTC and is due to finish in 60 minutes.  The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
opendevmeetThe meeting name has been set to 'nova'16:03
UgglaHello everyone16:03
sean-k-mooneyo/16:03
ratailoro/16:04
elodilleso/16:04
dansmitho/16:04
UgglaLet's start16:05
fwieselo/16:05
Uggla#topic Bugs (stuck/critical) 16:05
bauzas\o 16:05
Uggla#info No Critical bug16:05
Uggla#topic Gate status 16:05
Uggla#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:06
gibio/16:06
Uggla#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:06
* gibi is distracted :/16:06
Uggla#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status16:06
Uggla#info Please look at the gate failures and file a bug report with the gate-failure tag.16:06
Uggla#info Please try to provide a meaningful comment when you recheck16:06
UgglaI'm not aware of any issue on the upstream CI. Am I right ?16:07
elodillesmaybe worth to mention osc-placement16:08
sean-k-mooneyoh?16:08
sean-k-mooneyis there somethign we need to adress16:08
elodillestox-functional-py39 job is failing on its master and stable/2025.2 branch16:08
sean-k-mooneyoh16:08
sean-k-mooneyso we shoudl delete that16:08
elodillesi've prepared a patch for that: https://review.opendev.org/q/I7726c99961ef41c7cf5ec71bf28df15eee19187716:08
sean-k-mooneyand make suer we have a 3.12 job instead16:08
sean-k-mooneyah the clinet branches were cut last week16:09
sean-k-mooneyso we need to backport it to 2025.2 as well16:09
elodillessean-k-mooney: exactly16:09
sean-k-mooneysince hte branch already exists16:09
elodillesyes16:09
sean-k-mooneywe already have a 3.12 version fo the job so +216:09
elodillesyes, that too16:10
gibiI'm +216:10
elodillesthanks o/16:10
elodillesthen it should be fine now :]16:10
sean-k-mooneythis is a test only chnage so i dont thinkw e need to do another release right16:10
elodillessean-k-mooney: yes. no need for another release16:10
sean-k-mooney+116:10
sean-k-mooneyanything else for ci?16:11
elodillesnothing from me16:11
sean-k-mooneygibi: you mentioned there was a pyroute2 issues16:11
sean-k-mooneyhas the bump been reverted/capped16:11
sean-k-mooneyor are we waiting on anohter release by the pyroute2 maintainer16:12
* Uggla know that gibi is busy in another call.16:13
sean-k-mooneyah no worries we can move on16:13
sean-k-mooneyhttps://review.opendev.org/c/openstack/requirements/+/957657 might have been the patch16:13
Ugglamaybe, we can come back later to that point later16:13
tkajinamo/16:13
Ugglaskiping next point because gmaan is on pto.16:14
Uggla#topic Release Planning 16:14
Uggla#link https://releases.openstack.org/flamingo/schedule.html16:14
Uggla#info Nova deadlines are set in the above schedule16:14
Uggla#info RC1 target is Thursday.16:14
Uggla#info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg16:14
elodillesand we have the RC1 release patches proposed ;)16:15
Ugglathx elodilles !16:15
elodillesnova: https://review.opendev.org/960103 and placement: https://review.opendev.org/96010816:15
gibi(lets get back to pyroute2 at the end of the meeting)h16:15
Ugglagibi 👍16:15
UgglaDo not forget to register to PTG16:16
Ugglahttps://openinfra.org/ptg/16:16
Uggla#topic Review priorities 16:16
Uggla#link https://etherpad.opendev.org/p/nova-2025.2-status16:16
UgglaThere are bugs listed on the documents.16:17
UgglaBug maybe you should have a look at these 2:16:17
Uggla#link 699176: Faults from cell DB missing in GET /servers/detail | https://review.opendev.org/c/openstack/nova/+/69917616:17
Uggla#link 955657: Preserve vTPM state between power off and power on | https://review.opendev.org/c/openstack/nova/+/95565716:17
Uggla#topic OpenAPI 16:18
Uggla#link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned16:18
Uggla#info still 28 remaining atm.16:18
Uggla#topic Stable Branches16:19
Ugglaelodilles please go ahead.16:19
elodillesthanks16:19
elodilles#info stable/2025.2 branch were cut for nova libraries16:19
elodillesosc-placement is covered already, so skipping that o:)16:19
elodilles #info stable/2025.* and stable/2024.* seem to be in OK state16:20
elodilles#info stable/2025.* and stable/2024.* seem to be in OK state16:20
elodilles#info as soon as nova + placement RC1 patches land, stable/2025.2 branches will be cut for them 16:20
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:20
elodillesthat's all from me about stable, back to you Uggla 16:21
opendevreviewMerged openstack/osc-placement master: [CI] Drop unsupported py39 based functional job  https://review.opendev.org/c/openstack/osc-placement/+/95987316:21
elodilles\o/16:21
Ugglaelodilles, I think only the prelude is missing from a "process" point of view.16:22
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Select appropriate image for stateless firmware  https://review.opendev.org/c/openstack/nova/+/95998816:23
elodillesUggla: yes, i think that's correct16:23
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Select appropriate firmware for stateless firmware  https://review.opendev.org/c/openstack/nova/+/95998816:23
elodillesas cycle highlights have merged16:23
sean-k-mooneyUggla: you proposed that? last week corect or whas that the cycle highlights16:23
UgglaI guess we might still land some bugs too.16:23
elodillesUggla: before RC1?16:24
sean-k-mooneyhttps://review.opendev.org/c/openstack/nova/+/95918816:24
elodillesUggla: because in that case please add a -1 to the RC1 patch so that the release team will wait for an update there16:25
Ugglasean-k-mooney cycle highlights patch was merged, but the prelude is just a "copy" of the highlights.16:25
Ugglaelodilles, I will do it, we discussed a patch I need to check16:26
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Ignore unsupported firmware architectures  https://review.opendev.org/c/openstack/nova/+/95998516:26
elodillesACK, thanks o/16:27
Ugglasean-k-mooney, not sure I answered you question..16:27
sean-k-mooneyUggla: its fine i foudn the review16:27
Ugglasean-k-mooney thx16:27
sean-k-mooneyi see bauzas has a -1 16:27
Uggla#topic vmwareapi 3rd-party CI efforts Highlights16:27
sean-k-mooneybut i have not looked at why16:27
fwiesel#info fwiesel back from PTO16:27
Ugglafwiesel anything you want to discuss ?16:27
fwieselThat's it from my side. Didn't had the time yet to look into anything except my backlog of e-mails.16:28
fwieselUggla: So, back to you16:28
Ugglafwiesel, thx, I just hope you pto were good. ;)16:28
Uggla#topic Gibi's news about eventlet removal.16:29
Uggla#link Blog: https://gibizer.github.io/categories/eventlet/16:29
gibino news16:29
gibior rather no actionable new16:29
gibinews16:29
gibiI'm waiting for master to open for G16:29
Uggla👍16:30
dansmithgibi: I was trying to get my s-g patch set revised yesterday16:30
gibiin the background I'm brewing a rally job that might be able to compare the performance of nova between eventlet and threading16:30
dansmiththe tooling was making that hard, but I'm hoping to be able to get that up soon in G16:30
gibidansmith: cool. I will review when it is up16:30
gibithat is it from me16:31
Ugglathx gibi16:31
Uggla#topic Open discussion 16:31
UgglaI know bauzas wants to discuss about open infra topic.16:32
Ugglabauzas please go ahead.16:32
bauzasnothing important, this was a question whether we would want Nova presence at the OIF Summit pavilion https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/MM4OJO5CCC4GHMYUN3OJBDHTSZNB32H2/16:33
gibiI cannot be there16:35
opendevreviewMerged openstack/osc-placement stable/2025.2: [CI] Drop unsupported py39 based functional job  https://review.opendev.org/c/openstack/osc-placement/+/95987416:35
Ugglabauzas, I don't manage to open the link is it something we could do ?16:36
stephenfinUggla: The OpenInfra Summit 2025 will host an Open Source Pavilion booth space where open source projects can book an hour or two to showcase their work, engage with attendees, and share updates on their latest developments at the Summit. If you are interested in taking advantage of this opportunity for your project please fill out this form [0] and the event planners will get back to you with scheduling details.16:36
bauzasgibi: I'll be there, my question was whether you were wanting me to represent the Nova project16:37
stephenfinThat's the bulk of it16:37
stephenfin(It took ages to load for me too)16:37
gibibauzas: ahh I see16:37
stephenfinbauzas: What are you thinking? Something AI/GPU-flavoured?16:37
gibibauzas: showing the latest updates might make sense16:37
Ugglathx stephenfin16:37
bauzaspreviously we were providing project updates16:37
gibiyeah someting like that^^16:37
bauzaslooks like the pavilion is the new form16:37
stephenfinAh, nice one16:38
bauzascool, then that's settled16:38
bauzasand Uggla, will you be at the summit ?16:38
Ugglayes16:38
bauzasfancy co-presenting ?16:38
gibibauzas: if you could also mention to the folks that we are removing eventlet and ask them to try threading mode and report any issues that would be awesomej16:38
dansmithgibi: yeah, definitely16:39
bauzasgibi: that will certainly be part of the project updates :)16:39
Ugglagibi 👍16:39
dansmithdefinitely try to get some people on board for testing and providing feedback16:39
Ugglabauzas, will be happy to copresent with you16:39
bauzascool, settled as I said16:40
gibiahh I see it will be in France hence we will have nice representation16:40
bauzasmoving on ?16:40
Ugglaanything else you want to discuss ?16:41
gibio/16:41
gibipyroute216:41
Ugglasure, sorry I was about to forget about it! Thx16:41
gibiso the previous issue about async loops are reproduces with 0.9.4 as well 16:42
gibiso the supposed fix wasn't a real fix, it probably decreased the chance of happening16:42
gibiI pinged the release channel asking if we can revert back to 0.8.x so late in the cycle. I got no answers yet16:42
tkajinamyou mean requirements channel ?16:43
gibiI pinged the release channel I'm not aware of having a separate channel to requirements16:44
elodilles#openstack-requirements o:)16:44
tkajinamyeah16:44
elodillesbut i think i pinged the release folks 16:44
sean-k-mooneygibi:  is there a workaround16:44
elodilleson release channel16:44
sean-k-mooneybeyond downgrading16:44
gibisean-k-mooney: try again and it will succeed16:44
elodilles(yeah, i did ping them)16:44
gibithe issue happens pretty infrequently16:45
gibihttps://bugs.launchpad.net/os-vif/+bug/210939616:45
sean-k-mooneyi guess you could also use the legacy vsctl driver if we have not deleted that yet16:45
gibithis is the bug it has the links16:45
sean-k-mooneyoh actully no16:45
gibiI also don't have clear answer if we can revert the requirements 16:46
gibilater on stable16:46
tkajinamthough I've been struggling to get any feedback there. Maybe sending an email to ml would be a good option, hoping that Tony and Sean may be reading it. though I know release team has full +2 access to requirements, too.16:46
tkajinamI mean I've been struggling to get any feedback in #openstack-requirements16:47
gibiI will drop a mail to the ML16:47
sean-k-mooneygibi: i guess the reals concern with the cap16:47
tkajinamfrickler has been the only one there for some time (though he is not a req team member but a release team member)16:47
sean-k-mooneyis has neutron started depending on it16:47
sean-k-mooneyand what are distos shiping16:47
sean-k-mooneyif we cant cap it later we mgith eb able to work around it with a retry in os-vif by cathcing the RuntimeError16:48
gibiat least ykarel is aware of the issue from neutron as he discovered that the issue is happening with 0.9.416:48
sean-k-mooneymeaning they likely would not object to the cap?16:49
gibiI don't want to solve it here. I will drop a mail to ML asking for guidance from requirements team16:49
sean-k-mooneyi.e. its impacting them also16:49
sean-k-mooneyack16:49
gibiI think they saw it in CI16:49
gibimaking interface attach failing16:49
gibibut the failure is during the call from nova16:50
gibinot a call form neutron to os-vif16:50
sean-k-mooneyack well as i said we may be able to catch that excption and retry a limtied number of tiem in os-vif16:50
sean-k-mooneykind of like we do for powering off cores16:50
gibisure. I rather want pyroute2 to fix the async code16:50
sean-k-mooneybtu i know neutron uses it more widely16:50
gibianyhow I have nothing further on this16:51
elodilles(i added this to release team's weekly meeting's agenda for Friday, but i really hope that this will be sorted out until then :S)16:52
gibino worries I think we can go out with Flamingo even if the bug is there. Occasional failures that are fixed by the human retrying is not an end of the world16:53
gibielodilles: thanks!j16:53
elodillesgibi: thanks too in advance for your mail to ML about this16:53
Ugglagood, anything else ?16:55
tkajinamI was wondering if I could get any thoughts for https://bugs.launchpad.net/nova/+bug/2122296 . we don't have enough time and I likely skip the meeting next week but we can discuss it later here or the meeting in 2 weeks16:55
tkajinamthat's about sateless firmware but I also want to discuss similar problem with sev/sev-es, too16:56
sean-k-mooneyi belive we had a similar situration with secure boot before16:56
sean-k-mooneyi.e. if you enabel uefi adn dont reqeust secure boto we shoudl not use the SB+SMM one right16:57
tkajinamyeah16:57
tkajinamwe have firmware detection logic for secure boot now so I'm wondering if I should follow that pattern.16:57
tkajinamthough this means that we may break existing usage with firmware without explicit support declared16:57
tkajinam(I feel like such usage would be anyway broken but want to hear any opinion about it16:58
sean-k-mooneyya i dont have context loaded but i think that would be a good thing to fix eventually16:58
tkajinamthis is just for early heads-up16:58
sean-k-mooneywe cant rely on libvirt to select it?16:59
tkajinamwe can, though that would be a huge change16:59
sean-k-mooneyi vagely recall that being a thing in newer relases16:59
tkajinamlibvirt is now capable to select a correct firmware with only flags provided16:59
sean-k-mooneyack. that is prbaly the correct long term solution16:59
tkajinamUggla, I think we can wrap up the call (unless anyone else has additional topics)17:00
tkajinams/call/meeting/17:00
* gibi is done17:00
Ugglaok time to close. Thanks everyone.17:01
Uggla#endmeeting17:01
opendevmeetMeeting ended Tue Sep  9 17:01:09 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2025/nova.2025-09-09-16.03.html17:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2025/nova.2025-09-09-16.03.txt17:01
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2025/nova.2025-09-09-16.03.log.html17:01
gibiUggla: thanks17:01
elodillesthanks o/17:01
tkajinamthanks !17:02
Ugglayou are welcome17:02
opendevreviewMerged openstack/osc-placement stable/2025.2: Update .gitreview for stable/2025.2  https://review.opendev.org/c/openstack/osc-placement/+/95974417:03
sean-k-mooneyelodilles: just an fyi i have created a watcher release note prelude and will be proposing the cycle hights for it soon. once that is done i think we are also mostly done with watcher release artifacts17:06
sean-k-mooneyelodilles: my hope is to have those both merged before rc1 is created on thursday17:06
gibiUggla: FYI I've just approved https://review.opendev.org/c/openstack/nova/+/959604 As I consider the content to be safe to land close to RC1. We have extensive discussion about the solution on IRC last week17:08
gibis/have/had/17:09
Ugglagibi, thx and sorry for the mistake in the meeting. :)17:09
gibiUggla: no worries17:10
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013017:13
opendevreviewMerged openstack/osc-placement stable/2025.2: Update TOX_CONSTRAINTS_FILE for stable/2025.2  https://review.opendev.org/c/openstack/osc-placement/+/95974517:15
opendevreviewNell Jerram proposed openstack/nova master: Add managed='no' flag to libvirt XML definition for VIF type TAP  https://review.opendev.org/c/openstack/nova/+/96028417:18
opendevreviewStephen Finucane proposed openstack/nova master: setup: Remove pbr's wsgi_scripts  https://review.opendev.org/c/openstack/nova/+/90268817:19
opendevreviewStephen Finucane proposed openstack/nova master: Migrate mypy configuration to pyproject.toml  https://review.opendev.org/c/openstack/nova/+/95370317:19
opendevreviewStephen Finucane proposed openstack/nova master: Migrate codespell configuration to pyproject.toml  https://review.opendev.org/c/openstack/nova/+/95370417:19
opendevreviewStephen Finucane proposed openstack/nova master: Migrate setup configuration to pyproject.toml  https://review.opendev.org/c/openstack/nova/+/95370517:19
opendevreviewTakashi Kajinami proposed openstack/nova master: Update libvirt version support matrix for Flamingo  https://review.opendev.org/c/openstack/nova/+/96030117:25
opendevreviewTakashi Kajinami proposed openstack/nova master: docs: Update libvirt version support matrix for Flamingo  https://review.opendev.org/c/openstack/nova/+/96030117:25
tkajinam^^^ this might be worth merging before rc117:25
* tkajinam is double-checking code-name of 2025.217:26
elodillessean-k-mooney: ACK, will check those tomorrow, thanks for the heads up o/19:12

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