14:00:28 <haleyb> #startmeeting networking
14:00:28 <opendevmeet> Meeting started Tue Mar 11 14:00:28 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:28 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:28 <opendevmeet> The meeting name has been set to 'networking'
14:00:31 <haleyb> Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, haleyb, ralonsoh
14:00:32 <mlavalle> \o
14:00:42 <frickler> \o
14:00:43 <ykarel> o/
14:00:45 <slaweq> o/
14:00:56 <cbuggy> o/
14:01:11 <lajoskatona> o/
14:01:18 <rubasov> o/
14:01:21 <ralonsoh> hello
14:01:23 <haleyb> hi everyone
14:01:36 <haleyb> #announcements
14:01:45 <haleyb> We are currently in week R-3 of Epoxy
14:02:26 <haleyb> RC1 release proposals have been proposed
14:02:35 <elvira> o/
14:02:36 <haleyb> i have not looked at any yet
14:02:51 <haleyb> All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2025.1 branch will be cut. This branch will track the 2025.1 Epoxy release.
14:03:06 <haleyb> Once stable/2025.1 has been created, the master branch will be ready to switch to 2025.2 Flamingo development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2025.1 Epoxy plans.  Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2025.1 branch before a new release candidate can be proposed.
14:03:55 <haleyb> So we need to take a look at any patches in-flight and get them merged, then update the release patch
14:04:03 <haleyb> RC1 deadline: March 14th, 2025
14:04:16 <bcafarel> late o/
14:04:16 <haleyb> Final RC deadline: March 28th, 2025
14:04:25 <haleyb> Final 2025.1 Epoxy release: April 2nd, 2025
14:05:31 <haleyb> So please ping me with any patches that should merge, and set priority so they appear in the dashboard
14:06:11 <lajoskatona> +1
14:06:14 <slaweq> haleyb I think I may have one
14:06:23 <slaweq> https://review.opendev.org/c/openstack/neutron/+/944022
14:07:04 <ralonsoh> let's raise the priority to +2 to those patches that should land this week
14:07:08 <ralonsoh> I have another bug fix too
14:07:09 <haleyb> slaweq: +1, will start watching
14:07:39 <slaweq> thx
14:07:53 <haleyb> ralonsoh: yes, RP +2 is a good idea
14:08:33 <slaweq> I just set it for my patch
14:08:35 <haleyb> Project Teams Gathering (virtual): April 7th-11th, 2025
14:08:48 <haleyb> #link https://ptg.openinfra.dev/ to sign up
14:08:49 <slaweq> and I will address ralonsoh's comments just after this meeting
14:09:00 <haleyb> April 7-11, 2025, 13:00-17:00 UTC, Full virtual
14:09:14 <haleyb> #link https://etherpad.opendev.org/p/apr2025-ptg-neutron
14:09:24 <ralonsoh> ^ thanks!
14:09:25 <haleyb> please add topics there
14:09:34 <lajoskatona> thanks
14:10:11 <haleyb> like last time, i will sign-up for tue/wed/thur slots, we have not needed friday in a couple of meetings
14:10:29 <haleyb> i'm assuming monday is for TC, etc
14:10:37 <ralonsoh> and operator hours?
14:11:02 <slaweq> monday usually is for the TC & community leaders session
14:11:05 <haleyb> #link https://ptg.opendev.org/ptg.html
14:11:15 <slaweq> TC meetings are usually Thursday and Friday
14:11:19 <haleyb> not very much there yet
14:11:57 <haleyb> i do see eventlet on tuesday 14:00 and 15:00 UTC so will avoid that time as well
14:13:28 <haleyb> that's all i had on ptg and announcements, any others?
14:13:48 <haleyb> slaweq: i see TC on friday as well now
14:13:55 <haleyb> so monday and friday
14:14:02 <slaweq> could be
14:14:19 <slaweq> I am not in the TC anymore so I am not tracking it closely this time :)
14:14:20 <haleyb> that link ^^ is the source of truth
14:14:24 <haleyb> :)
14:15:15 <haleyb> Reminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers
14:15:25 <haleyb> i will look later this week
14:16:00 <haleyb> #topic bugs
14:16:06 <haleyb> rubasov was the deputy last week
14:16:13 <haleyb> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/RBDODEDOWWLFMQKLSO2SEAPENMU2WGE3/
14:16:38 <haleyb> there were a number of gate failures reported
14:17:06 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2100776
14:17:13 <haleyb> test_securitygroup(ovs-openflow) fullstack test random failure with Time out exception
14:17:24 <haleyb> not sure if any were discussed at yesterday's CI meeting
14:17:41 <ralonsoh> yes it was but just to report it
14:17:49 <haleyb> ack
14:18:22 <haleyb> that one needs an owner, comment that it could be similar to https://bugs.launchpad.net/neutron/+bug/1871908
14:18:51 <haleyb> another was
14:18:55 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2101165
14:19:01 <haleyb> Random failure in test_established_tcp_session_after_re_attachinging_sg
14:19:24 <ralonsoh> yes, this is failing both in ovn and ovs
14:19:52 <ralonsoh> could be a test issue implementation too
14:21:25 <haleyb> ack, that one needs an owner as well
14:22:14 <haleyb> and another gate failure
14:22:18 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2101166
14:22:27 <haleyb> Random failure in dvr ovs grenade jobs to ping vm post upgrade
14:23:06 <haleyb> that's always in the ovs dvr grenade multinode job
14:24:17 <haleyb> ykarel: were those all discussed in CI meeting or just reported?
14:25:04 <ykarel> haleyb, yes just briefly discussed and reported
14:25:58 <haleyb> ack, would be good to get owners to try and track some of those down, otherwise recheck; recheck; recheck :(
14:26:38 <ralonsoh> I try with the ovs dvr one
14:26:48 <ralonsoh> it seems that we don't have dhcp
14:27:08 <lajoskatona> perhaps this last grenade failure isrealted to https://bugs.launchpad.net/neutron/+bug/2101840
14:27:19 <haleyb> ralonsoh: thanks
14:27:22 <lajoskatona> and perhaps to the eventlet removal
14:27:38 <ralonsoh> lajoskatona, could be, let's sync after the meeting
14:27:48 <lajoskatona> ack
14:28:02 <haleyb> there was one more gate bug
14:28:09 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2100806
14:28:16 <haleyb> Intermittent test_batch_notifier failure
14:28:27 <haleyb> i picked this up and proposed a patch
14:28:50 <haleyb> ralonsoh: i was just writing a response before meeting, we can discuss there or i'll ping you after meeting
14:29:10 <ralonsoh> sure, after the meeting. I think we discussed it last week
14:30:03 <haleyb> ralonsoh: right, more discuss about the change, changing the sleeps wasn't as i expected
14:31:10 <haleyb> i'm just checking the rest of the bugs, most have owners
14:32:15 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2101077
14:32:16 <rubasov> I'll get back to see if I can reproduce this: https://bugs.launchpad.net/neutron/+bug/2101077
14:32:22 <haleyb> neutron-bgp-agent dies with debug log + json
14:32:41 <rubasov> just got some info yesterday
14:32:46 <haleyb> rubasov: ack, thanks
14:33:14 <haleyb> last one is
14:33:18 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2100752
14:33:24 <haleyb> Severe Packet Loss During Live Migration Due to Premature Route Advertisement in Neutron BGP Dynamic Routing
14:34:09 <haleyb> looks like lajoskatona had some thoughts on that one
14:34:25 <lajoskatona> I just checked the code to tell the truth
14:34:55 <rubasov> that one seems real, I think it cannot be made perfect, but it is likely possible to improve the timing
14:35:05 <rubasov> mostly based on what Lajos looked into
14:35:09 <lajoskatona> but based on that it seems valid bug, and with some extra conditions to the plugin.py for port_update callback it could be ok
14:35:26 <lajoskatona> yes exact as rubasov said
14:35:41 <lajoskatona> s/exact/exactly/
14:37:16 <lajoskatona> if the reporter can work on it that would be perfect :-)
14:37:18 <haleyb> ack, is anyone actually doing active development on that repo to take this? it doesn't look like it based on past changes
14:37:33 <haleyb> lajoskatona: yes, that would be best
14:39:03 <haleyb> ok, well make a comment in the bug regarding possible fix if you can, and see if submitter can take
14:39:17 <lajoskatona> +1
14:39:27 <haleyb> any other bugs people want to discuss?
14:40:11 <haleyb> looking at the calendar, this week mlavalle is deputy, next week is jlibosva
14:40:15 <mlavalle> on it since yesterday
14:40:33 <haleyb> mlavalle: woohoo! :)
14:41:08 <haleyb> ok, moving on
14:41:11 <haleyb> #topic community goals
14:41:34 <haleyb> lajoskatona: i see one of the neutronclient horizon changes was pushed into the gate, don't know if it merged, but progress
14:41:48 <lajoskatona> all merged this morning after few rechecks :-)
14:41:58 <lajoskatona> so I have to go back and do something again :-)
14:42:33 <haleyb> oh, perfect, nice end to the cycle! thanks for doing that work
14:42:44 <ralonsoh> +1
14:44:24 <haleyb> lajoskatona: if there is any more work we can add to etherpad and plan for flamingo if possible
14:44:48 <lajoskatona> good idea
14:45:12 <lajoskatona> as I remember there  was an etherpad for the whole work, I try to find that one also
14:45:35 <haleyb> sure, can just link it
14:45:53 <haleyb> next item is eventlet
14:46:11 <ralonsoh> yes, in bullet points
14:46:16 <ralonsoh> OVS: https://review.opendev.org/q/topic:%22bug/2087939%22+status:open
14:46:23 <ralonsoh> SR-IOV: https://review.opendev.org/c/openstack/neutron/+/942884
14:46:35 <ralonsoh> L3: nothing yet, stuck in high prio bugs
14:46:49 <ralonsoh> that's all, ^^ please review the open patches
14:47:31 <haleyb> ralonsoh: thanks for that, will review as much as i can today
14:48:03 <haleyb> and there was a bug for macvtap agent, but that needs a new oslo.service
14:48:09 <haleyb> #link https://bugs.launchpad.net/neutron/+bug/2101076
14:48:36 <ralonsoh> right, not urgency for now (and this mech driver is not frequently used)
14:49:44 <haleyb> great to get all that work done this cycle!
14:50:19 <haleyb> #topic on-demand
14:50:33 <haleyb> any other things to discuss? i see nothing in the wiki
14:51:28 <haleyb> ok, thanks for attending, have a good week and remember it is RC1 week
14:51:33 <haleyb> #endmeeting