[CONTROLLER-735] operational data for OpenFlow disappears after a time delay if packets do not move through a switch Created: 26/Aug/14 Updated: 25/Jul/23 Resolved: 04/Sep/14 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | restconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Coby B Soss | Assignee: | Anil Vishnoi |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Windows |
||
| External issue ID: | 1625 |
| Description |
|
It appears that operational data for openflow goes away after some time. It comes back if packets move through a node. This should not behave this way. The operational data should remain until the node goes away. See list conversation below for more details... https://lists.opendaylight.org/pipermail/controller-dev/2014-August/006334.html |
| Comments |
| Comment by Coby B Soss [ 26/Aug/14 ] |
|
The switch is a virtual switch (OVS/QEMU) |
| Comment by Anil Vishnoi [ 27/Aug/14 ] |
|
Hi Coby, I will try to recreate it locally, meanwhile can you please provide the steps you use to recreate it. Thanks |
| Comment by Anil Vishnoi [ 04/Sep/14 ] |
|
Hi Coby, I tested this with the latest code from controller and openflowpluging and things look fine to me. I did following tests I started controller from openflowplugin project, connected mininet and did pingall. It installs all the permanent flow to enable routing between hosts. I can see statistics of all flow in operational data store. I checked after 15 minutes and stats were still there. Then I installed one flow with idle_timeout== 60 seconds and after installation i can see statistics in operational data store. After 60 seconds flow gets expired and switch removes the flow. Once flow gets removed i can see that flow stats are also removed from operational data store and this is expected behavior. If you still see reported behavior please reopen the bug with instruction to recreate the bug. Thanks |