For cluster mode, only the first server, which is the leader, in a cluster should do init. But, sometimes, the role of the first server would transfer leadership, so we should add --no-leader-only in case the ovn-northd stucked.
v1: ovn-ctl: Add "--no-leader-only" while cluster db init Author: Tao YunXiang <[email protected]> Co-authored-by: Liu Chang <[email protected]> Co-authored-by: Rong Yin <[email protected]> Signed-off-by: Tao YunXiang <[email protected]> Signed-off-by: Liu Chang <[email protected]> Signed-off-by: Rong Yin <[email protected]> --- utilities/ovn-ctl | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/utilities/ovn-ctl b/utilities/ovn-ctl index 2a337ae27..8afe68a0a 100755 --- a/utilities/ovn-ctl +++ b/utilities/ovn-ctl @@ -290,10 +290,9 @@ $cluster_remote_port "$@" "$file" - # Initialize the database if it's running standalone, - # active-passive, or is the first server in a cluster. + # Initialize the database if it's NOT joining a cluster. if test -z "$cluster_remote_addr"; then - $(echo ovn-${db}ctl | tr _ -) init + $(echo ovn-${db}ctl | tr _ -) --no-leader-only init fi if test $mode = cluster; then -- 2.17.1 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
