[OPNFLWPLUG-768] l2switch Boron sees an error in karaf Created: 13/Sep/16 Updated: 27/Sep/21 Resolved: 23/Feb/17 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sai MarapaReddy | Assignee: | Anil Vishnoi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6711 |
| Priority: | Highest |
| Description |
|
When started controller by installing feature:install odl-l2switch-switch-ui we see error that "flow with flowid already exists" in karaf logs - Please check the logs here - http://pastebin.com/BTvFEANs Functionality works as expected. logs here - http://pastebin.com/Gqa28p22 |
| Comments |
| Comment by Sai MarapaReddy [ 13/Sep/16 ] |
|
When switch is disconnected and connected back it says 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 |
| Comment by Sai MarapaReddy [ 30/Sep/16 ] |
|
Anil / Abhijit - Do you have comments from openflowplugin |
| Comment by Abhijit Kumbhare [ 30/Sep/16 ] |
|
Adding Shuva & Jozef. |
| Comment by Jozef Bacigal [ 03/Oct/16 ] |
|
In first case it is wrong log setup, it should not be an error it is only information ? |
| Comment by Sai MarapaReddy [ 03/Oct/16 ] |
|
Jozef - We don't see this in Beryllium. But in Boron we see . Any reason what changed the behavior ? |
| Comment by Shuva Jyoti Kar [ 03/Oct/16 ] |
|
Will try out and let you know the reason Sai. |
| Comment by Shuva Jyoti Kar [ 04/Oct/16 ] |
|
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. 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. |
| Comment by Tomas Slusny [ 21/Feb/17 ] |
|
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. |
| Comment by Abhijit Kumbhare [ 23/Feb/17 ] |
|
Closing this bug based on the earlier comments in the bug report. If needed - please reopen. |