summaryrefslogtreecommitdiff
path: root/debian
diff options
context:
space:
mode:
authorGurucharan Shetty <guru@ovn.org>2017-08-06 22:53:03 -0700
committerGurucharan Shetty <guru@ovn.org>2017-08-07 11:06:38 -0700
commite0dfd67b456c8ea36cc2e2f23039a300dbbedfed (patch)
tree6d6916fe661e397a1b83a9a3b0159914fdc5abb2 /debian
parenta59ea79baa4cd05ca88f5952087ffda0470c7f5f (diff)
downloadopenvswitch-e0dfd67b456c8ea36cc2e2f23039a300dbbedfed.tar.gz
debian: Add note on interfaces in "auto" section.
We had a note about the issues with adding OVS interfaces in the "auto" section. This commit clarifies what an "auto" section is and also adds another note about how adding OVS bridges in the "auto" section can cause race conditions with systemd. Signed-off-by: Gurucharan Shetty <guru@ovn.org> Acked-by: Ben Pfaff <blp@ovn.org>
Diffstat (limited to 'debian')
-rw-r--r--debian/openvswitch-switch.README.Debian13
1 files changed, 12 insertions, 1 deletions
diff --git a/debian/openvswitch-switch.README.Debian b/debian/openvswitch-switch.README.Debian
index 5f8f82334..b38662be0 100644
--- a/debian/openvswitch-switch.README.Debian
+++ b/debian/openvswitch-switch.README.Debian
@@ -223,7 +223,8 @@ script that depends on openvswitch but starts before it, needs to be changed
to depend on openvswitch-switch too.
* Ideally, an admin should not add openvswitch bridges in the 'auto'
-section of the 'interfaces' file. This is because, when ifupdown starts
+section of the 'interfaces' file (i.e., if "br0" is a OVS bridge, you should
+not have a line "auto br0"). This is because, when ifupdown starts
working on bridges listed in 'auto', openvswitch has not yet started.
But, if the admin wants to go down this route and adds openvswitch bridges
@@ -231,3 +232,13 @@ in the 'auto' section, openvswitch-switch will forcefully be started when
ifupdown kicks in. In a case like this, the admin needs to make sure that /usr
has already been mounted and that a remote $syslog (if used) is ready to
receive openvswitch logs.
+
+* With systemd, adding openvswitch bridges in the 'auto' section of the
+'interfaces' file can cause race conditions (i.e., if "br0" is a OVS bridge,
+you should not have a line "auto br0"). Debian systems have added a
+systemd ifup@.service file. This file will call ifdown and ifup on interfaces
+in "auto" section automatically when the interfaces disappear and appear
+respectively. This will cause race conditions if you delete and add the same
+bridges using tools like "ovs-vsctl" or "ovs-dpctl". This is also a problem
+when you upgrade your openvswitch kernel module using commands like
+'force-reload-kmod'.