<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:16:05 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>[NETCONF-859] Devices with certain BBF yang models cannot be accessed in Swagger.</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-859</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;This problem is seen using lighty.io 14.0 and 15.1, but also seen with OpenDayLight Silicon and Phosphorus SR1 releases as well.&#160;&lt;/p&gt;

&lt;p&gt;Certain Broadband Forum Yang files cause the swagger in ODL to error. Specifically, one creates a device which contains the YANG file bbf-software-management, the device will get connected and mounted. However, the swagger will not allow access to the device, it will display a box with the following error:&lt;/p&gt;
&lt;h4&gt;&lt;a name=&quot;Fetcherror&quot;&gt;&lt;/a&gt;Fetch error&lt;/h4&gt;

&lt;p&gt;Server Error &lt;a href=&quot;http://10.184.144.176:8181/apidoc/openapi3/18/apis/mounts/5&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://10.184.144.176:8181/apidoc/openapi3/18/apis/mounts/5&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;It can be recreated by simply starting ODL and adding a device (netconf testtool) which contains yang file from the Broadband forum called &quot;&lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;mailto:bbf-software-management@21-09017.yang&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;bbf-software-management@21-09-17.yang&quot;&lt;sup&gt;&lt;img class=&quot;rendericon&quot; src=&quot;https://jira.opendaylight.org/images/icons/mail_small.gif&quot; height=&quot;12&quot; width=&quot;13&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/sup&gt;&lt;/a&gt;&lt;/span&gt;file.&#160; There are several yang files included in this JIRA.. a netconf test tool can be created using these files to reproduce the problem.&#160;&lt;/p&gt;

&lt;p&gt;The problem seems to be related to a &quot;leaf&quot; ref. The bbf-software-manager yang is an augmentation to ietf-hardware. Inside the model, it has the following for example:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;choice selection-criteria {&lt;br/&gt;
&#160; &#160; description&lt;br/&gt;
&#160; &#160; &quot;Selects the criteria to identify which&lt;br/&gt;
&#160; &#160; entry in the list &apos;revision&apos; should&lt;br/&gt;
&#160; &#160; be replaced.&quot;;&lt;br/&gt;
&#160; &#160; case id {&lt;br/&gt;
&#160; &#160; &#160; &#160; description&lt;br/&gt;
&#160; &#160; &#160; &#160; &#160;&quot;This case specifies that the action&lt;br/&gt;
&#160; &#160; &#160; &#160; is to replace the entry within the&lt;br/&gt;
&#160; &#160; &#160; &#160; list &apos;revision&apos; with the specified&lt;br/&gt;
&#160; &#160; &#160; &#160; &apos;id&apos;. The entry must be neither&lt;br/&gt;
&#160; &#160; &#160; &#160; active nor committed.&quot;;&lt;br/&gt;
&#160; &#160; &#160; &#160; leaf id {&lt;br/&gt;
&#160; &#160; &#160; &#160; &#160; &#160; type leafref &lt;/p&gt;
&lt;div class=&quot;error&quot;&gt;&lt;span class=&quot;error&quot;&gt;Unknown macro: {
&#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; path &amp;quot;../../../../../../../bbf-swm}&lt;/span&gt; &lt;/div&gt;
&lt;p&gt;&#160; &#160; &#160; &#160; must &quot;../../../../../../../bbf-swm:revisions/bbf-swm:revision[bbf-&#160; &#160; &#160; &#160; &#160;&#160;&lt;br/&gt;
&#160; &#160; &#160; ....&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&#160;The leaf &quot;id&quot; here is a leafref. ODL cannot decipher this path - or fails to do so. Directly after this there is also an &quot;alias leaf with the same issue. The paths for these seem to be correct.&#160; A work around for this is to change the BBF yang to use the define that the path refers to .. that fixes the issue.&#160;&lt;/p&gt;

&lt;p&gt;For example doing this instead...&#160;&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;leaf id {&lt;br/&gt;
&#160; &#160; &#160;type uint8;&lt;/p&gt;

&lt;p&gt;....&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Windows or Linux machine running ODL Silicon or Phosphorus&lt;/p&gt;

&lt;p&gt;Netconf testtool simulator running the yang files attached.&#160;&lt;/p&gt;</environment>
        <key id="35226">NETCONF-859</key>
            <summary>Devices with certain BBF yang models cannot be accessed in Swagger.</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <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="10002">Duplicate</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="rmagaldi">Robert Magaldi</reporter>
                        <labels>
                    </labels>
                <created>Wed, 9 Feb 2022 20:52:11 +0000</created>
                <updated>Mon, 24 Oct 2022 20:11:12 +0000</updated>
                            <resolved>Mon, 24 Oct 2022 20:11:12 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>1</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="71562" author="rovarga" created="Mon, 24 Oct 2022 20:11:12 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-883&quot; title=&quot;Fail to generate API Doc&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-883&quot;&gt;&lt;del&gt;NETCONF-883&lt;/del&gt;&lt;/a&gt; has a simpler steps to reproduce, let&apos;s follow up there.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="35837">NETCONF-883</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="17349" name="Steps to reproduce.odt" size="17948" author="SamoSchneider" created="Thu, 17 Feb 2022 07:55:53 +0000"/>
                            <attachment id="17323" name="bbf-software-management@2021-09-17.yang" size="68493" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17322" name="bbf-yang-types@2020-05-11.yang" size="7888" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17321" name="iana-hardware@2018-03-13.yang" size="6017" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17320" name="ietf-hardware@2018-03-13.yang" size="37345" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17319" name="ietf-inet-types@2013-07-15.yang" size="16757" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17317" name="ietf-netconf-monitoring-extension@2013-12-10.yang" size="542" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17318" name="ietf-netconf-monitoring@2010-10-04.yang" size="18739" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17316" name="ietf-yang-types@2013-07-15.yang" size="17939" author="rmagaldi" created="Wed, 9 Feb 2022 20:36:08 +0000"/>
                            <attachment id="17324" name="image-2022-02-09-15-31-50-637.png" size="34758" author="rmagaldi" created="Wed, 9 Feb 2022 20:31:51 +0000"/>
                            <attachment id="17350" name="karaf.log" size="483101" author="SamoSchneider" created="Thu, 17 Feb 2022 07:55:58 +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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i041hr:</customfieldvalue>

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