14:00:49 #startmeeting networking 14:00:49 Meeting started Tue Dec 17 14:00:49 2024 UTC and is due to finish in 60 minutes. The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:49 The meeting name has been set to 'networking' 14:00:51 Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh 14:00:58 hello 14:00:59 hi 14:01:05 hi all 14:01:13 Hello o/ 14:02:11 o/ 14:02:15 o/ 14:02:25 ok we can get started 14:02:28 #announcements 14:02:35 #link https://releases.openstack.org/epoxy/schedule.html 14:02:42 We are currently in week R-15 14:02:51 Epoxy-2 milestone R-12 (week of Jan 6th) 14:03:17 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:04:09 But there is not another scheduled drivers meeting for a while 14:05:12 I hope everyone saw my email on meetings for rest of year (i know ykarel did :) 14:05:36 Next CI meeting is Jan 6th 14:05:54 Next Neutron meeting is Jan 7th (mlavalle chair) 14:06:04 Next Drivers meeting Jan 10th 14:06:56 I did have a note in that meeting about my own availability 14:07:00 I will be offline from December 19th to January 8th, checking-in occasionally to make sure there are no fires 14:07:58 that is my plan ^^ but i probably will check email every other day until Jan 1st 14:08:31 Then you will only find me if you are sitting at the beach next to me sharing a cocktail 14:09:01 hi, sorry for being late 14:09:38 I hope everyone will take some time off to enjoy their family/friends too, Neutron will still be here :) 14:10:00 * haleyb feels like a Dad today 14:10:58 :D 14:11:02 last announcement i have is my weekly reminder 14:11:03 Let's continue to use the priorities dashboard for patches in the "ready to merge" state (weekly reminder) 14:11:12 thank you Grandpa for the holiday wisdom 14:12:05 :D 14:12:30 hey! no grandkids yet, don't rush things 14:13:10 and get off my lawn! 14:13:27 again, bad Dad jokes is all i have 14:14:05 Sahid Orentino Ferdjaoui proposed openstack/neutron master: ml2/ovs: improve log message for ports without VLAN tags/net-id during OVS restore https://review.opendev.org/c/openstack/neutron/+/929908 14:14:06 Sahid Orentino Ferdjaoui proposed openstack/neutron master: ml2/ovs: change log level from DEBUG to WARNING for port deletion during binding https://review.opendev.org/c/openstack/neutron/+/929909 14:14:12 any other announcements? 14:14:25 Sahid Orentino Ferdjaoui proposed openstack/neutron master: ml2/ovs: change log level from DEBUG to INFO for port deletion during binding https://review.opendev.org/c/openstack/neutron/+/929909 14:14:54 let's move on 14:15:03 #topic bugs 14:15:13 ihrachys was the deputy last week 14:15:19 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/QNUVMQ4WRKHVAQIAKIRLQZMX5FBMMT42/ 14:16:02 there were a couple related to gate issues that have owners and fixes 14:16:56 this revert should help with the l3-ha issues 14:17:00 #link https://review.opendev.org/c/openstack/neutron/+/937758 14:17:10 Merged openstack/neutron master: Revert "[HA] Do not add initial state change delay in HA router" https://review.opendev.org/c/openstack/neutron/+/937758 14:17:15 Merged openstack/neutron-tempest-plugin master: Turn off wsgi in linuxbridge stable branch jobs https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/937842 14:17:22 but as amorin asked there, will that just re-introduce the original bug? 14:17:47 the bug this patch was solving was in the FTs only 14:18:08 "FTs"? 14:18:12 functional tests 14:18:20 https://bugs.launchpad.net/neutron/+bug/1945512 14:18:27 so I think we are ok with this revert 14:18:40 if we find again the FTs errors, we can address them in a better way 14:19:15 what I saw in our downstream openstack was the following: https://bugs.launchpad.net/neutron/+bug/2083237 14:19:24 I was wondering if the revert will fix it? 14:19:42 yes it should 14:19:44 amorin, yes the revert should help in the scenario mentioned in the bug 14:19:55 perfect, thanks :) 14:20:03 ok, so https://review.opendev.org/c/openstack/neutron/+/929406 shouldn't be required any more 14:20:24 I believe so, I can abandone and mark this as related to the revert 14:20:31 same on the launchpad bug, agree? 14:20:41 yes 14:21:13 great 14:21:50 next bug 14:21:58 Stanislav Dmitriev proposed openstack/neutron master: HA VRRP health check parameters https://review.opendev.org/c/openstack/neutron/+/932716 14:21:59 #link https://bugs.launchpad.net/neutron/+bug/2091711 14:22:08 SG list failure on stable branches 14:22:13 I saw it once only 14:22:27 and in postgre CI 14:22:36 if we don't see it again, we can close it 14:23:09 ralonsoh: ack 14:24:00 next bug 14:24:06 #link https://bugs.launchpad.net/neutron/+bug/2091211 14:24:13 network leakage for flat network 14:25:44 as ihrachys noted, it looks like a legit bug, and there are some good notes there 14:26:36 i will watch it but do not have time to pick it up 14:26:53 should mac-aging-time update with "other" traffic as the reporter suggests? 14:27:51 I don't know if Saeed is only using the explicitly_egress_direct=True option 14:28:03 this is preventing from using the MAC table 14:28:12 because the packet is not using the normal action 14:28:16 that was a reported issue 14:28:19 ralonsoh: that is set in his notes 14:28:23 I know 14:28:35 but I don't know if he tested with and without this flag 14:29:31 there: https://bugs.launchpad.net/neutron/+bug/1884708 (also in the notes) 14:29:37 ralonsoh: when you say it was a reported issue - with neutron or OVS? ah 14:30:17 it is supposed to be fixed but maybe this patch was not considering FLAT networks 14:31:13 I'll comment that in the bug today 14:31:46 thanks ralonsoh 14:32:18 that was all for the bugs 14:33:20 i did have one question regarding the l3-ha revert (which just merged), guess that needs backports 14:33:25 #link https://review.opendev.org/c/openstack/neutron/+/937758 14:33:54 yes pushing those 14:33:59 fixing conflicts :) 14:34:02 ykarel: thanks 14:34:26 are there any other gate issues we should focus on? 14:34:50 the issues with wsgi migration (and the related fixes) 14:35:09 ++ ^ the other main ones 14:35:10 that usually affect loaded envs (with more API workers) 14:35:21 still working on why the Neutron API misses the events... 14:36:43 ok, just want to cut-down the number of rechecks if possible 14:37:50 ok, if no other bugs we can move on 14:37:56 #topic community goals 14:38:09 i see there was a little movement on neutronclient deprecation ? 14:38:12 yatin proposed openstack/neutron stable/2024.2: Revert "[HA] Do not add initial state change delay in HA router" https://review.opendev.org/c/openstack/neutron/+/937878 14:38:16 not really 14:38:16 #link https://review.opendev.org/q/topic:%22bug/1999774%22 14:38:55 well at least one +2 on the routers one 14:39:04 yatin proposed openstack/neutron stable/2024.1: Revert "[HA] Do not add initial state change delay in HA router" https://review.opendev.org/c/openstack/neutron/+/937879 14:39:23 i don't see lajos here today to discuss further 14:39:34 yatin proposed openstack/neutron stable/2023.2: Revert "[HA] Do not add initial state change delay in HA router" https://review.opendev.org/c/openstack/neutron/+/937880 14:39:50 other community goal is eventlet 14:39:52 #link https://bugs.launchpad.net/neutron/+bugs?field.tag=eventlet-deprecation 14:40:13 I have this 14:40:13 https://review.opendev.org/c/openstack/neutron/+/937545 14:40:37 I have a working metadata server (for OVN metadata agent and OVN agent) that works without eventlet 14:40:48 the issue (and I'll send a mail for this) 14:41:17 this implementation only adds the threading option, that means the embbeded server that runs in the same process 14:41:32 so the option metadata_workers is not not valid 14:42:03 I implemented this option only (for now) because it was easier and not dependant on, for example, oslo.services 14:42:33 to implement a multiprocess metadata server we should maybe use a wsgi server or use oslo.services worker to spawn several processes 14:42:50 so this will be a limitation, for sure 14:43:35 this implementation uses the same strategy: haproxy with unix socket 14:43:45 and the metadata server listening to this socket 14:44:01 I'm now trying to export this to the L3 agent metadata 14:44:03 that's all 14:44:21 (btw, we don't have any CI testing metadata in DHCP) 14:44:42 so when oslo.service work progresses will there be something we can consume? 14:45:07 we'll need to implement something (I don't know what) to replace the multiprocess metadata 14:45:16 now is using eventlet.wsgi.server 14:45:23 I replaced all this logic 14:45:48 and most probably we'll be able to use the current logic to spawn processes using the new server 14:46:00 but still unknown if that will work 14:46:01 yes, it's a large patch, thanks for all the work on it 14:46:36 i did see one other change to use threading in the ovs agent i think 14:47:06 #link https://review.opendev.org/c/openstack/neutron/+/937765 14:47:13 i have not reviewed yet just watching 14:48:15 i need to prepare for another meeting so will move on 14:48:17 #topic on-demand 14:48:29 any other items to discuss? 14:48:48 oh, completely forgot about bug deputy... 14:49:08 I am this week 14:49:22 ralonsoh is covering this week, jlibosva next week, then obondarev 14:49:34 it should be very light with holidays i hope 14:49:52 and if some have to wait until january it will be Ok 14:50:28 ok, any other topics? 14:51:02 have a great week and enjoy the holidays, will see you in January 14:51:05 #endmeeting