[ovs-git] [ovn-org/ovn] d05170: ovs: Include monitor condition expected seqno fix.

Dumitru Ceara noreply at github.com
Tue Jun 1 11:45:14 UTC 2021

  Branch: refs/heads/master
  Home:   https://github.com/ovn-org/ovn
  Commit: d0517045596964ef9de8332779079513b200209f
  Author: Dumitru Ceara <dceara at redhat.com>
  Date:   2021-06-01 (Tue, 01 Jun 2021)

  Changed paths:
    M ovs

  Log Message:
  ovs: Include monitor condition expected seqno fix.

When setting monitor conditions ovsdb_cs_db_set_condition() returns the
sequence number when it is expected that all updates that correspond to
the new condition have been received.  This sequence number is used by
ovn-controller to determine whether a monitor condition change is
already in flight.  If that's the case ovn-controller waits until all
in-flight condition changes have been processed before propagating the
SB_Global.nb_cfg value to the chassis record.

This is part of the "ovn-nbctl --wait=hv sync" implementation which, as
far as I know, is not used actively by any CMS but is, however, used by
OVN self tests.

Bump the OVS submodule version to include b5bb044fbe4c ("ovsdb-cs:
Consider all tables when computing expected cond seqno.") which fixes a
bug in ovsdb_cs_db_set_condition().  Without it, the returned expected
sequence number was wrong, leading to occasional test failures in the
OVN test suite.

Signed-off-by: Dumitru Ceara <dceara at redhat.com>
Acked-by: Ilya Maximets <i.maximets at ovn.org>
Signed-off-by: Numan Siddique <numans at ovn.org>

More information about the git mailing list