Hi Timothy, Timothy Redaelli <[email protected]> writes:
> In some scenarios starting ovsdb-server takes more than 90 seconds and > so ovsdb-server.service is marked as failed. > > Signed-off-by: Timothy Redaelli <[email protected]> > --- > NOTE: Currently systemd will not start openvswitch.service > and ovs-vswitchd.service if ovsdb-server.service is automatically restarted > after a failure, but this is a feature that needs to be implemented in systemd > itself (systemd#18856). > --- > rhel/usr_lib_systemd_system_ovsdb-server.service | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/rhel/usr_lib_systemd_system_ovsdb-server.service > b/rhel/usr_lib_systemd_system_ovsdb-server.service > index 98338b9df..ed6419f31 100644 > --- a/rhel/usr_lib_systemd_system_ovsdb-server.service > +++ b/rhel/usr_lib_systemd_system_ovsdb-server.service > @@ -29,3 +29,4 @@ ExecStop=/usr/share/openvswitch/scripts/ovs-ctl > --no-ovs-vswitchd stop > ExecReload=/usr/share/openvswitch/scripts/ovs-ctl --no-ovs-vswitchd \ > ${OVS_USER_OPT} \ > --no-monitor restart $OPTIONS > +TimeoutSec=300 > -- > 2.29.2 waiting for the vswitchd feature, the change LGTM. Acked-by: Paolo Valerio <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
