Do not assert seal transition on forward path 24/80424/2
authorRobert Varga <robert.varga@pantheon.tech>
Wed, 20 Feb 2019 12:56:30 +0000 (13:56 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Wed, 20 Feb 2019 21:12:55 +0000 (22:12 +0100)
commit6a6c8b35a9c389488f76e221abca9bcd16ceff64
tree5ecc5033e32850a3bdfa7221debc0f92289c5e07
parent4e9452f4d05224f001d84b38d1a288a7cd8aea60
Do not assert seal transition on forward path

Unlike the replay path, where we expect no successor, the forward
path may very well encounter a successor being present.

Move the assertion to replay path only, as that is where it catches
issues. The forward path automatically propagates the seal via its
use of sendRequest(), which is forwarded as needed and therefore
we only note the race via LOG.debug() and not assert it.

Change-Id: I6f95acc49800d456c049d19982c801015fd69420
JIRA: CONTROLLER-1885
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
(cherry picked from commit db3d7caeeb310f76a9a159f9a8d7e9beff89f645)
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/AbstractProxyTransaction.java
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/LocalReadWriteProxyTransaction.java
opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/databroker/actors/dds/RemoteProxyTransaction.java