Code Review / ovsdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: f5bdbec) | patch
Fix transaction replay logic 69/86269/15
authorRobert Varga <robert.varga@pantheon.tech>
Fri, 6 Dec 2019 13:53:44 +0000 (14:53 +0100)
committerStephen Kitt <skitt@redhat.com>
Tue, 7 Jan 2020 16:04:52 +0000 (16:04 +0000)
commitccc8c4dbe82454fae0eae9e43f14cc115f1e372c
tree8be5133cd8b6da0c8254d0cc0472bdcdafe19e6etree | snapshot
parentf5bdbec0adeb8f11724ffdda403f4dd0bde0467fcommit | diff
Fix transaction replay logic

After adding disambiguation (previous patch), it clear there is
a day-0 Obi-Wan bug in the code, which would cause the last
command to not be replayed.

Looking at the pending queue, if the transaction failing is second,
the second and third transactions should be replayed, not just
the second.

JIRA: OVSDB-428
Change-Id: Ifbdf5ba8bad5be6103e4666d95afd615ae7d1ab9
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/transactions/md/TransactionInvokerImpl.java diff | blob | history
southbound/southbound-impl/src/test/java/org/opendaylight/ovsdb/southbound/transactions/md/TransactionInvokerImplTest.java diff | blob | history
Open vSwitch Database Management Protocol