[NETCONF-253] netconf-topology spawned mount of netconf-testtool using ipv6 address fails Created: 10/Aug/16 Updated: 15/Mar/19 Resolved: 23/Aug/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Ryan Goulding | Assignee: | Rudolf Brisuda |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6375 |
| Description |
|
I am not sure if this applies to other ipv6 devices as well, but at least for netconf-testtool, using ipv6 results in: https://gist.github.com/anonymous/58f6d37c4fe4d9299b64e1c724407bb8 and the mount is stuck in "connecting" state. |
| Comments |
| Comment by Rudolf Brisuda [ 16/Aug/16 ] |
|
I tried to replicate this error but it works correctly with ipv6 with using testtool. I always get state "connected" with no exceptions. Are you able to replicate this error again? |
| Comment by Rudolf Brisuda [ 16/Aug/16 ] |
|
This seems like this: https://bugs.opendaylight.org/show_bug.cgi?id=6273 . It is probably duplicate. |
| Comment by Ryan Goulding [ 23/Aug/16 ] |
|
Ack... I haven't had the bandwidth to try to reproduce this. I'll pull a copy later today and try it out. |