| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-09-09 | |||
| 16:37:04 | stephenfin | That's the bulk of it | |
| 16:37:14 | stephenfin | (It took ages to load for me too) | |
| 16:37:16 | gibi | bauzas: ahh I see | |
| 16:37:32 | stephenfin | bauzas: What are you thinking? Something AI/GPU-flavoured? | |
| 16:37:39 | gibi | bauzas: showing the latest updates might make sense | |
| 16:37:41 | Uggla | thx stephenfin | |
| 16:37:45 | bauzas | previously we were providing project updates | |
| 16:37:54 | gibi | yeah someting like that^^ | |
| 16:37:56 | bauzas | looks like the pavilion is the new form | |
| 16:38:08 | stephenfin | Ah, nice one | |
| 16:38:23 | bauzas | cool, then that's settled | |
| 16:38:37 | bauzas | and Uggla, will you be at the summit ? | |
| 16:38:46 | Uggla | yes | |
| 16:38:47 | bauzas | fancy co-presenting ? | |
| 16:38:58 | gibi | 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 | bauzas | gibi: that will certainly be part of the project updates :) | |
| 16:39:16 | dansmith | gibi: yeah, definitely | |
| 16:39:24 | Uggla | gibi 👍 | |
| 16:39:35 | dansmith | definitely try to get some people on board for testing and providing feedback | |
| 16:39:43 | Uggla | bauzas, will be happy to copresent with you | |
| 16:40:11 | bauzas | cool, settled as I said | |
| 16:40:12 | gibi | ahh I see it will be in France hence we will have nice representation | |
| 16:40:14 | bauzas | moving on ? | |
| 16:41:04 | Uggla | anything else you want to discuss ? | |
| 16:41:20 | gibi | o/ | |
| 16:41:22 | gibi | pyroute2 | |
| 16:41:39 | Uggla | sure, sorry I was about to forget about it! Thx | |
| 16:42:08 | gibi | so the previous issue about async loops are reproduces with 0.9.4 as well | |
| 16:42:27 | gibi | so the supposed fix wasn't a real fix, it probably decreased the chance of happening | |
| 16:42:54 | gibi | 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 | tkajinam | you mean requirements channel ? | |
| 16:44:01 | gibi | I pinged the release channel I'm not aware of having a separate channel to requirements | |
| 16:44:14 | elodilles | #openstack-requirements o:) | |
| 16:44:20 | tkajinam | yeah | |
| 16:44:26 | sean-k-mooney | gibi: is there a workaround | |
| 16:44:26 | elodilles | but i think i pinged the release folks | |
| 16:44:31 | elodilles | on release channel | |
| 16:44:32 | sean-k-mooney | beyond downgrading | |
| 16:44:46 | gibi | sean-k-mooney: try again and it will succeed | |
| 16:44:56 | elodilles | (yeah, i did ping them) | |
| 16:45:02 | gibi | the issue happens pretty infrequently | |
| 16:45:34 | gibi | https://bugs.launchpad.net/os-vif/+bug/2109396 | |
| 16:45:37 | sean-k-mooney | i guess you could also use the legacy vsctl driver if we have not deleted that yet | |
| 16:45:40 | gibi | this is the bug it has the links | |
| 16:45:55 | sean-k-mooney | oh actully no | |
| 16:46:25 | gibi | I also don't have clear answer if we can revert the requirements | |
| 16:46:28 | gibi | later on stable | |
| 16:46:47 | tkajinam | 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 | tkajinam | I mean I've been struggling to get any feedback in #openstack-requirements | |
| 16:47:25 | gibi | I will drop a mail to the ML | |
| 16:47:26 | sean-k-mooney | gibi: i guess the reals concern with the cap | |
| 16:47:32 | tkajinam | 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 | sean-k-mooney | is has neutron started depending on it | |
| 16:47:39 | sean-k-mooney | and what are distos shiping | |
| 16:48:45 | sean-k-mooney | 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 | gibi | 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 | sean-k-mooney | meaning they likely would not object to the cap? | |
| 16:49:36 | sean-k-mooney | i.e. its impacting them also | |
| 16:49:36 | gibi | I don't want to solve it here. I will drop a mail to ML asking for guidance from requirements team | |
| 16:49:42 | sean-k-mooney | ack | |
| 16:49:49 | gibi | I think they saw it in CI | |
| 16:49:57 | gibi | making interface attach failing | |
| 16:50:14 | gibi | but the failure is during the call from nova | |
| 16:50:22 | gibi | not a call form neutron to os-vif | |
| 16:50:34 | sean-k-mooney | 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 | sean-k-mooney | kind of like we do for powering off cores | |
| 16:50:48 | gibi | sure. I rather want pyroute2 to fix the async code | |
| 16:50:49 | sean-k-mooney | btu i know neutron uses it more widely | |
| 16:51:09 | gibi | anyhow I have nothing further on this | |
| 16:52:17 | 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:53:02 | gibi | 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 | gibi | elodilles: thanks!j | |
| 16:53:54 | elodilles | gibi: thanks too in advance for your mail to ML about this | |
| 16:55:03 | Uggla | good, anything else ? | |
| 16:55:43 | tkajinam | 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 | tkajinam | that's about sateless firmware but I also want to discuss similar problem with sev/sev-es, too | |
| 16:56:45 | sean-k-mooney | i belive we had a similar situration with secure boot before | |
| 16:57:19 | sean-k-mooney | i.e. if you enabel uefi adn dont reqeust secure boto we shoudl not use the SB+SMM one right | |
| 16:57:30 | tkajinam | yeah | |
| 16:57:31 | tkajinam | we have firmware detection logic for secure boot now so I'm wondering if I should follow that pattern. | |
| 16:57:46 | tkajinam | though this means that we may break existing usage with firmware without explicit support declared | |
| 16:58:09 | tkajinam | (I feel like such usage would be anyway broken but want to hear any opinion about it | |
| 16:58:13 | sean-k-mooney | ya i dont have context loaded but i think that would be a good thing to fix eventually | |
| 16:58:36 | tkajinam | this is just for early heads-up | |
| 16:59:16 | sean-k-mooney | we cant rely on libvirt to select it? | |
| 16:59:29 | sean-k-mooney | i vagely recall that being a thing in newer relases | |
| 16:59:29 | tkajinam | we can, though that would be a huge change | |
| 16:59:47 | tkajinam | libvirt is now capable to select a correct firmware with only flags provided | |
| 16:59:47 | sean-k-mooney | ack. that is prbaly the correct long term solution | |
| 17:00:00 | tkajinam | Uggla, I think we can wrap up the call (unless anyone else has additional topics) | |
| 17:00:11 | tkajinam | s/call/meeting/ | |
| 17:01:02 | Uggla | ok time to close. Thanks everyone. | |
| 17:01:09 | opendevmeet | Meeting ended Tue Sep 9 17:01:09 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | |
| 17:01:09 | opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2025/nova.2025-09-09-16.03.html | |
| 17:01:09 | opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2025/nova.2025-09-09-16.03.log.html | |
| 17:01:09 | Uggla | #endmeeting | |
| 17:01:09 | opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2025/nova.2025-09-09-16.03.txt | |
| 17:01:23 | gibi | Uggla: thanks | |
| 17:01:24 | elodilles | thanks o/ | |
| 17:02:04 | tkajinam | thanks ! | |