We ran into an issue in a container environment where the pid files are on a mount in the host system and not cleaned up. In this case, due to reuse of pids and ovn-ctl using exec(), the pid of ovn-ctl itself was in the ovnnb_db.pid file. So ovn-ctl would fail to start ovsdb-server.
This adds the ability to add an optional process name check to avoid this situation. Terry Wilson (2): Handle re-used pids in pidfile_is_running Ensure pid belongs to ovsdb-server in ovn-ctl ovs | 2 +- utilities/ovn-ctl | 11 +++++++++-- 2 files changed, 10 insertions(+), 3 deletions(-) -- 2.34.3 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
