14:00:17 #startmeeting networking 14:00:17 Meeting started Tue Jul 30 14:00:17 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:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:17 The meeting name has been set to 'networking' 14:00:19 Ping list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh 14:00:20 \o 14:00:27 o/ 14:00:28 o/ 14:00:49 hi 14:00:55 o/ 14:01:02 o/ 14:01:23 hi everyone 14:01:26 #topic announcements 14:01:43 We are now in Dalmatian release week (R - 9) 14:01:48 o/ 14:01:53 Non-client library freeze: August 22nd, 2024 (R-6 week) 14:01:59 Client library freeze: August 29th, 2024 (R-5 week) 14:02:06 Dalmatian-3 milestone: August 29th, 2024 (R-5 week) 14:02:42 so we are pretty close to the end of D 14:03:31 hopefully we have a happy gate so we can merge code :-) 14:03:52 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:23 anything crazy happen last week? 14:04:55 I think most of the CI problems are addressed 14:04:56 we didn't wreck the place \o/ 14:05:28 good to know :) 14:05:54 i am still digging out from a backlog, so feel free to ping me on irc for anything important 14:05:56 o/ 14:06:14 #topic bugs 14:06:27 bcafarel was the deputy last week, here is a link to his report 14:06:33 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/NZKXVL2DHNFLKEEXETJ2JZYMQM5DALCZ/ 14:07:10 there are a few without assignee 14:07:14 on the 3 unassigned bugs, I see you checked the low-haning fruit one, also thanks ralonsoh for checking first one 14:07:20 #link https://bugs.launchpad.net/neutron/+bug/2074207 14:07:28 DHCP agent makes endless attempts to configure a network with MTU < 1280 14:07:46 i thought this was related to a previous bug, but it's slightly different 14:08:03 ralonsoh: just noticing you added a comment 14:08:14 I think it makes sense not to add the ipv6 metadata address if there are no ipv6 subnets 14:08:31 in any case, if you have ipv6 enabled in your env, you should not used smaller mtus 14:08:39 but don't fail because of us 14:09:04 ralonsoh: ack, i couldn't tell whether you thought it was invalid, but i agree we could fix this with a check 14:09:29 i can take it if noone else wants it as i worked on the last one 14:10:20 i don't know why people use small mtus like that, but... 14:11:01 next bug is 14:11:04 #link https://bugs.launchpad.net/neutron/+bug/2073872 14:11:13 Neutron L3 agent not create ECMP in HA router but in single mode is ok 14:12:15 looks like l3-ha differs from "regular" l3 in adding/deleting routes 14:13:26 I can try to maybe reproduce it and look quickly if I will have some time, but not promissing anything for now 14:13:35 this is reminding me of a previous bug where we had issues with overlapping routes, in this case it's just the gateway 14:14:09 slaweq: thanks, i'll watch it 14:14:31 last unassigned is 14:14:35 #link https://bugs.launchpad.net/neutron/+bug/2074056 14:14:43 Invalid documented security group rule protocol "any" 14:14:59 I added a comment here based on what i knew 14:15:16 the "any" keyword is only actually valid when using OSC, not the API 14:15:34 but the API ref says "any" is valid 14:16:39 IMO if Openstackclient accepts 'any' as valid value, we may accept it on the server side as well to be more consistent with the cli tool 14:16:47 it should be easy to do 14:16:51 We can clean-up the doc to say "use None or 0", but i was wondering if anyone thought supporting "any" as an alias in the API was a good idea 14:17:04 you type faster than me 14:17:13 :) 14:17:21 actually the value in the server is "ip" 14:17:33 for protocol 0 14:18:05 ralonsoh: yes, i pointed that out in the bug, so there's almost too many choices 14:18:19 right, I'm now reading your comment 14:18:33 we should not change the CLI (or deprecate "any" with time) 14:19:01 or accept both "any" or "ip" (and the deprecate "any") 14:19:24 right, i think i've used 'any' in scripts myself 14:20:23 i think it should be easy enough to support 'any' as an alias on the server side 14:20:42 +1 14:21:08 +1 14:21:11 the only thing that might be an issue is what does the POST return for protocol? 14:21:32 what it returns now for None and 0 values? 14:22:12 I guess it should be the same and we can clearly document that 'any' is just alias for the value which is returned from API 14:22:13 yes, i just didn't know if someone would be confused if it didn't reutrn "any" 14:22:33 slaweq: yes, that sounds good 14:23:17 i will add that info to the bug, and should be able to work on it eventually 14:24:58 i had filed a bug over the weekend, one of those "this is an annoying traceback" seen in the server logs 14:25:05 #link https://bugs.launchpad.net/neutron/+bug/2074312 14:25:21 of course my quick fix proposal didn't work 14:25:38 has anyone else noticed those tracebacks? 14:25:51 title was " DB semantic violation seen in neutron-tempest-plugin-openvswitch logs deleting router " 14:26:06 This handler is supposed to handle AFTER events, as in 'AFTER it's committed', not BEFORE. Offending resource event: port, after_delete 14:26:12 yes when implementing the new db facade 14:26:25 I think this is because we are creating a port inside a transaction 14:26:35 sorry, deleting the port 14:26:36 i found the code that should have disabled the warning but it's not working in this case 14:26:56 is that somethign recurrent? 14:26:59 there is also one in create_security_group() that doesn't have the "disable the warning" code 14:27:23 every neutron-tempest-openvswitch run has occurrences 14:27:37 neutron-tempest-plugin-openvswitch 14:27:44 i didn't check other logs 14:28:29 one question i had was is it possible to move the code? i figured it would have been done by now if simple 14:28:43 i.e. save the ports and do in a second transaction 14:30:24 ralonsoh: feel free to add a comment to the bug if you have a suggestion, it's not critical just an annoying traceback 14:30:34 we can try that, we are deleting the GW port before that txn 14:31:08 I'll push a patch but we need to be cautious leaving leftovers 14:31:52 there are at least two TODOs for that same issue, luckily finding GUARD_TRANSACTION is easy 14:32:10 ok, i had no other bugs 14:32:16 any others to discuss? 14:32:44 This week elvira is the bug deputy, next week will be slaweq 14:32:49 is that ok for both? 14:32:55 sure! 14:33:51 Current bug count this week: 721, up 14 from last run 14:34:22 #topic community-goals 14:34:36 good for me 14:35:03 We merged the MANAGER role and added documentation, so good there, thanks slaweq ! 14:35:21 yeah, this can be IMO consider as done finally 14:36:23 lajos continues to work on neutronclient deprecation 14:36:28 #link https://review.opendev.org/q/topic:%22bug/1999774%22 14:37:08 fixes all for horizon 14:38:30 ralonsoh: and it looks like you just have one change left for evenlet deprecation? 14:38:39 #link https://review.opendev.org/c/openstack/neutron/+/924317 14:38:46 I'm currently working in an issue related to wsgi and OVN 14:38:49 #link https://review.opendev.org/q/topic:%22bug/2069581%22 14:38:53 that is part of the eventlet server deprecation 14:39:20 yeah, ml2/ovn won't work right now with wsgi (it was 1 week before) 14:39:29 :( 14:39:39 so just investigating https://bugs.launchpad.net/neutron/+bug/2075147 14:39:49 and that's all 14:39:53 and i do see the governance change merged 14:39:55 ack, thanks 14:40:02 #link https://review.opendev.org/c/openstack/governance/+/902585 (merged) 14:40:54 #topic on-demand 14:41:14 we already talked about the dhcp-agent looping bug 14:41:19 any other topics? 14:41:38 not from me 14:42:16 ykarel: CI meeting in-person today? 14:42:32 haleyb, sent a cancellation mail for today 14:42:44 ykarel: ack 14:43:02 ok, if nothing else we are done, have a good week everyone! 14:43:09 #endmeeting