Timothy Redaelli via dev <[email protected]> writes: > 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: the umbrella 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+, PR systemd/systemd#27584) 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 the directive is silently ignored with a > harmless journal warning ("Unknown key name 'RestartMode'"), so > this change is safe for all supported platforms. Tested with > containers:
Thanks - applied. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
