A recent change made the ovsdb-server socket available as a gating object
preventing race conditions leading to cascading failure states when the
DB service experienced a failure. As part of that change, all of the
service dependencies were shifted to using the socket file as the gate.
Unfortunately, this exposed a problem on Fedora 44 shipped systemd.
Specifically, with systemd 259.8 the services are now starting in
parallel, but the ovs-ctl calls 'ovs-vsctl' requiring the vswitchd
service to be active.
There already exists the ovs_vsctl function which is meant for db only
transactions, so switch to using that form.
Fixes: 7e7f5d26f841 ("rhel: Add ovsdb-server.socket unit for systemd socket
activation.")
Signed-off-by: Aaron Conole <[email protected]>
---
v1->v3: Lots of rebase / systemd mistakes causing unrelated / unneeded changes.
utilities/ovs-ctl.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utilities/ovs-ctl.in b/utilities/ovs-ctl.in
index 8ebd720dc5..01967e9ffa 100644
--- a/utilities/ovs-ctl.in
+++ b/utilities/ovs-ctl.in
@@ -115,7 +115,7 @@ check_core_config () {
}
del_transient_ports () {
- for port in `ovs-vsctl --bare -- --columns=name find port
other_config:transient=true`; do
+ for port in `ovs_vsctl --bare -- --columns=name find port
other_config:transient=true`; do
ovs_vsctl -- del-port "$port"
done
}
--
2.55.0
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
