<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:26 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-1393] Controller config ReST call now reports non-existent mount point.</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1393</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;This URL is being used in system tests to determine that all necessary modules are up.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/controller-config/yang-ext:mount/config:module&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/config/opendaylight-inventory:nodes/node/controller-config/yang-ext:mount/config:module&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The tests are now failing because this is being returned:&lt;/p&gt;

&lt;p&gt;{&lt;br/&gt;
    &quot;errors&quot;: {&lt;br/&gt;
        &quot;error&quot;: [&lt;/p&gt;
            {
                &quot;error-type&quot;: &quot;protocol&quot;,
                &quot;error-tag&quot;: &quot;data-missing&quot;,
                &quot;error-message&quot;: &quot;Mount point does not exist.&quot;
            }
&lt;p&gt;        ]&lt;br/&gt;
    }&lt;br/&gt;
}&lt;/p&gt;

&lt;p&gt;The failure occurs on the master branch with controllers in single node and clustered configurations. The failure does not occur on the Lithium branch.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25947">CONTROLLER-1393</key>
            <summary>Controller config ReST call now reports non-existent mount point.</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="-1">Unassigned</assignee>
                                    <reporter username="phillip.shea@hp.com">Phillip Shea</reporter>
                        <labels>
                    </labels>
                <created>Thu, 16 Jul 2015 22:02:44 +0000</created>
                <updated>Thu, 19 Oct 2017 21:26:32 +0000</updated>
                            <resolved>Mon, 9 Nov 2015 10:40:31 +0000</resolved>
                                    <version>Beryllium</version>
                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                                                                <comments>
                            <comment id="50900" author="tcere" created="Fri, 17 Jul 2015 07:52:15 +0000"  >&lt;p&gt;This is fixed in: &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/24092/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/24092/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But it probably won&apos;t be merged until we finalize the move of netconf out of the controller project. In the meantime workaround is to install odl-aaa-netconf-plugin feature.&lt;/p&gt;</comment>
                            <comment id="50901" author="vrpolak" created="Wed, 5 Aug 2015 12:43:41 +0000"  >&lt;p&gt;I was under impression that netconf mounts (including controller-config) will cease to be present in opendaylight-inventory in Beryllium?&lt;/p&gt;

&lt;p&gt;Even if that is not case, I recommend to use this URL instead for Beryllium tests (also works for Lithium, but not for Helium).&lt;br/&gt;
&lt;a href=&quot;http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="50902" author="phillip.shea@hp.com" created="Mon, 31 Aug 2015 16:31:20 +0000"  >&lt;p&gt;I&apos;m bumping it back to confirmed. &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/24092/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/24092/&lt;/a&gt; did not fix the issue.&lt;/p&gt;</comment>
                            <comment id="50903" author="tcere" created="Thu, 10 Sep 2015 11:10:09 +0000"  >&lt;p&gt;Inventory code is now reintroduced in sal-netconf-connector(netconf repository).&lt;br/&gt;
The classes are still deprecated so they will probably be removed after Beryllium release so it would be a good time to start migrating towards the topology model as Vratko suggested.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/26710/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/26710/&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="25946">CONTROLLER-1392</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>4010</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=4010]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

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

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

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