Force all fdb entries update after ovs-vswitchd restart
When ovs-vswitchd process is restarted neutron-ovs-agent will
handle it and reconfigure all ports and openflows in bridges.
Unfortunatelly when tunnel networks are used together with
L2pop mechanism driver, this driver will not notice that agent
lost all openflow config and will not send all fdb entries which
should be added on host.
In such case L2pop mechanism driver should behave in same way like
when neutron-ovs-agent is restarted and send all fdb_entries to
agent.
This patch adds "simulate" of agent start flag when ovs_restart is
handled thus neutron-server will send all fdb_entries to agent and
tunnels openflow rules can be reconfigured properly.
Reviewed: https:/ /review. openstack. org/620708 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=ae031d18866 a9e3652f4fc122f 120915209a7b29
Committed: https:/
Submitter: Zuul
Branch: master
commit ae031d18866a9e3 652f4fc122f1209 15209a7b29
Author: Slawek Kaplonski <email address hidden>
Date: Wed Nov 28 22:42:18 2018 +0100
Force all fdb entries update after ovs-vswitchd restart
When ovs-vswitchd process is restarted neutron-ovs-agent will
handle it and reconfigure all ports and openflows in bridges.
Unfortunatelly when tunnel networks are used together with
L2pop mechanism driver, this driver will not notice that agent
lost all openflow config and will not send all fdb entries which
should be added on host.
In such case L2pop mechanism driver should behave in same way like
when neutron-ovs-agent is restarted and send all fdb_entries to
agent.
This patch adds "simulate" of agent start flag when ovs_restart is
handled thus neutron-server will send all fdb_entries to agent and
tunnels openflow rules can be reconfigured properly.
Change-Id: I5f1471e20bbad9 0c4cdcbc6c06d3a 4412db55b2a
Closes-bug: #1804842