ovs-vsctl's connections are short-lived, so it doesn't care about db status changes.
Reported-by: Tobias Hofmann <[email protected]> Reported-at: https://mail.openvswitch.org/pipermail/ovs-discuss/2021-February/050914.html Signed-off-by: Han Zhou <[email protected]> Acked-by: Dumitru Ceara <[email protected]> --- utilities/ovs-vsctl.c | 1 + 1 file changed, 1 insertion(+) diff --git a/utilities/ovs-vsctl.c b/utilities/ovs-vsctl.c index c1d470006169..2f5ac1a26225 100644 --- a/utilities/ovs-vsctl.c +++ b/utilities/ovs-vsctl.c @@ -180,6 +180,7 @@ main(int argc, char *argv[]) ovsdb_idl_set_shuffle_remotes(idl, shuffle_remotes); ovsdb_idl_set_remote(idl, db, retry); ovsdb_idl_set_leader_only(idl, leader_only); + ovsdb_idl_set_db_change_aware(idl, false); run_prerequisites(commands, n_commands, idl); /* Execute the commands. -- 2.30.2 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
