Browse Source
Ovs-agent can be very time-consuming in handling a large number of ports. At this point, the ovs-agent status report may have exceeded the set timeout value. Some flows updating operations will not be triggerred. This results in flows loss during agent restart, especially for hosts to hosts of vxlan tunnel flow. This fix will let the ovs-agent explicitly, in the first rpc loop, indicate that the status is restarted. Then l2pop will be required to update fdb entries. Conflicts: neutron/plugins/ml2/rpc.py Conflicts: neutron/plugins/ml2/drivers/l2pop/mech_driver.py Closes-Bug: #1813703 Closes-Bug: #1813714 Closes-Bug: #1813715 Closes-Bug: #1794991 Closes-Bug: #1799178 Change-Id: I8edc2deb509216add1fb21e1893f1c17dda80961 (cherry picked from commitchanges/29/649729/8a5244d6d44
) (cherry picked from commitcc49ab5501
) (cherry picked from commit5ffca49668
)
9 changed files with 128 additions and 17 deletions
@ -0,0 +1,27 @@
|
||||
--- |
||||
critical: |
||||
- | |
||||
The neutron-openvswitch-agent can sometimes spend too much time handling |
||||
a large number of ports, exceeding its timeout value, ``agent_boot_time``, |
||||
for L2 population. Because of this, some flow update operations will not |
||||
be triggerred, resulting in lost flows during agent restart, especially |
||||
for host-to-host vxlan tunnel flows, causing the original tunnel flows to |
||||
be treated as stale due to the different cookie IDs. The agent's first |
||||
RPC loop will also do a stale flow clean-up procedure and delete them, |
||||
leading to a loss of connectivity. |
||||
Please ensure that all neutron-server and neutron-openvswitch-agent |
||||
binaries are upgraded for the changes to take effect, after which |
||||
the L2 population ``agent_boot_time`` config option will no longer |
||||
be used. |
||||
fixes: |
||||
- | |
||||
The neutron-openvswitch-agent was changed to notify the neutron-server |
||||
in its first RPC loop that it has restarted. This signals neutron-server |
||||
to provide updated L2 population information to correctly program FDB |
||||
entries, ensuring connectivity to instances is not interrupted. |
||||
This fixes the following bugs: |
||||
`1794991 <https://bugs.launchpad.net/neutron/+bug/1794991>`_, |
||||
`1799178 <https://bugs.launchpad.net/neutron/+bug/1799178>`_, |
||||
`1813703 <https://bugs.launchpad.net/neutron/+bug/1813703>`_, |
||||
`1813714 <https://bugs.launchpad.net/neutron/+bug/1813714>`_, |
||||
`1813715 <https://bugs.launchpad.net/neutron/+bug/1813715>`_. |
Loading…
Reference in new issue