[CONTROLLER-12] ForwardingRulesManager allows provisioning of conflicting/duplicate flows Created: 26/Apr/13 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: | Tejas Nevrekar | Assignee: | Unassigned |
| 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: | 15 |
| Description |
|
As discussed on the forum with Alessandro et al, this is to track the issue with the ForwardingRulesManager during installFlowEntry. In the method addEntry(FlowEntry), the set of container merged flows, stored in toInstallList, is subject to conflict detection & duplicate check resulting in the non-conflicting flows stored in the list toInstallSafe. However, in the end when the actual addEntriesInternal is called, the toInstallList is used in stead of the toInstallSafe. This needs to be fixed to use the toInstallSafe. Without this the duplicate detection will not work. |
| Comments |
| Comment by Tao Chang [ 23/Aug/13 ] |
|
Fixed by Alessandro Boch in: |
| Comment by Carol Sanders [ 05/May/15 ] |
|
This bug is part of the project to Move all ADSAL associated component bugs to ADSAL. |