<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:14:16 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-144] Documentation needed for device reconnect based on schema change</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-144</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;When Beryllium is started (without additional features in featuresBoot), then feature:install odl-netconf-connector-all and then feature:install another feature (for example odl-bgpcep-bgp), this is seen in karaf.log:&lt;/p&gt;

&lt;p&gt;2016-02-09 10:41:03,007 | INFO  | oupCloseable-6-1 | NetconfDevice                    | 182 - org.opendaylight.netconf.sal-netconf-connector - 1.3.0.SNAPSHOT | RemoteDevice&lt;/p&gt;
{controller-config}: Schemas change detected, reconnecting&lt;br/&gt;
2016-02-09 10:41:03,011 | WARN  | oupCloseable-6-1 | NetconfDeviceCommunicator        | 182 - org.opendaylight.netconf.sal-netconf-connector - 1.3.0.SNAPSHOT | RemoteDevice{controller-config}
&lt;p&gt;: Session went down&lt;br/&gt;
java.io.IOException: End of input detected. Close the session.&lt;/p&gt;

&lt;p&gt;The connection seem to re-establish successfully, but there is a brief period when controller-config device fails on any operation. This behavior is relevant for csit tests, suites should retry the operation as in this specific case failure is not an error.&lt;/p&gt;

&lt;p&gt;There needs to be a wikipage explaining this behavior, so that test developers are informed.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21157">NETCONF-144</key>
            <summary>Documentation needed for device reconnect based on schema change</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="JMorvay">Jakub Morvay</assignee>
                                    <reporter username="vrpolak">Vratko Polak</reporter>
                        <labels>
                    </labels>
                <created>Tue, 9 Feb 2016 10:56:29 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:20 +0000</updated>
                            <resolved>Mon, 1 Oct 2018 16:22:42 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="39179" author="vrpolak" created="Wed, 10 Feb 2016 13:51:05 +0000"  >&lt;p&gt;&amp;gt; there is a brief period when controller-config device fails on any operation.&lt;/p&gt;

&lt;p&gt;I have seen jobs actually stuck on such operation, waiting for hours.&lt;br/&gt;
Not sure whether the re-connection described in this Bug is the reason though.&lt;/p&gt;</comment>
                            <comment id="65119" author="jmorvay" created="Mon, 1 Oct 2018 16:22:42 +0000"  >&lt;p&gt;config subsytem was removed completely, there is no point in creating loopback connection to CSS netconf server endpoint. This issue is no longer valid.&lt;/p&gt;</comment>
                    </comments>
                    <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>5281</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=5281]]></customfieldvalue>

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

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

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