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-594 netconf <p>When creating a southbound Netconf connection over TLS to a device, using restconf and the odl-netconf-clustered-topology feature in Fluorine SR1, the connection setup fails.</p> <p>From ODL traces, it looks like ODL is attempting to setup an SSH connection, even though TLS is specified in the restconf call. See the attached trace log.</p> <p>The same restconf call successfully sets up a Netconf connection over TLS when the non-clustered odl-netconf-topology feature is used. See the attached restconf URL.</p> <p>When testing the odl-netconf-clustered-topology feature, the actual ODL deployment is not clustered. But according to the ODL documenation, this should still work. Testing with an actaulyl clustered ODL deployment has not yet been done.</p> NETCONF-594

Unable to setup southbound Netconf over TLS using odl-netconf-clustered-topology, Fluorine SR1

Bug Medium Resolved Done Jakub Morvay Martin Sandberg Mon, 14 Jan 2019 08:56:33 +0000 Mon, 28 Jan 2019 18:34:17 +0000 Thu, 17 Jan 2019 14:29:14 +0000 Fluorine Fluorine SR1 Fluorine SR2 Neon Fluorine SR2 netconf 0 4 <p>The problem is that clustered and non-clustered topologies share very little code. The code should be merged up, with very little specialization.</p> <p>Yeah <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rovarga" class="user-hover" rel="rovarga">rovarga</a> is right, I believe we just missed to port the changes that add TLS support also to clustered topology implementation.</p> <p>It has happened already couple of times and it is not really convenient to support and maintain both implementations (odl-netconf-topology and odl-clustered-netconf-topology). We should aim to either merge the code or get rid of non clustered one. I can open an issue to track this.</p> <p>I actually noticed this discrepancy last week, but could not follow through <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/sad.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=JMorvay" class="user-hover" rel="JMorvay">JMorvay</a> please file a separate issue for merging the common parts of odl-*-netconf-topology, as the clustered thing has a hard dependency on akka – which is not desirable in some deployments. Merging the two requires just taking care of activation and voting – which should be easily abstracted out. It certainly does not concern actual session setup like the problem we are facing here.</p> <p>Issue is created, please see <a href="https://jira.opendaylight.org/browse/NETCONF-601" title="Merge common code from both odl-*-netconf-topologies" class="issue-link" data-issue-key="NETCONF-601">NETCONF-601</a>.</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=Martin_S" class="user-hover" rel="Martin_S">Martin_S</a> Can you please try to build your own distro with <a href="https://git.opendaylight.org/gerrit/#/c/79578/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/79578/</a> and let us know if it solves this issue?</p> <p>Hi Jakub,</p> <p>Has the fix been released? Or when is it planned to be released? We'd like to use the ODL version with the fixes for our ongoing development if possible and are reliant on the TLS support for clustered topology.</p> <p>Thanks in advance.</p> <p>The fix has been delivered to current fluorine and master, hence it will be part of Neon and Fluorine SR2. Release dates are here: <a href="https://docs.opendaylight.org/en/latest/release-process/release-schedule.html" class="external-link" target="_blank" rel="nofollow noopener">https://docs.opendaylight.org/en/latest/release-process/release-schedule.html</a></p> Development Rank 0|i03m1z: