[SXP-127] Nodes may fail to connect when their connection is deleted and readded in quick succession Created: 11/Oct/17 Updated: 20/Mar/18 |
|
| Status: | Open |
| Project: | sxp |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Martin Dindoffer | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 9268 |
| Description |
|
This can be seen in filtering tests, such as Nodes do send each other OPEN and HANDLE messages, however their connection does not switch to the ON state. This hints at a possible race condition in delete and add operations. |
| Comments |
| Comment by Martin Dindoffer [ 19/Feb/18 ] |
|
Possibly another Carbon occurence: |
| Comment by Martin Dindoffer [ 20/Mar/18 ] |
|
A similar thing happened in Oxygen, however there was no delete operation beforehand - https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/sxp-csit-1node-basic-all-oxygen/214/ |