16:03:44 #startmeeting nova 16:03:44 Meeting 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:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:03:44 The meeting name has been set to 'nova' 16:03:53 Hello everyone 16:03:56 o/ 16:04:00 o/ 16:04:04 o/ 16:04:53 o/ 16:05:24 Let's start 16:05:31 o/ 16:05:36 #topic Bugs (stuck/critical) 16:05:43 \o 16:05:43 #info No Critical bug 16:05:54 #topic Gate status 16:06:00 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:06:07 o/ 16:06:10 #link https://etherpad.opendev.org/p/nova-ci-failures-minimal 16:06:13 * gibi is distracted :/ 16:06:20 #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 status 16:06:28 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:06:37 #info Please try to provide a meaningful comment when you recheck 16:07:39 I'm not aware of any issue on the upstream CI. Am I right ? 16:08:03 maybe worth to mention osc-placement 16:08:20 oh? 16:08:26 is there somethign we need to adress 16:08:30 tox-functional-py39 job is failing on its master and stable/2025.2 branch 16:08:36 oh 16:08:39 so we shoudl delete that 16:08:43 i've prepared a patch for that: https://review.opendev.org/q/I7726c99961ef41c7cf5ec71bf28df15eee191877 16:08:48 and make suer we have a 3.12 job instead 16:09:10 ah the clinet branches were cut last week 16:09:17 so we need to backport it to 2025.2 as well 16:09:21 sean-k-mooney: exactly 16:09:23 since hte branch already exists 16:09:28 yes 16:09:53 we already have a 3.12 version fo the job so +2 16:10:00 yes, that too 16:10:03 I'm +2 16:10:07 thanks o/ 16:10:16 then it should be fine now :] 16:10:21 this is a test only chnage so i dont thinkw e need to do another release right 16:10:42 sean-k-mooney: yes. no need for another release 16:10:47 +1 16:11:11 anything else for ci? 16:11:20 nothing from me 16:11:24 gibi: you mentioned there was a pyroute2 issues 16:11:57 has the bump been reverted/capped 16:12:10 or are we waiting on anohter release by the pyroute2 maintainer 16:13:01 * Uggla know that gibi is busy in another call. 16:13:17 ah no worries we can move on 16:13:29 https://review.opendev.org/c/openstack/requirements/+/957657 might have been the patch 16:13:48 maybe, we can come back later to that point later 16:13:48 o/ 16:14:13 skiping next point because gmaan is on pto. 16:14:21 #topic Release Planning 16:14:30 #link https://releases.openstack.org/flamingo/schedule.html 16:14:37 #info Nova deadlines are set in the above schedule 16:14:43 #info RC1 target is Thursday. 16:14:49 #info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg 16:15:02 and we have the RC1 release patches proposed ;) 16:15:23 thx elodilles ! 16:15:24 nova: https://review.opendev.org/960103 and placement: https://review.opendev.org/960108 16:15:35 (lets get back to pyroute2 at the end of the meeting)h 16:15:46 gibi 👍 16:16:04 Do not forget to register to PTG 16:16:34 https://openinfra.org/ptg/ 16:16:46 #topic Review priorities 16:16:56 #link https://etherpad.opendev.org/p/nova-2025.2-status 16:17:23 There are bugs listed on the documents. 16:17:44 Bug maybe you should have a look at these 2: 16:17:46 #link 699176: Faults from cell DB missing in GET /servers/detail | https://review.opendev.org/c/openstack/nova/+/699176 16:17:53 #link 955657: Preserve vTPM state between power off and power on | https://review.opendev.org/c/openstack/nova/+/955657 16:18:22 #topic OpenAPI 16:18:30 #link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned 16:18:36 #info still 28 remaining atm. 16:19:24 #topic Stable Branches 16:19:35 elodilles please go ahead. 16:19:38 thanks 16:19:42 #info stable/2025.2 branch were cut for nova libraries 16:19:58 osc-placement is covered already, so skipping that o:) 16:20:17 #info stable/2025.* and stable/2024.* seem to be in OK state 16:20:22 #info stable/2025.* and stable/2024.* seem to be in OK state 16:20:37 #info as soon as nova + placement RC1 patches land, stable/2025.2 branches will be cut for them 16:20:45 #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci 16:21:10 that's all from me about stable, back to you Uggla 16:21:37 Merged openstack/osc-placement master: [CI] Drop unsupported py39 based functional job https://review.opendev.org/c/openstack/osc-placement/+/959873 16:21:49 \o/ 16:22:54 elodilles, I think only the prelude is missing from a "process" point of view. 16:23:13 Takashi Kajinami proposed openstack/nova master: libvirt: Select appropriate image for stateless firmware https://review.opendev.org/c/openstack/nova/+/959988 16:23:26 Uggla: yes, i think that's correct 16:23:40 Takashi Kajinami proposed openstack/nova master: libvirt: Select appropriate firmware for stateless firmware https://review.opendev.org/c/openstack/nova/+/959988 16:23:42 as cycle highlights have merged 16:23:50 Uggla: you proposed that? last week corect or whas that the cycle highlights 16:23:53 I guess we might still land some bugs too. 16:24:23 Uggla: before RC1? 16:24:30 https://review.opendev.org/c/openstack/nova/+/959188 16:25:20 Uggla: because in that case please add a -1 to the RC1 patch so that the release team will wait for an update there 16:25:52 sean-k-mooney cycle highlights patch was merged, but the prelude is just a "copy" of the highlights. 16:26:38 elodilles, I will do it, we discussed a patch I need to check 16:26:59 Takashi Kajinami proposed openstack/nova master: libvirt: Ignore unsupported firmware architectures https://review.opendev.org/c/openstack/nova/+/959985 16:27:01 ACK, thanks o/ 16:27:03 sean-k-mooney, not sure I answered you question.. 16:27:16 Uggla: its fine i foudn the review 16:27:26 sean-k-mooney thx 16:27:31 i see bauzas has a -1 16:27:34 #topic vmwareapi 3rd-party CI efforts Highlights 16:27:36 but i have not looked at why 16:27:45 #info fwiesel back from PTO 16:27:58 fwiesel anything you want to discuss ? 16:28:09 That's it from my side. Didn't had the time yet to look into anything except my backlog of e-mails. 16:28:39 Uggla: So, back to you 16:28:40 fwiesel, thx, I just hope you pto were good. ;) 16:29:12 #topic Gibi's news about eventlet removal. 16:29:20 #link Blog: https://gibizer.github.io/categories/eventlet/ 16:29:23 no news 16:29:37 or rather no actionable new 16:29:39 news 16:29:45 I'm waiting for master to open for G 16:30:01 👍 16:30:09 gibi: I was trying to get my s-g patch set revised yesterday 16:30:09 in the background I'm brewing a rally job that might be able to compare the performance of nova between eventlet and threading 16:30:17 the tooling was making that hard, but I'm hoping to be able to get that up soon in G 16:30:29 dansmith: cool. I will review when it is up 16:31:02 that is it from me 16:31:32 thx gibi 16:31:41 #topic Open discussion 16:32:09 I know bauzas wants to discuss about open infra topic. 16:32:16 bauzas please go ahead. 16:33:05 nothing 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:35:14 I cannot be there 16:35:43 Merged openstack/osc-placement stable/2025.2: [CI] Drop unsupported py39 based functional job https://review.opendev.org/c/openstack/osc-placement/+/959874 16:36:37 bauzas, I don't manage to open the link is it something we could do ? 16:36:59 Uggla: 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:37:00 gibi: I'll be there, my question was whether you were wanting me to represent the Nova project 16:37:04 That's the bulk of it 16:37:14 (It took ages to load for me too) 16:37:16 bauzas: ahh I see 16:37:32 bauzas: What are you thinking? Something AI/GPU-flavoured? 16:37:39 bauzas: showing the latest updates might make sense 16:37:41 thx stephenfin 16:37:45 previously we were providing project updates 16:37:54 yeah someting like that^^ 16:37:56 looks like the pavilion is the new form 16:38:08 Ah, nice one 16:38:22 cool, then that's settled 16:38:37 and Uggla, will you be at the summit ? 16:38:46 yes 16:38:47 fancy co-presenting ? 16:38:58 bauzas: 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 awesomej 16:39:16 gibi: yeah, definitely 16:39:16 gibi: that will certainly be part of the project updates :) 16:39:24 gibi 👍 16:39:35 definitely try to get some people on board for testing and providing feedback 16:39:43 bauzas, will be happy to copresent with you 16:40:11 cool, settled as I said 16:40:12 ahh I see it will be in France hence we will have nice representation 16:40:14 moving on ? 16:41:04 anything else you want to discuss ? 16:41:20 o/ 16:41:22 pyroute2 16:41:39 sure, sorry I was about to forget about it! Thx 16:42:08 so the previous issue about async loops are reproduces with 0.9.4 as well 16:42:27 so the supposed fix wasn't a real fix, it probably decreased the chance of happening 16:42:54 I pinged the release channel asking if we can revert back to 0.8.x so late in the cycle. I got no answers yet 16:43:19 you mean requirements channel ? 16:44:01 I pinged the release channel I'm not aware of having a separate channel to requirements 16:44:14 #openstack-requirements o:) 16:44:20 yeah 16:44:26 but i think i pinged the release folks 16:44:26 gibi: is there a workaround 16:44:31 on release channel 16:44:32 beyond downgrading 16:44:46 sean-k-mooney: try again and it will succeed 16:44:56 (yeah, i did ping them) 16:45:02 the issue happens pretty infrequently 16:45:34 https://bugs.launchpad.net/os-vif/+bug/2109396 16:45:37 i guess you could also use the legacy vsctl driver if we have not deleted that yet 16:45:40 this is the bug it has the links 16:45:55 oh actully no 16:46:25 I also don't have clear answer if we can revert the requirements 16:46:28 later on stable 16:46:47 though 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:47:03 I mean I've been struggling to get any feedback in #openstack-requirements 16:47:25 I will drop a mail to the ML 16:47:26 gibi: i guess the reals concern with the cap 16:47:32 frickler has been the only one there for some time (though he is not a req team member but a release team member) 16:47:34 is has neutron started depending on it 16:47:39 and what are distos shiping 16:48:45 if we cant cap it later we mgith eb able to work around it with a retry in os-vif by cathcing the RuntimeError 16:48:52 at least ykarel is aware of the issue from neutron as he discovered that the issue is happening with 0.9.4 16:49:22 meaning they likely would not object to the cap? 16:49:36 I don't want to solve it here. I will drop a mail to ML asking for guidance from requirements team 16:49:36 i.e. its impacting them also 16:49:42 ack 16:49:49 I think they saw it in CI 16:49:57 making interface attach failing 16:50:14 but the failure is during the call from nova 16:50:22 not a call form neutron to os-vif 16:50:34 ack well as i said we may be able to catch that excption and retry a limtied number of tiem in os-vif 16:50:43 kind of like we do for powering off cores 16:50:48 sure. I rather want pyroute2 to fix the async code 16:50:49 btu i know neutron uses it more widely 16:51:09 anyhow I have nothing further on this 16:52:17 (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:53:02 no 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 world 16:53:27 elodilles: thanks!j 16:53:54 gibi: thanks too in advance for your mail to ML about this 16:55:03 good, anything else ? 16:55:43 I 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 weeks 16:56:20 that's about sateless firmware but I also want to discuss similar problem with sev/sev-es, too 16:56:45 i belive we had a similar situration with secure boot before 16:57:19 i.e. if you enabel uefi adn dont reqeust secure boto we shoudl not use the SB+SMM one right 16:57:30 yeah 16:57:31 we have firmware detection logic for secure boot now so I'm wondering if I should follow that pattern. 16:57:46 though this means that we may break existing usage with firmware without explicit support declared 16:58:09 (I feel like such usage would be anyway broken but want to hear any opinion about it 16:58:13 ya i dont have context loaded but i think that would be a good thing to fix eventually 16:58:36 this is just for early heads-up 16:59:16 we cant rely on libvirt to select it? 16:59:29 we can, though that would be a huge change 16:59:29 i vagely recall that being a thing in newer relases 16:59:47 libvirt is now capable to select a correct firmware with only flags provided 16:59:47 ack. that is prbaly the correct long term solution 17:00:00 Uggla, I think we can wrap up the call (unless anyone else has additional topics) 17:00:11 s/call/meeting/ 17:00:25 * gibi is done 17:01:02 ok time to close. Thanks everyone. 17:01:09 #endmeeting