diff options
author | Alex Wang <alexw@nicira.com> | 2015-04-01 16:11:19 -0700 |
---|---|---|
committer | Alex Wang <alexw@nicira.com> | 2015-04-01 17:02:39 -0700 |
commit | b3cceba0b7c4013f46b01f8987e8716d7857c6db (patch) | |
tree | 3ea3a66493941d789d0732025f5e8f34f74fa704 /datapath-windows/include | |
parent | 508624b691e1517e4d426aa69165ea1efba80d53 (diff) | |
download | openvswitch-b3cceba0b7c4013f46b01f8987e8716d7857c6db.tar.gz |
bridge: Execute bridge_run() only after retrieving db contents.
During upgrade of ovs-vswitchd, we do not want to recreate the already
configured kernel interfaces. Especially when IP address is assigned to
the internal port, the recreation will cause the lost of connection.
Therefore, ovs-vswitchd should read current ovsdb content first and then
reuse the existing kernel interfaces that are configured in ovsdb. In
terms of the code language, ovs-vswitchd should only execute bridge_run()
after it finishes reading the ovsdb content.
However, this expected behavior is broken by the recent commit d18e52e
(ovsdb-idl: Tolerate missing tables and columns.) which causes the
execution of bridge_run() before getting the hint of configured interfaces
from ovsdb.
To fix the issue, this commit makes sure that the execution of bridge_run()
happens only after retrieving the ovsdb contents.
VMware-BZ: #1424342
Signed-off-by: Alex Wang <alexw@nicira.com>
Acked-by: Ben Pfaff <blp@nicira.com>
Diffstat (limited to 'datapath-windows/include')
0 files changed, 0 insertions, 0 deletions