<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:34:12 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>[OPNFLWPLUG-1103] Openflow-Action list needs a key?</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-1103</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;I am using `pyang` to validate a yang module which I am basing off of openflow. In the process of building it out, I am validating my yang through pyang and I am noticing this error:&lt;/p&gt;

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

&lt;p&gt;&lt;tt&gt;$ pyang my.yang&lt;/tt&gt;&lt;br/&gt;
 &lt;tt&gt;openflow-instruction@2013-07-31.yang:21: error: the list at &quot;openflow-&lt;font color=&quot;#ff0000&quot;&gt;instruction@2013-07-31.yang:21 (at openflow-action@2015-02-03.yang:32)&quot; needs at least one key because it is used as config&lt;/font&gt;&lt;/tt&gt;&lt;/p&gt;

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

&lt;p&gt;When looking at the source code for openflow-action I see:&lt;/p&gt;

&lt;p&gt;&#160;grouping actions-grouping {&lt;br/&gt;
 &lt;tt&gt;&#160; &#160;list action {&lt;/tt&gt;&lt;br/&gt;
 &lt;tt&gt;&#160; &#160; &#160; uses action-grouping;&lt;/tt&gt;&lt;br/&gt;
 &lt;tt&gt;&#160; &#160; &#160; leaf experimenter-id {&lt;/tt&gt;&lt;br/&gt;
 &lt;tt&gt;&#160; &#160; &#160; &#160; type oft:experimenter-id;&lt;/tt&gt;&lt;br/&gt;
 &lt;tt&gt;&#160; &#160; &#160;&lt;/tt&gt;}&lt;br/&gt;
}&lt;/p&gt;

&lt;p&gt;So it is missing a `key`. I can&apos;t tell if this is a bug with openflow-action or if pyang is running in some ultra strict mode, but does anyone have insight on this?&lt;/p&gt;</description>
                <environment>&lt;ul&gt;
	&lt;li&gt;CentOS 7&lt;/li&gt;
	&lt;li&gt;pyang 2.3.2&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&#160;&lt;/p&gt;</environment>
        <key id="33216">OPNFLWPLUG-1103</key>
            <summary>Openflow-Action list needs a key?</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="dheenab">dheenadayalan b</assignee>
                                    <reporter username="esender">Eric Sender</reporter>
                        <labels>
                    </labels>
                <created>Fri, 4 Sep 2020 20:21:24 +0000</created>
                <updated>Wed, 16 Dec 2020 21:44:41 +0000</updated>
                            <resolved>Wed, 16 Dec 2020 21:44:41 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="68611" author="JIRAUSER13128" created="Thu, 10 Sep 2020 18:27:13 +0000"  >&lt;p&gt;A couple github tickets which I am running in parallel confirm that ODL has syntax errors&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/mbj4668/pyang/issues/674&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mbj4668/pyang/issues/674&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/CESNET/libyang/issues/1192#issuecomment-690026975&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/CESNET/libyang/issues/1192#issuecomment-690026975&lt;/a&gt;&lt;/p&gt;

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

&lt;p&gt;Essentially I modified:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;tt&gt;opendaylight-port-types@2013-09-25.yang&lt;/tt&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;tt&gt;openflow-action@2015-02-03.yang&lt;/tt&gt;{{}}&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;&lt;span class=&quot;nobr&quot;&gt;&lt;a href=&quot;mailto:openflow-instruction@2013-07-31.yang&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;openflow-instruction@2013-07-31.yang&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;&lt;br/&gt;
{{}}&lt;/li&gt;
&lt;/ul&gt;


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

&lt;p&gt;&lt;tt&gt;And my diff:&lt;/tt&gt;&lt;/p&gt;

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

&lt;p&gt;&lt;tt&gt;&#160;diff --git a/box/rmbn-yang/src/main/yang/opendaylight-port-types@2013-09-25.yang b/box/rmbn-yang/src/main/yang/opendaylight-port-types@2013-09-25.yang&lt;/tt&gt;&lt;br/&gt;
{{ index fa6e1fc..53f00c5 100644}}&lt;br/&gt;
{{ &#8212; a/box/rmbn-yang/src/main/yang/opendaylight-port-types@2013-09-25.yang}}&lt;br/&gt;
{{ +++ b/box/rmbn-yang/src/main/yang/opendaylight-port-types@2013-09-25.yang}}&lt;br/&gt;
{{ @@ -193,6 +193,7 @@ module opendaylight-port-types {}}&lt;br/&gt;
{{ augment &quot;/multipart:multipart-reply/multipart:multipart-reply-body&quot; {}}&lt;br/&gt;
{{ case multipart-reply-port-desc {}}&lt;br/&gt;
{{ list ports}}{{&lt;/p&gt;
{ + key &quot;name&quot;; uses flow-capable-port; }
&lt;p&gt;}}&lt;tt&gt;}&lt;/tt&gt;&lt;br/&gt;
{{ diff --git a/box/rmbn-yang/src/main/yang/openflow-action@2015-02-03.yang b/box/rmbn-yang/src/main/yang/openflow-action@2015-02-03.yang}}&lt;br/&gt;
{{ index d2ae42f..25abff6 100644}}&lt;br/&gt;
{{ &#8212; a/box/rmbn-yang/src/main/yang/openflow-action@2015-02-03.yang}}&lt;br/&gt;
{{ +++ b/box/rmbn-yang/src/main/yang/openflow-action@2015-02-03.yang}}&lt;br/&gt;
{{ @@ -30,6 +30,7 @@}}&lt;tt&gt;grouping actions-grouping {&lt;/tt&gt;&lt;br/&gt;
{{ list action {}}&lt;br/&gt;
{{ + key &quot;experimenter-id&quot;;}}&lt;br/&gt;
{{ uses action-grouping;}}&lt;br/&gt;
{{ leaf experimenter-id {}}&lt;br/&gt;
{{ type oft:experimenter-id;}}&lt;br/&gt;
{{ diff --git a/box/rmbn-yang/src/main/yang/openflow-instruction@2013-07-31.yang b/box/rmbn-yang/src/main/yang/openflow-instruction@2013-07-31.yang}}&lt;br/&gt;
{{ index b9e515b..1dfdd14 100644}}&lt;br/&gt;
{{ &#8212; a/box/rmbn-yang/src/main/yang/openflow-instruction@2013-07-31.yang}}&lt;br/&gt;
{{ +++ b/box/rmbn-yang/src/main/yang/openflow-instruction@2013-07-31.yang}}&lt;br/&gt;
{{ @@ -23,6 +23,7 @@}}&lt;tt&gt;grouping instructions-grouping {&lt;/tt&gt;&lt;br/&gt;
{{ list instruction {}}&lt;br/&gt;
{{ + key &quot;experimenter-id&quot;;}}&lt;br/&gt;
{{ config false;}}&lt;br/&gt;
{{ uses instruction-grouping;}}&lt;br/&gt;
{{ leaf experimenter-id {}}&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="68905" author="rovarga" created="Wed, 16 Dec 2020 21:32:34 +0000"  >&lt;p&gt;can you create a separate issue for this, with the attached patch, please?&lt;/p&gt;</comment>
                            <comment id="68907" author="rovarga" created="Wed, 16 Dec 2020 21:43:41 +0000"  >&lt;p&gt;The pyang error is expected: OpenDaylight&apos;s LogicalDatastoreType.CONFIGURATION is more flexible.&lt;/p&gt;

&lt;p&gt;It comes from pyang&apos;s strict reading of RFC6020/7950 when &apos;config&apos; is involved &#8211; it effectively expresses what is a datastore policy for those nodes. RFC8342 fixes this and pyang needs to adapt.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="33217">OPNFLWPLUG-1104</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03uqv:</customfieldvalue>

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