[NETCONF-207] Clustering: Problem accessing Netconf device when a node is isolated Created: 20/May/16 Updated: 15/Mar/19 Resolved: 10/Oct/17 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 5937 |
| Description |
|
1. Configure a 3-node cluster with one Netconf device You will get an error. In the attached case it is "akka timeout error" but I have seen test runs failing in a different way (but these test run results were lost). |
| Comments |
| Comment by Jozef Behran [ 20/May/16 ] |
|
Attachment bug.tgz has been added with description: Test run exhibiting the bug |
| Comment by Tomas Cere [ 10/Oct/17 ] |
|
This case should be working now according to csit |