On Fri, 5 Mar 2021 10:34:36 -0800 Ben Pfaff <[email protected]> wrote: > On Fri, Mar 05, 2021 at 12:47:05PM +0100, Timothy Redaelli wrote: > > 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]> > > I'm surprised it takes so long. What leads to that? Is it a bug in > ovsdb-server?
Hi, The scenario is an openshift (RHOCP4.6) server in low-performance mode after a reboot of the server. After the failure systemd automatically restarts ovsdb-server.service (that starts successfully at this time), but due to [1] openvswitch.service and ovs-vswitchd.service are not started and they needs to be started manually. In the meanwhile systemd implements the RFE in [1], I think changing the timeout to 300 seconds (the same timeout we already use for ovs-vswitchd.service) is a good workaround. [1] https://github.com/systemd/systemd/issues/18856 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
