[OPNFLWPLUG-299] notification NodeRemoved is bypassing processing queue Created: 25/Sep/14 Updated: 27/Sep/21 Resolved: 28/Sep/14 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michal Rehak | Assignee: | Jan Medved |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 2091 | ||||||||
| Description |
|
NodeRemoved notification is currently published to MD-SAL upon connection closed event (issued by device or ofPlugin). Bypassing standard processing queue renders into situation where after notification delivery still some zombie messages might be delivered to MD-SAL and cause confusion. |
| Comments |
| Comment by Michal Rehak [ 25/Sep/14 ] |
|
NodeUpdated must use the same way of delivery to MD-SAL in order to preclude state where during reconnect nodeAdded would arrive before nodeRemoved. |
| Comment by Michal Rehak [ 25/Sep/14 ] |
| Comment by Colin Dixon [ 25/Sep/14 ] |
|
Setting severity to critical. |
| Comment by Jan Medved [ 28/Sep/14 ] |
|
Dangling nodes still being seen seen after mininet exits with a recent integration image |