https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-100 ovsdb <p>There are a few cases, identified such as lack of exception handling in event processing and others which might cause random failures in flow programming.</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-100

Flows failed to get programmed in a very random fashion

Bug Resolved Done Unassigned Madhu Venugopal Fri, 19 Sep 2014 05:32:12 +0000 Thu, 19 Oct 2017 21:28:13 +0000 Tue, 12 Jan 2016 23:17:28 +0000 unspecified openstack.net-virt-providers 0 4 <p><a href="https://git.opendaylight.org/gerrit/11353" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/11353</a></p> <p>A temporary work around to this bug was put in place by<br/> adding a Thread.sleep(500):</p> <p><a href="https://github.com/opendaylight/ovsdb/commit/e2506003510932187bbac87e0d5b6bbd3c4d57a2" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/opendaylight/ovsdb/commit/e2506003510932187bbac87e0d5b6bbd3c4d57a2</a></p> <p> try </p> { commitFuture.get(); // TODO: Make it async (See CONTROLLER-624) logger.debug("Transaction success for write of Flow "+flowBuilder.getFlowName()); Thread.sleep(500); &lt;====== here } <p> catch (Exception e) </p> { logger.error(e.getMessage(), e); modification.cancel(); } <p>while that helped, a better fix should be implemented, so<br/> flow programming can scale.</p> Development External issue ID 1972 External issue URL ODL SR Target Milestone Rank 0|i020nb: