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-128 netconf <p>When odl-netconf-connector-* feature is not installed (example: Netconf clustered CRUD tests <span class="error">&#91;1&#93;</span>, <span class="error">&#91;2&#93;</span>, <span class="error">&#91;3&#93;</span>, <span class="error">&#91;4&#93;</span>), then there is no way to remotely detect whether Netconf is ready or not (and when that happens). Locally it is possible to grep logs for "&lt;some netconf related component&gt; is up/initialized successfully/whatever" message but when no ssh access is provided, this can't help much. This currently breaks "netconf readiness" suite as it was intended to detect exactly when Netconf is ready.</p> <p>Investigation revealed that the problem is caused by bizzare behavior of Netconf. All Netconf related Restconf URLs will return "404 Not Found" until a Netconf device is configured, then they mysteriously start to report "200 Ok". Tested on Netconf topology. The correct behavior (at least for topology) is to start returning "200 Ok" as soon as devices can be configured.</p> <p><span class="error">&#91;1&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-only-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-only-beryllium/</a><br/> <span class="error">&#91;2&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-beryllium/</a><br/> <span class="error">&#91;3&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-only-boron/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-only-boron/</a><br/> <span class="error">&#91;4&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-boron/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-boron/</a></p> <p>Operating System: All<br/> Platform: All</p> NETCONF-128

Cannot detect netconf up and running when odl-netconf-connector-* is not used

Bug Resolved Done Tomas Cere Jozef Behran Tue, 19 Jan 2016 16:27:36 +0000 Mon, 5 Dec 2022 19:50:58 +0000 Fri, 22 Jan 2016 12:36:44 +0000 netconf 0 3 <p>This change is reportedly fixing this problem: <a href="https://git.opendaylight.org/gerrit/#/c/32936/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/32936/</a></p> <p>It appears the patch above was merged but is still not in the artifacts in Nexus. So a multipatch-sandbox-build job is due to be done to make sure this bug is not there. Changing to "waiting for review".</p> <p>Just completed testing on a Beryllium snapshot (had to build it locally as the build server(s) are broken; build was made from stable/beryllium sources as they were yesterday evening). This bug is still present.</p> <p>(changed to "CONFIRMED" as the bug is confirmed to survive the patches)</p> <p>Another change that contributes to fixing this bug: <a href="https://git.opendaylight.org/gerrit/32939/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/32939/</a></p> <p>Results of discussion with developers:</p> <p>1. The fixes add the topology into the operational datastore.<br/> However the test suite is searching it in config datastore.<br/> We agreed that it would be good to add it into the config datastore<br/> as well as some components might search it there and get confused<br/> if not found.<br/> 2. The fixes did not make it to beryllium before I built my image so I<br/> did not have them (yet).</p> <p>Going to retest with the latest image of netconf. Right now leaving at "confirmed" as the bug is still there (the netconf may be invisible to components which search for topology in config datastore only).</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/33196/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/33196/</a></p> Relates NETCONF-919 Development External issue ID 5014 External issue URL Rank 0|i01wmn: