[ovs-dev] [PATCH] debian: Add another note on interfaces in "auto" section.

[Gurucharan Shetty]

We had one note about the issues with adding OVS interfaces
in the "auto" section.  This commit adds another note about
how adding OVS bridges in the "auto" section can cause
race conditions with systemd.

Signed-off-by: Gurucharan Shetty <guru at ovn.org>
---
 debian/openvswitch-switch.README.Debian | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/debian/openvswitch-switch.README.Debian b/debian/openvswitch-switch.README.Debian
index 5f8f823..d236824 100644
--- a/debian/openvswitch-switch.README.Debian
+++ b/debian/openvswitch-switch.README.Debian
@@ -231,3 +231,11 @@ 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.  Debian systems have added a
+systemd ifup at .service file.  This file will call ifdown and ifup on interfaces
+in "auto" section automatically when they 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'.
-- 
1.9.1