[CONTROLLER-763] of-flow: flow present in operational db even aftrer 60 seconds from switch removal Created: 04/Sep/14 Updated: 25/Jul/23 Resolved: 05/May/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | adsal |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Peter Gubka | Assignee: | Peter Gubka |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Windows |
||
| External issue ID: | 1697 |
| Description |
|
This bug might be related to https://bugs.opendaylight.org/show_bug.cgi?id=1654, but in my case you dont need to have 100s of flows configured. See results from https://jenkins.opendaylight.org/integration/job/integration-master-verify-test-base-of13/138/robot/report/log.html All 8 failures are flows which are present in operational db 30 seconds after deletion. I manually reproduced this behavior with 60 seconds delay too. To reproduce use tests from this gerrit You can manually increase the delay after deletion by modifying 010_SM_add_upd_del_flows.txt; Test Delete Flows; increase sleep timeout. |
| Comments |
| Comment by Vaclav Demcak [ 02/Oct/14 ] |
|
I'd like to ask you for a check. I hope, the described behavior is not available anymore. |
| Comment by Vaclav Demcak [ 02/Oct/14 ] |
|
I hope it is fixed in |
| Comment by Carol Sanders [ 05/May/15 ] |
|
This bug is part of the project to Move all ADSAL associated component bugs to ADSAL. |