From 1ab9ff80b1e85e66a0bf2ddc99d77d028ba9729c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Mon, 27 Jun 2022 15:12:24 -0400
Subject: [PATCH] document another open vswitch bug (tpo/tpa/team#40816)
---
howto/upgrades/bullseye.md | 21 +++++++++++++++------
1 file changed, 15 insertions(+), 6 deletions(-)
diff --git a/howto/upgrades/bullseye.md b/howto/upgrades/bullseye.md
index 2a6db27b..0a864b1f 100644
--- a/howto/upgrades/bullseye.md
+++ b/howto/upgrades/bullseye.md
@@ -559,12 +559,6 @@ See also the official list of [known issues](https://www.debian.org/releases/bul
## Pending
- * the Open vSwitch upgrade completely broke the vswitches. This was
- reported in [Debian bug 989720](https://bugs.debian.org/989720). The workaround is to use `auto`
- instead of `allow-ovs` but this is explicitly warned against [in
- the README.Debian file](https://sources.debian.org/src/openvswitch/2.15.0%2Bds1-2%2Bdeb11u1/debian/openvswitch-switch.README.Debian/#L236) because of a race condition. It's
- unclear what the proper fix is at this point.
-
* some config files should be updated in Puppet to reduce the diff
with bullseye, see [issue tpo/tpa/team#40723](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40723)
@@ -725,6 +719,21 @@ the package was upgraded successfully and the procedure was resumed.
Go figure.
+### major Open vSwitch failures
+
+The Open vSwitch upgrade completely broke the vswitches. This was
+reported in [Debian bug 989720](https://bugs.debian.org/989720). The workaround is to use `auto`
+instead of `allow-ovs` but this is explicitly warned against [in the
+README.Debian file](https://sources.debian.org/src/openvswitch/2.15.0%2Bds1-2%2Bdeb11u1/debian/openvswitch-switch.README.Debian/#L236) because of a race condition. It's unclear what
+the proper fix is at this point, but a patch was provided to [warn
+about this in the the release notes](https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/133) and to [tweak the README a
+little](https://salsa.debian.org/openstack-team/third-party/openvswitch/-/merge_requests/10).
+
+The service names also changed, which led needrestart to coldly
+restart Open vSwitch on the entire gnt-fsn cluster. That brought down
+the *host* networking but, strangely, not the instances. The fix was
+to reboot of the nodes, see [tpo/tpa/team#40816](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40816) for details.
+
# Troubleshooting
## Upgrade failures
--
GitLab