[NETCONF-99] Netconf's yang-ext:mount nodes not registered for remote RPC handling Created: 13/Nov/15 Updated: 15/Mar/19 Resolved: 24/Nov/15 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Unassigned |
| 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: | 4635 | ||||||||
| Description |
|
When a Netconf device is configured on one node of a cluster and then accessed on a different node, its state is visible but any attempt to access its yang-ext:mount URL will end up with "Mount point does not exist". Testsuite exposing the problem is here: https://git.opendaylight.org/gerrit/#/c/28725 Occurs on stable/lithium and on beryllium as well. The symptoms and behavior exhibited when they are subjected to the test suite linked to above is exactly the same. |
| Comments |
| Comment by Jozef Behran [ 13/Nov/15 ] |
|
The reason for the name in the bug is that after investigation I realized that the most probable cause is that the yang-ext:mount URL node is not registered as "needs to use remote RPC when accessed" so it only performs local lookup and then fails as the device is not accessible locally. |
| Comment by Moiz Raja [ 17/Nov/15 ] |
|
This seems to be a netconf specific issue |
| Comment by Jozef Behran [ 24/Nov/15 ] |
|
Well, it seems our Bugzilla's search is pretty limited. It did not manage to find |