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-768 OpenFlowPlugin <p>When started controller by installing feature:install odl-l2switch-switch-ui</p> <p>we see error that "flow with flowid already exists" in karaf logs - Please check the logs here - <a href="http://pastebin.com/BTvFEANs" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/BTvFEANs</a></p> <p>Functionality works as expected. logs here - <a href="http://pastebin.com/Gqa28p22" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/Gqa28p22</a></p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-768

l2switch Boron sees an error in karaf

Bug Resolved Done Anil Vishnoi Sai MarapaReddy Tue, 13 Sep 2016 18:04:39 +0000 Mon, 27 Sep 2021 09:01:54 +0000 Thu, 23 Feb 2017 16:41:14 +0000 General 0 6 <p>When switch is disconnected and connected back it says</p> <p>2016-09-13 11:04:57,490 | ERROR | entLoopGroup-7-5 | DeviceFlowRegistryImpl | 207 - org.opendaylight.openflowplugin.impl - 0.3.0.Boron | Flow with flowId 3 already exists in table 0<br/> 2016-09-13 11:04:57,491 | ERROR | entLoopGroup-7-6 | DeviceFlowRegistryImpl | 207 - org.opendaylight.openflowplugin.impl - 0.3.0.Boron | Flow with flowId 2 already exists in table 0</p> <p>Anil / Abhijit - Do you have comments from openflowplugin</p> <p>Adding Shuva &amp; Jozef.</p> <p>In first case it is wrong log setup, it should not be an error it is only information ?</p> <p>Jozef - We don't see this in Beryllium. But in Boron we see . Any reason what changed the behavior ?<br/> Changing the log to Info is easy, Even if these are INFO messages why do we see duplicate flows in Boron but not in Beryllium ?</p> <p>Will try out and let you know the reason Sai.</p> <p>I do agree with the fact that the log is purely informative. It tells us that the application is trying to provision flows with the same flow id. And as noticed by you it does not affect functionality.</p> <p>As stated in Bug5822, it has to be ensured by the application that the flow-id used is unique.If not we get this log, meaning there's been one more flow asked to be added with the same flow-id.</p> <p>This log was already changed from ERROR to WARN in both stable/boron and carbon, and as it is l2switch fault by not providing unique enough flow id, and then we just create flow with alien ID, but as Shuva said, it does not affect functionality, then I think this bug can be safely closed.</p> <p>Closing this bug based on the earlier comments in the bug report. If needed - please reopen.</p> Development External issue ID 6711 External issue URL Priority Rank 0|i0336v: