Description of problem: Customers network team discovered that when the neutron fip-* namespace is deleted OR when the fg-* port is deleted from the br-int bridge, after restarting the 'neutron-l3-agent' service, the default gateway is missing within the fip-* namespace. It appears to be a race condition as a subsequent restart after the initial restart of the 'neutron-l3-agent' service adds the route back. Version-Release number of selected component (if applicable): OSP10 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I think I answered a similar bug on the rhos-tech list, here's my response from there: There have been a couple of bugs fixed upstream (and backported) that might be related, the fact that adding the default route and arping fail make me think of this one: (Race condition in update_gateway_port when two simultaneous router update occurs for the same router) https://bugs.launchpad.net/neutron/+bug/1631513 https://review.openstack.org/#/c/385617/ Another related change is: (After binding a floating IP to VM, the static route can't work in DVR) https://bugs.launchpad.net/neutron/+bug/1571676 https://review.openstack.org/#/c/308068/ But I would think it's the first. I do see that first change in the rhos-10.0-patches branch, so I'm assuming there is a build that has the change. If that doesn't fix the problem then I'd need to investigate further.
Is that included in the rebase BZ:1430712
I don't see bug 1631513 listed in that BZ, but the fix for it was merged back in January, before some of the other bugs listed.
Customer is going to test applying the patches manually from the following: https://review.openstack.org/#/c/385617/ https://review.openstack.org/#/c/413240/ I will report back the findings when they have completed the testing.
Assaf - Customer confirmed the manual edits fixed their issue. Customer seems to be okay with waiting for rebase. So I believe once the rebase comes out we can close this out as FIXED CURRENT RELEASE?
Verified on openstack-neutron-9.3.1-2.el7ost.noarch The code that solved the problem to the customer exists in this version
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1594