14:00:19 #startmeeting neutron_l3 14:00:20 Meeting started Wed Sep 25 14:00:19 2019 UTC and is due to finish in 60 minutes. The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:23 The meeting name has been set to 'neutron_l3' 14:00:48 hi 14:01:25 hi 14:01:38 #chair haleyb 14:01:39 Current chairs: haleyb liuyulong 14:02:36 OooooK, let's ssstart. 14:02:44 #topic Announcements 14:03:59 #link https://releases.openstack.org/train/index.html 14:04:07 #link https://releases.openstack.org/train/index.html 14:04:19 We have a Projects Release Date: 16 October, 2019 14:05:01 it will come soon 14:05:36 And I received many RC release mail. 14:06:08 yes, we already released rc1 for many stadium projects 14:06:29 #link https://launchpad.net/neutron/+milestone/train-rc1 14:08:26 This is our train-rc1 related topics. IMO, they are in good shape now, we could catch up the scheduler. 14:10:04 Next 14:10:18 #link https://etherpad.openstack.org/p/Shanghai-Neutron-Planning 14:11:21 Call for topics, summit is also coming soon, we will have 5 days meeting? 14:11:49 ptg starts on Wednesday 14:12:02 Monday - Wednesday is summit and Forum 14:12:12 IIRC 14:13:55 Good, so 3 days, another thing is that we will also hold the meeting online in parallel? 14:14:22 liuyulong: I sent You an email recently about that 14:14:39 I will probably need Your help to organize some streaming 14:14:53 but we can sync later with that 14:15:03 And mlavalle send us the mail to query if there will have a nice tool for those who can not go to Shanghai. 14:16:37 liuyulong: yes, but I will now take care of it instead of mlavalle 14:18:02 Wechat is widely used in China. So I may want to give a try for our L3 team members to test some tools before the PTG. 14:18:29 liuyulong: will You be available tomorrow morning my time? So afternoon Your time 14:18:35 we can sync about it then 14:18:43 or on Friday if You want 14:19:34 And a Proxy Server can also be another choice, so I wonder if there are any free server for us to user from the community? 14:19:58 Backup is coming... 14:20:10 Seems that connection is broken... 14:22:06 slaweq, sure, I will ping you tomorrow. Friday can also be fine. 14:22:26 liuyulong__: great 14:22:28 thx 14:23:41 All right, I have no more announcement. If you have please go ahead. 14:25:05 My irc connection is unstable. Let's speedup. 14:25:18 #topic Bugs 14:27:07 #topic Bugs 14:27:29 #chair liuyulong__ 14:27:30 Current chairs: haleyb liuyulong liuyulong__ 14:27:43 #link https://bugs.launchpad.net/neutron/+bug/1845150 14:27:43 Launchpad bug 1845150 in neutron "[FT] "keepalived" needs network interfaces configured as in its own config" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez) 14:28:01 the patch is here 14:28:12 #link https://review.opendev.org/#/c/684249/ 14:28:49 as commented in the patch, if keepalived starts and doesn't see the tracked interfaces with the needed ips 14:28:52 ralonsoh, thanks, it looks good to me. 14:29:02 the process stops 14:29:07 ok, thanks! thats all 14:29:37 haleyb have +wed it :) 14:30:12 #link https://bugs.launchpad.net/neutron/+bug/1844688 14:30:12 Launchpad bug 1844688 in neutron ""radvd" daemon does not work by default in some containers" [Medium,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez) 14:30:21 yes, thanks for the comment 14:30:22 The fix: https://review.opendev.org/683207 14:30:26 I need to add a reno 14:30:49 and test cases 14:31:16 A new config is added for this bug, so IMO, a release note is needed. Users should know such config option in many ways. 14:31:37 for sure, today I'll push a new patch 14:32:48 ralonsoh, np 14:33:01 Next 14:33:03 #link https://review.opendev.org/683207 14:33:09 #undo 14:33:10 Removing item from minutes: #link https://review.opendev.org/683207 14:33:14 #link https://bugs.launchpad.net/neutron/+bug/1845227 14:33:15 Launchpad bug 1845227 in neutron "new l3 agent router factory breaks neutron-fwaas functional tests" [Critical,Fix committed] 14:33:41 fixed here #link https://review.opendev.org/#/c/652812/ 14:34:16 A Critical bug, and it is fixed. 14:35:52 Last one from me 14:35:55 #link https://bugs.launchpad.net/neutron/+bug/1845145 14:35:55 Launchpad bug 1845145 in neutron "[L3] add abilitiy for iptables_manager to ensure rule was added only once" [High,In progress] - Assigned to LIU Yulong (dragon889) 14:38:21 Basically I did not see that WARNING log from our local queens deployments. But when create new agent extension with parallel processing, I noticed many warning log. 14:39:16 In order to ensure the reentrancy of rule addition, I raised such bug. 14:39:21 liuyulong: but doesn't it means that Your agent extension is doing something wrong? 14:42:21 slaweq, we can add more code to prevent that, but it will need more cache and event more lock to achieve that. A simple reentrancy or idempotent can be a nice approach. 14:42:55 IMO, iptables_manager should have that ability. 14:43:55 I wonder why it wasn't dont like that in the past 14:44:13 I did not find any reason that we want the duplicated rules in that managers rule cache. 14:44:16 maybe haleyb or mlavalle will remember something 14:44:42 #link https://review.opendev.org/#/c/684237/ 14:44:47 * haleyb sticks his head up 14:45:14 The fix is quite simple. 14:45:52 slaweq: we've never needed that before, i don't know why it's happening now 14:47:32 that's why i was wondering if something outside neutron was adding a rule, or if we were calling something twice 14:48:08 haleyb: IIUC Neutron U/S don't need it still but liuyulong is doing some d/s agent extension which needs it to make his life easier 14:48:17 haleyb, yes, that upstream log search can approve that. 14:48:32 LOG a warning does not make sense to me, we are neutron developers, so we can make it better. 14:49:26 right, i'm just wondering how that ironic devstack setup is causing issues, since that seems to be where that port rule is added, not via the neutron api 14:50:14 This fix should still use list() instead of set(), because the rule needs the proper order. 14:50:15 basically i'm saying it would be good to better understand how it's happening before adding a duplicate check 14:50:46 And that's why the patch set 2 has functional test failures. 14:51:13 I will run test locally and update it soon. 14:51:43 Sorry, I have to run now. Let's stop here. 14:52:01 Thank you for your participation. 14:52:10 bye 14:52:25 and sorry for my bad network connection... 14:52:30 Bye 14:52:33 thanks 14:52:35 o/ 14:52:41 #endmeeting