A summary of issues I'm experiencing (just so that we are on the same page):
1) The problem in the previous comment, where some rules are leftover/deleted when they shouldn't, causing connectivity errors which are fixed by manually deleting all the flows in br-int (this causes a re-creation of all the flows in br-tun).
2) Removing the gateway of a DVR+HA router does not delete the 'sg-' device. This does not reproduce on a normal DVR router, which means it's a regression caused by this patch. I have a fix locally and already posted it on [1].
3) Re-starting the ovs agent after everything is setup, deletes all the flow rules (as it should - they're "stale") but it does not recreate them. This probably has something to do with the cookies of some of the flows is not set properly (they are 0 before restarting the ovs agent and are deleted after the restart).
A summary of issues I'm experiencing (just so that we are on the same page):
1) The problem in the previous comment, where some rules are leftover/deleted when they shouldn't, causing connectivity errors which are fixed by manually deleting all the flows in br-int (this causes a re-creation of all the flows in br-tun).
2) Removing the gateway of a DVR+HA router does not delete the 'sg-' device. This does not reproduce on a normal DVR router, which means it's a regression caused by this patch. I have a fix locally and already posted it on [1].
3) Re-starting the ovs agent after everything is setup, deletes all the flow rules (as it should - they're "stale") but it does not recreate them. This probably has something to do with the cookies of some of the flows is not set properly (they are 0 before restarting the ovs agent and are deleted after the restart).
[1]: https:/ /review. openstack. org/#/c/ 196893/ 19/neutron/ agent/l3/ dvr_edge_ ha_router. py
John.