tree c3a8246502e3775fd1bc45d6a16e99b584f145ae
parent b471bd19a7d116e201798509f9bc819664f1ac8d
author pierventre <pier@opennetworking.org> 1647886540 +0100
committer Pier Luigi Ventre <pier@opennetworking.org> 1648152642 +0000

[SDFAB-1100] Fix flow removal logic

If the store is already in sync re-issueing a batch
request is dangerous (race with conflictual writes)
and wrong. In this case, if the device is still reporting
the flow, it is enough to send a flow removal directly.

Instead, if the flow is expired it is important to update
the store accordingly and then issue a flow removal as
consequence of the batch request.

Change-Id: I11a595e0a91f0efdc1cac3bf1d589a5108f1ae06