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/OPNFLWPLUG-169 OpenFlowPlugin <p>When running regression tests the flow:1 topology is sometimes present and sometimes it is not. This shows that the timetaken for ODL to detect the extra flow is not constant </p> <p>Steps<br/> Startup ODL<br/> Wait<br/> Call <a href="http://localhost:8080/restconf/operational/network-topology:network-topology/" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8080/restconf/operational/network-topology:network-topology/</a></p> <p>ODL details:<br/> org.opendaylight.controller.version = 0.1 org.opendaylight.controller.build.scm.version = a31a4448ea6665317f4af41ae26d804829418c04<br/> org.opendaylight.controller.build.user = jenkins-controller org.opendaylight.controller.build.workspace = ********** org.opendaylight.controller.build.timestamp = 1400624933140 org.opendaylight.controller.build.machine = **********</p> <p>Result<br/> This topology may be present or it may not.</p> { "topology-id": "flow:1" } <p>Operating System: Linux<br/> Platform: PC</p> OPNFLWPLUG-169

"topology-id": "flow:1" present sporadically

Bug Resolved Done Luis Gomez RichardHill Wed, 21 May 2014 08:55:03 +0000 Mon, 27 Sep 2021 09:01:12 +0000 Tue, 12 Aug 2014 22:12:24 +0000 General 0 2 <p>Attachment opendaylight.tar.xz has been added with description: opendaylight logs</p> <p>Luis,</p> <p>Do you see this issue?</p> <p>Thanks,<br/> Abhijit</p> <p>I do not see this issue in the automation but I normally give 70 secs between I launch run.sh and I start doing something with the controller. It could be also that with low CPU, you need more than 70 secs to get the controller full up.</p> <p>BR/Luis</p> <p>Luis,</p> <p>Should we close this one?</p> <p>Abhijit</p> <p>Yes, close it. MD-SAL topology works fine in the automation.</p> Development External issue ID 1060 External issue URL Rank 0|i02zhr: