[NETCONF-539] Incorect handling of base:1.1 capability when namespaces are used Created: 25/Apr/18  Updated: 27/Apr/18  Resolved: 27/Apr/18

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: Oxygen
Fix Version/s: Oxygen

Type: Bug Priority: Medium
Reporter: Marek Gradzki Assignee: Marek Gradzki
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I tried to use ncclient to connect netconf server.
It sends following hello message:

<?xml version="1.0" encoding="UTF-8"?>
<nc:hello xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0"><nc:capabilities>
[...]
<nc:capability>urn:ietf:params:netconf:base:1.0</nc:capability>
<nc:capability>urn:ietf:params:netconf:base:1.1</nc:capability>
[...]
</nc:capabilities></nc:hello>

ODL Netconf also advertises base:1.1 capability, so
ncclient expects chunked framing.

But ODL Netconf fails to detect base:1.1 capability due to used namespace prefixes.
As a result nnclient reports timeout.

 Comments   
Comment by Marek Gradzki [ 25/Apr/18 ]

Oxygen fix:

https://git.opendaylight.org/gerrit/#/c/71296/

Comment by Marek Gradzki [ 25/Apr/18 ]

Master:

https://git.opendaylight.org/gerrit/#/c/71298/

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