+++ This bug was initially created as a clone of Bug #1807638 +++
During OVS shutdown and startup new and reused connections are being impacted (in upgrade).
We should attempt to preserve all existing flows in the kernel while the OVS daemon is offline, and during startup avoid clearing those flows.
While this does not completely mitigate dropped / failed connections while OVS is upgrading, it dramatically reduces the amount of time user applications are impacted both by upgrades or by unexpected disruption (an OOM kill or OVS crash). Future changes will build on this to try to make OVS upgrade completely transparent to end user applications.
ARP flows are potentially still being lost for new connections (workarounds being investigated with OVS team).
After testing in 4.5, we will consider back porting this to all active releases.
I would have expected ovs save/restore to go back to 4.4 at least.
Verified this bug on 4.4.0-0.nightly-2020-05-24-193742
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.