[OPNFLWPLUG-707] [He plugin] Reconciliation not triggering after a single node reboot in a nonOFHA scenario Created: 14/Jun/16 Updated: 27/Sep/21 Resolved: 17/Aug/16 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Shuva Jyoti Kar | Assignee: | Shuva Jyoti Kar |
| 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: | 6058 |
| Description |
|
Reconciliation is not getting triggered after reboot of node to which the switch was connected. In a non-OFHA scenario, if the node goes does down along with th eswitch, the OperDS still has the stale entity. Now, when switch reconnects to the same cluster-node or different cluster-node, even if we try to update Oper DS, DataTreeChange notification is not fired (because we are updating same switch infor again) and hence reconciliation would not trigger. |
| Comments |
| Comment by Shuva Jyoti Kar [ 14/Jun/16 ] |
|
As a part of the patch we plan to delete the switch from OperDS, if hasOwner and isOwner for that switch is null. Since there exists no notification publisher (as the node to which the switch was connected has gone down), as suggested, we plan to make inventory-manager , an OfEntity listener and delete the node in specific condition |
| Comment by Shuva Jyoti Kar [ 14/Jun/16 ] |