Aaron Conole <[email protected]> writes: > 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 few problems on Fedora 44 shipped systemd. > Specifically, with systemd 259.8 the services are now starting in parallel, > but that leads to a few unexpected side effects: > > 1. The ovs-ctl calls 'ovs-vsctl' directly, which requires both a DB service > and the vswitchd service to acknowledge the transaction, leading to a > hang. > > 2. The ovs-delete-transient-ports service not waiting for the ovsdb service > to fully initialize (when running vsctl with --no-wait), so erroring > before completing the transient port deletion. > > Since the service is meant to run on boot, only once (given the Type and > RemainAfterExit values) it makes more sense to keep the gate on the server > service, and switch 'ovs-ctl' to use the builtin ovs_vsctl function to > be a 'db only' transaction. > > Fixes: 7e7f5d26f841 ("rhel: Add ovsdb-server.socket unit for systemd socket > activation.") > Signed-off-by: Aaron Conole <[email protected]> > ---
Ugh... sorry about this. This is from a rebase-gone-wrong, and I'll send a v3 shortly. Please ignore this version. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
