On Tue, May 26, 2026 at 2:39 PM Timothy Redaelli via dev <
[email protected]> wrote:
> When ovsdb-server or ovs-vswitchd fails and auto-restarts
> (Restart=on-failure), it briefly passes through the failed/inactive
> state. This causes a cascade: openvswitch.service (which Requires
> both) sees the failure and stops, which in turn stops the other
> service via PartOf. When the failed service comes back, the other
> does not automatically restart.
>
> RestartMode=direct (systemd v254+) makes the service transition
> directly to the activating state during auto-restart, skipping the
> failed/inactive state. Dependents never see the failure, so the
> cascade does not happen.
>
> On older systemd versions (e.g. RHEL 9 with systemd 252) the
> directive is silently ignored with a harmless journal warning
> ("Unknown key name 'RestartMode'"), so this change is safe for
> all supported platforms.
>
> Signed-off-by: Timothy Redaelli <[email protected]>
> ---
Looks reasonable to me.
Acked-by: Mike Pattrick <[email protected]>
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
