https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-99 netconf <p>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".</p> <p>Testsuite exposing the problem is here: <a href="https://git.opendaylight.org/gerrit/#/c/28725" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/28725</a></p> <p>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.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-99

Netconf's yang-ext:mount nodes not registered for remote RPC handling

Bug Resolved Duplicate Unassigned Jozef Behran Fri, 13 Nov 2015 17:45:28 +0000 Fri, 15 Mar 2019 22:22:16 +0000 Tue, 24 Nov 2015 15:13:42 +0000 netconf 0 3 <p>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.</p> <p>This seems to be a netconf specific issue</p> <p>Well, it seems our Bugzilla's search is pretty limited. It did not manage to find <a href="https://jira.opendaylight.org/browse/NETCONF-25" title="Clustering : It should be possible to mount a netconf device on one controller instance and access it from any other node in the cluster" class="issue-link" data-issue-key="NETCONF-25"><del>NETCONF-25</del></a> when entering this one ...</p> Duplicate NETCONF-25 Development External issue ID 4635 External issue URL Rank 0|i01wg7: