OVSDB-445 Port creation not reflected in OperDS 62/66862/2
authorVishal Thapar <vishal.thapar@ericsson.com>
Thu, 4 Jan 2018 05:34:48 +0000 (11:04 +0530)
committerVishal Thapar <vishal.thapar@ericsson.com>
Thu, 4 Jan 2018 10:35:56 +0000 (16:05 +0530)
commite81885ee24626690ed2aacc77b9002b243455ab9
treebc15f8e393483ac37036015b2fde963d21d5bbdb
parent336b178ac8dda6cbf544617427092fdcf16e83fa
OVSDB-445 Port creation not reflected in OperDS

When a port is deleted and added in same ovs-vsctl command
it doesn't show up in OperDS. This is because
OvsdbOperationalCommandAggregator always processes removes
after Updates. Since delete is being done for same port right
after update, it ends up not adding it to datastore.

Fix is to check if same port is present in updates or not
before deleting it.

Note: This may impact other such configuration too, though
not sure of any valid use cases for bridges etc.

Change-Id: I596ceaf579c4342a3e6bc282ce140cf15a295d60
Signed-off-by: Vishal Thapar <vishal.thapar@ericsson.com>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/transactions/md/OvsdbPortRemoveCommand.java