<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:14:24 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-193] Netconf connectors unreadable due to &quot;data model content does not exist&quot;</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-193</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;Observed on: Boron, &quot;only&quot;, with suite &quot;netconfready.robot&quot;&lt;/p&gt;

&lt;p&gt;If content of any Netconf connectors (or the list of Netconf connectors) is requersted (URIs under &quot;restconf/config/network-topology:network-topology/topology/topology-netconf&quot;), the received response is always the following error: &quot;Request could not be completed because the relevant data model content does not exist&quot;. What is strange is that creating or deleting Netconf connectors appears to work (received response code is of the 2xx variety).&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21206">NETCONF-193</key>
            <summary>Netconf connectors unreadable due to &quot;data model content does not exist&quot;</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="10002">Duplicate</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="jbehran@cisco.com">Jozef Behran</reporter>
                        <labels>
                    </labels>
                <created>Tue, 3 May 2016 08:22:36 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:23 +0000</updated>
                            <resolved>Thu, 2 Jun 2016 12:23:35 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="39350" author="jbehran@cisco.com" created="Tue, 3 May 2016 09:14:53 +0000"  >&lt;p&gt;After a better look at the test results it turns out that this is most likely a &quot;ODL boot performance&quot; problem. Namely, further down there is a CRUD suite which can access the netconf connectors just fine.&lt;/p&gt;</comment>
                            <comment id="39351" author="jbehran@cisco.com" created="Thu, 5 May 2016 13:41:47 +0000"  >&lt;p&gt;It turns out that this is not an &quot;ODL performance problem&quot;. The CRUD suite after the failed Netconf readiness did not report any failed tests (which caused me to suspect that the ODL boot performance is to be blamed). So I tried to increased the netconf boot wait timeout to 15 minutes and it still fails. The conclusion is that this seems to be one of these &quot;Netconf looks to be broken until first used&quot; bugs that disappear on first use (in this case Netconf fixes itself after a device is configured and connected).&lt;/p&gt;</comment>
                            <comment id="39352" author="vrpolak" created="Thu, 26 May 2016 15:20:58 +0000"  >&lt;p&gt;Is there any symptom of this bug not covered by &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-211&quot; title=&quot;Subtree filter does not return any data&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-211&quot;&gt;&lt;del&gt;NETCONF-211&lt;/del&gt;&lt;/a&gt;?&lt;/p&gt;</comment>
                            <comment id="39353" author="jmorvay@cisco.com" created="Thu, 2 Jun 2016 12:23:35 +0000"  >&lt;p&gt;Suite &quot;netconfready.robot&quot; should work fine now. Closing this bug as this is duplicate of &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1514&quot; title=&quot;Request could not be completed because the relevant data model content does not exist&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1514&quot;&gt;&lt;del&gt;CONTROLLER-1514&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="26068">CONTROLLER-1514</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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5832</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=5832]]></customfieldvalue>

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

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