Skip to content
Snippets Groups Projects
Verified Commit 1ab9ff80 authored by anarcat's avatar anarcat
Browse files

document another open vswitch bug (tpo/tpa/team#40816)

parent 4d4d3f17
No related branches found
No related tags found
No related merge requests found
......@@ -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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment