<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:54:58 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[CONTROLLER-1219] OpenDaylight cannot read NETCONF messages that do not contain a xmlns attribute</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1219</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;When OpenDaylight tries to open a NETCONF session with a Cisco router, OpenDaylight generates an error during the reception of the &amp;lt;hello&amp;gt; message coming from the router:&lt;/p&gt;

&lt;p&gt;io.netty.handler.codec.DecoderException: java.lang.IllegalStateException: Hello message not received, instead received: &amp;lt;hello&amp;gt;&lt;br/&gt;
&amp;lt;capabilities&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;urn:ietf:params:netconf:base:1.0&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;urn:ietf:params:netconf:capability:writeable-running:1.0&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;urn:ietf:params:netconf:capability:startup:1.0&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;urn:ietf:params:netconf:capability:url:1.0&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;urn:cisco:params:netconf:capability:pi-data-model:1.0&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;urn:cisco:params:netconf:capability:notification:1.0&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;/capabilities&amp;gt;&lt;br/&gt;
&amp;lt;session-id&amp;gt;1409770544&amp;lt;/session-id&amp;gt;&lt;br/&gt;
&amp;lt;/hello&amp;gt;&lt;/p&gt;

&lt;p&gt;Consequently, the NETCONF session fails to open.&lt;/p&gt;

&lt;p&gt;This has been observed with the follwoing Cisco equipments and IOS versions:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;CSR1000V (virtual routeur) with  IOS 15.4(1)S&lt;/li&gt;
	&lt;li&gt;ASR1001-X with IOS 15.4(2)S0a&lt;/li&gt;
	&lt;li&gt;ISR2900 with IOS 15.1(4)M1&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Attached is a test program that can be used to reproduce the problem with a Cisco router.&lt;/p&gt;

&lt;p&gt;Some investigations in OpenDaylight NETCONF code show that the failure is due to the lack of xmlns attribute in the &amp;lt;hello&amp;gt; message sent by the router. OpenDaylight expects something like:&lt;/p&gt;

&lt;p&gt;  &amp;lt;hello xmlns=&quot;urn:ietf:params:xml:ns:netconf:base:1.0&quot;&amp;gt;&lt;/p&gt;

&lt;p&gt;Whether the NETCONF RFC mandates the presence of the xmlns attribute is unclear to me. So I don&apos;t know if this is a bug in OpenDaylight or a bug in Cisco routers. Anyway, it can be fixed (or worked around depending on the point of view) in OpenDaylight, and I will propose a patch to do this.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25773">CONTROLLER-1219</key>
            <summary>OpenDaylight cannot read NETCONF messages that do not contain a xmlns attribute</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="gwenael.lambrouin@b-com.com">Gwenael Lambrouin</assignee>
                                    <reporter username="gwenael.lambrouin@b-com.com">Gwenael Lambrouin</reporter>
                        <labels>
                    </labels>
                <created>Fri, 20 Mar 2015 10:38:55 +0000</created>
                <updated>Tue, 25 Jul 2023 08:23:57 +0000</updated>
                            <resolved>Mon, 30 Mar 2015 08:21:31 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="50303" author="gwenael.lambrouin@b-com.com" created="Fri, 20 Mar 2015 10:38:55 +0000"  >&lt;p&gt;Attachment hostname-cisco--2015-03-20.zip has been added with description: Test program to reproduce the problem&lt;/p&gt;</comment>
                            <comment id="50300" author="mmarsale@cisco.com" created="Fri, 20 Mar 2015 13:48:03 +0000"  >&lt;p&gt;This was discussed in &lt;a href=&quot;https://ask.opendaylight.org/question/1206/illegalstateexception-on-netconf-hello-message/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://ask.opendaylight.org/question/1206/illegalstateexception-on-netconf-hello-message/&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;There is a pointer to a class in ODL where the hello validation is performed.&lt;/p&gt;

&lt;p&gt;Reading RFC 6241: Hello message example contains the namespace declaration and the xsd schema for netconf base elements contains the hello element. So Id say hello should contain the namespace, but it would do no harm making the validation less strict in ODL.&lt;/p&gt;</comment>
                            <comment id="50301" author="gwenael.lambrouin@b-com.com" created="Fri, 20 Mar 2015 16:35:24 +0000"  >&lt;p&gt;Actually, just removing the namespace test in the method isHelloMessage(Document) of the class &lt;a href=&quot;https://github.com/opendaylight/controller/blob/master/opendaylight/netconf/netconf-util/src/main/java/org/opendaylight/controller/netconf/util/messages/NetconfHelloMessage.java&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/opendaylight/controller/blob/master/opendaylight/netconf/netconf-util/src/main/java/org/opendaylight/controller/netconf/util/messages/NetconfHelloMessage.java&lt;/a&gt; is not enough.&lt;/p&gt;

&lt;p&gt;If we do this, ODL fails later in the method extractSessionId() of the class &lt;a href=&quot;https://github.com/opendaylight/controller/blob/master/opendaylight/netconf/netconf-client/src/main/java/org/opendaylight/controller/netconf/client/NetconfClientSessionNegotiator.java&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/opendaylight/controller/blob/master/opendaylight/netconf/netconf-client/src/main/java/org/opendaylight/controller/netconf/client/NetconfClientSessionNegotiator.java&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;I found a solution, but it is a bit heavy: add the namespace to hello messages when it is missing. I submitted my patch for review here:&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/16926/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/16926/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="50302" author="mmarsale@cisco.com" created="Mon, 23 Mar 2015 08:46:25 +0000"  >&lt;p&gt;Please take bugs if you work on them (so we can keep track of the bugs). I assigned it to you for you this time. Thanks&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13497" name="hostname-cisco--2015-03-20.zip" size="30179" author="gwenael.lambrouin@b-com.com" created="Fri, 20 Mar 2015 10:38:55 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2877</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=2877]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10380"><![CDATA[Lithium-M5]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02p7z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>