<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:53:31 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-641] Read Yang files from Local if device reported capabilities don&apos;t have the revision</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-641</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;device reporting yang modules but without revision&lt;br/&gt;
In this case ODL is not even able to read local Yang files from /cache/schema folder.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Linux&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="25195">CONTROLLER-641</key>
            <summary>Read Yang files from Local if device reported capabilities don&apos;t have the revision</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="mmarsale@cisco.com">Maros Marsalek</assignee>
                                    <reporter username="ankit21.a@tcs.com">Ankit agarwal</reporter>
                        <labels>
                    </labels>
                <created>Fri, 18 Jul 2014 13:41:26 +0000</created>
                <updated>Wed, 17 Sep 2014 13:23:29 +0000</updated>
                            <resolved>Wed, 17 Sep 2014 13:23:29 +0000</resolved>
                                    <version>Helium</version>
                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="48741" author="ankit21.a@tcs.com" created="Mon, 21 Jul 2014 05:30:11 +0000"  >&lt;p&gt;Below mentioned gerrit changes can be used to fix these issues.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9112/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9112/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9135/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9135/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="48742" author="tony.tkacik@gmail.com" created="Mon, 21 Jul 2014 07:33:35 +0000"  >&lt;p&gt;Hi Ankit,&lt;br/&gt;
would you rework your controller patch&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9135/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9135/&lt;/a&gt; &lt;br/&gt;
to not require this change in YANGTools?&lt;/p&gt;

&lt;p&gt;Would you abandon your YANGTools patch &lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9112/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9112/&lt;/a&gt;&lt;br/&gt;
since it starts allowing Null values in places, where they were not allowed&lt;br/&gt;
and has potential to introduce NPE based regression at various places (parser, codecs...).&lt;/p&gt;</comment>
                            <comment id="48743" author="ankit21.a@tcs.com" created="Thu, 24 Jul 2014 09:03:26 +0000"  >&lt;p&gt;Hi Tony,&lt;/p&gt;

&lt;p&gt;I have submitted a new patch on &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9135/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9135/&lt;/a&gt; &lt;br/&gt;
and&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/9112/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/9112/&lt;/a&gt;&lt;br/&gt;
But both the changes are required to fix the Bug.&lt;/p&gt;

&lt;p&gt;In 9112 now only YangModelDependencyInfo class has changes which is a caller for the parsing method.&lt;/p&gt;</comment>
                            <comment id="48744" author="kwatsen@juniper.net" created="Wed, 3 Sep 2014 18:32:07 +0000"  >
&lt;p&gt;Regarding this bug, there is plenty of evidence in RFC 6020 that the first revision of a YANG module does not need to have a &quot;revision&quot; statement, and hence not needed in the &amp;lt;hello&amp;gt; message, but section 5.6.4.1 says:&lt;/p&gt;

&lt;p&gt;   &quot;A server MUST advertise all revisions of all modules it implements.&quot;&lt;/p&gt;

&lt;p&gt;Which seems contradictory.  Discussing with the NETMOD WG, it is agreed that the sentence should have been written:&lt;/p&gt;

&lt;p&gt;   &quot;A server MUST advertise all known revisions of all modules it implements.&quot;&lt;/p&gt;

&lt;p&gt;Thus providing the necessary leeway.&lt;/p&gt;

&lt;p&gt;FWIW, the only time it is envisioned a YANG module not wanting to have an initial revision date is when the module itself is already version-specific (e.g., &lt;a href=&quot;http://xml.juniper.net/netconf/junos/14.2R2.4&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://xml.juniper.net/netconf/junos/14.2R2.4&lt;/a&gt;), which clearly will have one and only one revision.  In all other cases, it seems the module is expected to be versioned over time and therefore SHOULD have a revision statement.  For this reason, the NETMOD WG may also add a clarifying statement into section 7.1.9.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Kent&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="25347">CONTROLLER-793</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </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>1393</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=1393]]></customfieldvalue>

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

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

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