[NETCONF-594] Unable to setup southbound Netconf over TLS using odl-netconf-clustered-topology, Fluorine SR1 Created: 14/Jan/19  Updated: 28/Jan/19  Resolved: 17/Jan/19

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: Fluorine, Fluorine SR1, Fluorine SR2
Fix Version/s: Neon, Fluorine SR2

Type: Bug Priority: Medium
Reporter: Martin Sandberg Assignee: Jakub Morvay
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File logfile_clusteredtopology_091     Text File restconf URL.txt    

 Description   

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.

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.

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.

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.



 Comments   
Comment by Robert Varga [ 15/Jan/19 ]

The problem is that clustered and non-clustered topologies share very little code. The code should be merged up, with very little specialization.

Comment by Jakub Morvay [ 15/Jan/19 ]

Yeah rovarga is right, I believe we just missed to port the changes that add TLS support also to clustered topology implementation.

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.

Comment by Robert Varga [ 15/Jan/19 ]

I actually noticed this discrepancy last week, but could not follow through

JMorvay 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.

Comment by Jakub Morvay [ 16/Jan/19 ]

Issue is created, please see NETCONF-601.

Comment by Jakub Morvay [ 16/Jan/19 ]

Martin_S Can you please try to build your own distro with https://git.opendaylight.org/gerrit/#/c/79578/ and let us know if it solves this issue?

Comment by Raj Gumma [ 28/Jan/19 ]

Hi Jakub,

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.

Thanks in advance.

Comment by Robert Varga [ 28/Jan/19 ]

The fix has been delivered to current fluorine and master, hence it will be part of Neon and Fluorine SR2. Release dates are here: https://docs.opendaylight.org/en/latest/release-process/release-schedule.html

Generated at Wed Feb 07 20:15:25 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.