14:00:11 <liuyulong> #startmeeting neutron_l3
14:00:12 <openstack> Meeting started Wed Mar 10 14:00:11 2021 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:15 <openstack> The meeting name has been set to 'neutron_l3'
14:00:23 <liuyulong> Hi there
14:01:56 <liuyulong> OK, looks like a one person meeting
14:02:07 <liuyulong> Let's scan the bugs quickly.
14:02:19 <liuyulong> #topic Bugs
14:02:22 <liuyulong> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020903.html
14:02:41 <liuyulong> #link http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020767.html
14:02:54 <liuyulong> Two lists from our bug deputy.
14:03:21 <liuyulong> First one is related to DVR
14:03:22 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1916761
14:03:25 <openstack> Launchpad bug 1916761 in neutron "[dvr] bound port permanent arp entries never deleted" [High,In progress] - Assigned to LIU Yulong (dragon889)
14:03:58 <liuyulong> We revert the code deletion of DVR arp control code.
14:04:00 <liuyulong> #link https://review.opendev.org/c/openstack/neutron/+/777903
14:04:41 <liuyulong> That DVR arp control code removal is for this change https://review.opendev.org/c/openstack/neutron/+/601336
14:05:27 <liuyulong> But as we discussed in the gerrit, another approach same to l2pop should be introduced to handle such "ARP responder for allowed_address_pair IP"
14:05:52 <haleyb> hi, sorry i'm late, conflict
14:05:54 <liuyulong> #link https://review.opendev.org/c/openstack/neutron/+/651905
14:06:06 <liuyulong> And this one is also related to 601336.
14:06:20 <liuyulong> If the 601336 is not going to accepted, maybe we should revert this as well.
14:06:49 <liuyulong> I have created one: https://review.opendev.org/c/openstack/neutron/+/778820
14:06:56 <liuyulong> But there are many conflicts.
14:07:00 <liuyulong> haleyb, hi
14:08:20 <haleyb> yes, some of those dvr changes are not a simple revert unfortunately
14:09:43 <liuyulong> Yes, I will read the git log again. My idea is to remove those changes.
14:10:00 <liuyulong> Hope you guys can also take a look at these changes. : )
14:10:35 <liuyulong> Next one
14:10:36 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1917393
14:10:37 <openstack> Launchpad bug 1917393 in neutron "[L3][Port forwarding] admin state DOWN/UP router will lose all pf-floating-ips and nat rules" [High,Fix released] - Assigned to LIU Yulong (dragon889)
14:10:47 <liuyulong> A quick fix: https://review.opendev.org/c/openstack/neutron/+/778126
14:11:10 <liuyulong> This should be backport to stable branches. I will do that.
14:11:26 <liuyulong> Next
14:11:27 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1752903
14:11:28 <openstack> Launchpad bug 1752903 in neutron "Floating IPs should not allocate IPv6 addresses" [Medium,Won't fix]
14:11:51 <liuyulong> I changed this to "wont fix" after my comments: https://bugs.launchpad.net/neutron/+bug/1752903/comments/5
14:12:36 <liuyulong> "Add service type to the subnets of public network" can fix the problem ! Mission complete!
14:13:16 <liuyulong> Last one:
14:13:18 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1917409
14:13:19 <openstack> Launchpad bug 1917409 in neutron "neutron-l3-agents won't become active" [High,New]
14:14:16 <liuyulong> There are gerrit changes uploaded.
14:14:30 <liuyulong> #link https://review.opendev.org/q/topic:%22bug%252F1917409%22+(status:open%20OR%20status:merged)
14:15:51 <haleyb> i finally figured out there were two related changes there, i was confused
14:16:13 <liuyulong> The fix is simple, but we have no idea about why the port can be None from the call trace.
14:16:30 <liuyulong> haleyb, yes, I have left some comments to that.
14:16:44 <liuyulong> The author should merge these two changes to one.
14:17:19 <haleyb> liuyulong: right, and i also don't like just catching the error there if it's really the caller at fault
14:17:52 <haleyb> i'm guessing the port is '' or something
14:19:07 <haleyb> i put a comment
14:19:24 <liuyulong> OK, I see the bug...
14:20:24 <liuyulong> after reading the report's l3 log, it is related to agent gateway port creation.
14:20:43 <liuyulong> We fixed that here
14:20:47 <liuyulong> #link https://review.opendev.org/c/openstack/neutron/+/735762
14:21:04 <liuyulong> #link https://bugs.launchpad.net/neutron/+bug/1883089
14:21:05 <openstack> Launchpad bug 1883089 in neutron "[L3] floating IP failed to bind due to no agent gateway port(fip-ns)" [Medium,Fix released] - Assigned to LIU Yulong (dragon889)
14:21:11 <liuyulong> Same error as this bug.
14:21:40 <liuyulong> OK, mission complete!
14:21:40 <liuyulong> haha
14:22:38 <liuyulong> Mark duplicate of bug #1883089.
14:22:40 <openstack> bug 1883089 in neutron "[L3] floating IP failed to bind due to no agent gateway port(fip-ns)" [Medium,Fix released] https://launchpad.net/bugs/1883089 - Assigned to LIU Yulong (dragon889)
14:22:54 <liuyulong> OK, no more bugs from me now.
14:24:45 <liuyulong> OK, let's move on.
14:24:47 <liuyulong> #topic On demand agenda
14:25:20 <liuyulong> Again for  bp/distributed-dhcp-for-ml2-ovs: https://review.opendev.org/q/topic:%22bp%252Fdistributed-dhcp-for-ml2-ovs%22+(status:open%20OR%20status:merged)
14:26:13 <liuyulong> It's pretty close now, reviews are welcomed.
14:26:48 <haleyb> yes, i have it on my list, just have a busy meeting morning
14:27:46 <liuyulong> The fullstack test case works fine now: https://5fd5e74cdeb26ed32d55-9d697031d66865af8e6eba8e2a3ea98e.ssl.cf5.rackcdn.com/776568/11/check/neutron-fullstack-with-uwsgi/89bfdb7/testr_results.html
14:28:25 <liuyulong> haleyb, thank you, your comments are all addressed. : )
14:34:32 <liuyulong> OK, let's end the meeting here.
14:34:37 <liuyulong> #endmeeting