14:00:26 <haleyb> #startmeeting networking
14:00:26 <opendevmeet> Meeting started Tue Apr  1 14:00:26 2025 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:26 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:26 <opendevmeet> The meeting name has been set to 'networking'
14:00:33 <haleyb> Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh
14:00:34 <mlavalle> \o
14:00:43 <ykarel> o/
14:00:45 <elvira> o/
14:00:46 <ralonsoh> sorry, in a meeting now
14:00:50 <frickler> \o
14:01:08 <slaweq> o/
14:01:37 <mtomaska1> o/
14:02:09 <haleyb> #announcements
14:02:26 <haleyb> We are currently in week R-0 of Epoxy
14:02:34 <bcafarel> o/
14:02:35 <haleyb> Final 2025.1 Epoxy release: April 2nd, 2025
14:02:46 <haleyb> RC2 release will be Epoxy final
14:02:47 <rubasov> o/
14:02:57 <lajoskatona> o/
14:03:16 * frickler is already flexing the trigger finger ;)
14:03:18 <haleyb> So there was much rejoicing!
14:03:59 <mlavalle> +1
14:04:00 <lajoskatona> \o/
14:04:34 <haleyb> Project Teams Gathering (virtual): April 7th-11th, 2025 - next week
14:04:45 <haleyb> #link https://ptg.openinfra.dev/ to sign up if you haven't
14:04:51 <haleyb> #link https://etherpad.opendev.org/p/apr2025-ptg-neutron
14:04:57 <haleyb> #link https://ptg.opendev.org/ptg.html for room assignments
14:05:06 <haleyb> I added two slots Tuesday, 4 on Wednesday and Thursday
14:05:13 <haleyb> please add topics to the etherpad, i plan to add any RFE topics to that thursday
14:05:57 <haleyb> we will have a cross-project with nova (and hopefully cinder) on thursday 13:00 to discuss a QoS RFE proposal
14:06:08 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2102184
14:06:16 <haleyb> that was the only planned cross-project
14:06:56 <haleyb> actually, there is another short one with nova right after on vif plugging, i'll get the schedule finalized later this week
14:07:46 <haleyb> I think the only thing we are still waiting to finalize is the job templates for 2025.2 (master)
14:07:54 <haleyb> #link https://review.opendev.org/c/openstack/neutron/+/944809/
14:08:10 <haleyb> it is waiting on a zuul-jobs change to merge
14:08:28 <haleyb> but essentially Flamingo is open for business
14:09:05 <haleyb> any other comments on Epoxy for Flamingo?
14:09:24 <haleyb> ok
14:09:42 <frickler> oh, I wasn't aware that that change is still open
14:09:49 <frickler> will ping elodille1
14:10:01 <haleyb> #link https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/941246
14:10:25 <frickler> ack
14:10:33 <haleyb> i think it actually needs a change based on my -1 :(
14:10:43 <haleyb> or maybe not, need confirmation
14:10:59 <frickler> yes, but all relevant projects should be branched by now, so no need to wait for tomorrow
14:11:26 <haleyb> no, and i'm guessing the release patch merged, i'm just coming online so have not looked
14:12:15 <haleyb> My other comment/question was about this meeting time
14:12:22 <frickler> actual release is tomorrow, if you refer to that
14:12:47 <haleyb> ack, thought i saw one +2
14:13:53 <frickler> only +1s and one misled -1 afaict, but nevermind
14:13:54 <haleyb> With the time change in the US I started having conflicts, and i've been unable to move other things, i'm actually in another meeting as i type this
14:14:43 <haleyb> Would people be able to move this one hour earlier, until at least October when the time will change again?
14:14:54 <frickler> +1
14:15:06 <lajoskatona> For me it can work
14:15:11 <haleyb> so to 13:00 UTC
14:15:16 <lajoskatona> +1 for -1 hour
14:15:27 <ykarel> +1
14:15:45 <slaweq> sounds good for me
14:16:46 <haleyb> ok, i will send a review out (i think that's how we change that) and an email to the list since someone might not be here
14:16:50 <mlavalle> I prefer this time
14:17:02 <mlavalle> but can live with 1300utc
14:17:56 <mlavalle> haleyb: what happens when we go back to standard time?
14:18:09 <frickler> https://opendev.org/opendev/irc-meetings/src/branch/master/meetings/neutron-team-meeting.yaml is the file to change
14:18:16 <mlavalle> at that moment it is going to be too early for me
14:18:38 <haleyb> mlavalle: i would want to move it back to 14:00 when we change times
14:18:46 <mlavalle> +1
14:18:50 <mlavalle> sound good
14:19:07 <haleyb> the other option would be to move it later to 15:00
14:19:08 <frickler> we've been doing a similar thing for the kolla meeting for years now, maybe time to implement that in code
14:19:44 <slaweq> please don't move it 1h later then it is now, it is a bit late for me
14:19:48 <haleyb> or even 14:30
14:20:07 <mlavalle> I'm also fina with that option, but is would be too late for our European friends
14:20:53 <haleyb> slaweq: that's what i figured. 14:00 seems to be limit
14:21:15 <lajoskatona> 1300UTC summertime is good for me, but perhaps 1400 UTC for winter is also good as I see my calendar for autumn
14:21:29 <haleyb> and it also works for the around-the-world timezone meeting i'm in weekly with a guy in NZ
14:21:45 <mlavalle> 1300utc during DST and 1400utc during standard time seems to be a good middle groud
14:22:37 <slaweq> haleyb yes,for me it is the best if it is 1400 or earlier
14:22:46 <haleyb> mlavalle: ack, that i think works, i will propose, don't know if there's a way to represent that in the meeting wiki but i'll see
14:23:40 <haleyb> alright, that's all i had for announcement, anyone else?
14:23:44 <frickler> currently you'll have to submit a patch to change it every 6 months. but adding code to represent that changing UTC time automatically might be a nice idea
14:24:53 <haleyb> frickler: ack, i'll at least put it in the wiki that it moves spring and fall
14:25:09 <haleyb> or is it still winter? i have no idea
14:25:28 <frickler> US might be winter, EU in spring
14:25:56 <frickler> will always be a comprise when to switch exactly. for both directions
14:26:07 <frickler> compromise even
14:26:48 <haleyb> understood, and the other downstream meetings we have are always changing as well
14:27:14 <haleyb> ok, we can move on to bugs
14:27:17 <haleyb> #topic bugs
14:27:25 <haleyb> obondarev was the deputy last week
14:27:29 <haleyb> his report is at
14:27:36 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/KZN4GRCJMNSUOD652GYE3JEY2L5LLUG7/
14:28:09 <haleyb> first one
14:28:18 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2104019
14:28:19 <haleyb> random failures in L3 HA fullstack failover tests
14:28:25 <haleyb> mlavalle: i see you took this one
14:28:58 <mlavalle> I did yes
14:29:06 <mlavalle> I'll keep an eye on it
14:29:29 <haleyb> ack, thanks for taking
14:29:54 <haleyb> next is
14:30:00 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2104134
14:30:06 <haleyb> ovs/linuxbridge jobs running on ubuntu noble broken with latest kernel 6.8.0-56.58
14:30:53 <haleyb> this was worked-around by removing the bad image
14:31:30 <haleyb> new kernel should be released week of April 14th, we pinged about speeding that up
14:32:24 <haleyb> but i think we're good for now and nothing we can fix in neutron without a modprode hack somewhere
14:32:58 <haleyb> next
14:33:10 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2104160
14:33:11 <haleyb> [DB] Stop expand migrations with field drop exceptions
14:33:21 <frickler> well you are good, but infra stopped building noble images, so any speedup would still be fine (for prev bug)
14:34:37 <haleyb> frickler: we pushed in our matrix channel, but did not get a definitive answer, but they were unaware it broke openstack CI
14:34:59 <frickler> not only neutron, but also kolla, if that matters
14:35:42 <haleyb> ack
14:36:36 <haleyb> regarding the DB migration bug, will wait for ralonsoh to comment, or maybe can discuss at PTG
14:37:48 <haleyb> next one
14:37:59 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2104979
14:38:00 <haleyb> Possible deadlock on closing ip_monitor thread.
14:38:16 <haleyb> i see there was a patch just proposed
14:38:22 <haleyb> #link https://review.opendev.org/c/openstack/neutron/+/946028
14:38:58 <haleyb> so we can comment there
14:39:00 <haleyb> and last one
14:39:12 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2104037
14:39:14 <haleyb> Unable to open stream to ssl::6641 to retrieve schema: Exec format error
14:40:06 <frickler> is ommitting the host IP allowed? wasn't sure from the docs
14:40:45 <frickler> but might also be a container arch issue. anyway more info needed
14:41:16 <haleyb> frickler: no, you need something there i believe
14:41:52 <haleyb> ssl:127.0.0.1:6641
14:42:12 <haleyb> i will add comment
14:42:32 <frickler> so it might be good for neutron to check that and raise a config error earlier
14:43:23 <lajoskatona> isnt't that parsed to ipv6 perhaps?
14:44:01 <lajoskatona> but perhaps that can be filtered in config read time also
14:44:24 <frickler> the first : should be parsed as separator and ":6641" isn't valid v6 either
14:44:52 <lajoskatona> frickler: ack
14:45:35 <haleyb> i thought we would have thrown OvsdbConnectionUnavailable which would print an error but it might be later in startup
14:46:52 <haleyb> we did just add a regex to make sure tcp/ssl/unix was given
14:47:36 <haleyb> either way, i don't think it's a neutron bug, but we can maybe make it clearer what's broken
14:47:52 <haleyb> any more bugs to discuss?
14:48:26 <haleyb> #topic community goals
14:49:03 <haleyb> since ralonsoh is in another meeting can skip eventlet update, unless someone else has one on it?
14:49:15 <ralonsoh> just the question about the L3 migration
14:49:32 <ralonsoh> I implemented a thread handler with resizable workers
14:49:40 <ralonsoh> but there are concerns about its usage
14:49:54 <ralonsoh> so the other proposal is to remnove the L3 agent resizable pool
14:50:08 <ralonsoh> https://review.opendev.org/c/openstack/neutron/+/938411
14:50:22 <ralonsoh> please, any idea or comment, you can do it here
14:50:34 <ralonsoh> IMO, at this point of the cycle (starting)
14:50:38 <ralonsoh> we can use this new class
14:50:42 <ralonsoh> https://review.opendev.org/c/openstack/neutron/+/945566
14:51:13 <ralonsoh> sorry, I need to leave. Feel free to comment ^^^
14:51:17 <ralonsoh> I'll do the same
14:51:35 <haleyb> ralonsoh: ack, will look and comment in reviews
14:52:15 <haleyb> any other community goals topics?
14:52:27 <haleyb> #topic on-demand
14:52:47 <haleyb> anything else? now is your time :)
14:53:31 <lajoskatona> perhaps this one: https://review.opendev.org/c/openstack/neutron/+/861169
14:53:43 <lajoskatona> this is for device_id in ports
14:54:12 <lajoskatona> I think we discussed it earlier, but please check it, and check the Nova patch also on which this one depends
14:54:14 <haleyb> just one reminder that there is no drivers meeting this week, and next week is PTG - so add any topics to the etherpad
14:54:50 <lajoskatona> this is for service user for inter project APIs
14:55:15 <slaweq> thx lajoskatona, I will check that patch
14:55:50 <lajoskatona> thanks
14:55:59 <haleyb> ok, thanks for attending everyone, see you online next week (and i'll be on time this PTG :)
14:56:16 <haleyb> #endmeeting