<!-- 
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-196] Boron: Clustered setup sometimes fails to boot with &quot;server is unhealthy&quot;</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-196</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;Sometimes the clustered setup fails to boot properly. Search in logs reveals numerous &quot;server is unhealthy&quot; messages. See attached file for an example.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21209">NETCONF-196</key>
            <summary>Boron: Clustered setup sometimes fails to boot with &quot;server is unhealthy&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="10001">Won&apos;t Do</resolution>
                                        <assignee username="JMorvay">Jakub Morvay</assignee>
                                    <reporter username="jbehran@cisco.com">Jozef Behran</reporter>
                        <labels>
                    </labels>
                <created>Tue, 17 May 2016 11:41:07 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:23 +0000</updated>
                            <resolved>Mon, 1 Oct 2018 14:58:24 +0000</resolved>
                                                                    <component>restconf-nb</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="39365" author="jbehran@cisco.com" created="Tue, 17 May 2016 11:41:07 +0000"  >&lt;p&gt;Attachment buggyrun.tgz has been added with description: Example of a failed cluster boot&lt;/p&gt;</comment>
                            <comment id="39362" author="rovarga" created="Tue, 17 May 2016 13:56:44 +0000"  >&lt;p&gt;I cannot see any such message in the attached logs. Can you provide the offending exception?&lt;/p&gt;</comment>
                            <comment id="39363" author="jbehran@cisco.com" created="Wed, 18 May 2016 08:02:10 +0000"  >&lt;p&gt;It turns out the original &quot;failed cluster boot&quot; attachment is not from the &quot;failed cluster boot&quot; runs at all (this is why it is now flagged as &quot;obsolete&quot;). Attached is the console outputs from the 2 test runs where this bug happened (the console output is all that was left). What is suspect is a &quot;NullPointerException: Null service reference is not allowed&quot; happening.&lt;/p&gt;</comment>
                            <comment id="39366" author="jbehran@cisco.com" created="Wed, 18 May 2016 08:02:10 +0000"  >&lt;p&gt;Attachment 5896.tgz has been added with description: The correct outputs from the 2 failed tests.&lt;/p&gt;</comment>
                            <comment id="39364" author="tpantelis" created="Wed, 15 Jun 2016 18:33:55 +0000"  >&lt;p&gt;restconf is failing to push:&lt;/p&gt;

&lt;p&gt;java.lang.NullPointerException: A null service reference is not allowed.&lt;br/&gt;
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.getService(BundleContextImpl.java:586)&lt;br/&gt;
	at org.opendaylight.restconf.rest.RestConnectorProvider.getObjectFromBundleContext(RestConnectorProvider.java:50)&lt;br/&gt;
	at org.opendaylight.restconf.rest.RestConnectorProvider.onSessionInitiated(RestConnectorProvider.java:37)&lt;br/&gt;
	at org.opendaylight.controller.sal.dom.broker.BrokerImpl.registerProvider(BrokerImpl.java:159)&lt;br/&gt;
	at org.opendaylight.RestconfWrapperProviders.registerProviders(RestconfWrapperProviders.java:63)&lt;br/&gt;
	at org.opendaylight.controller.config.yang.md.sal.rest.connector.RestConnectorModule.createInstance(RestConnectorModule.java:34)&lt;br/&gt;
	at org.opendaylight.controller.config.spi.AbstractModule.getInstance(AbstractModule.java:82)&lt;/p&gt;

&lt;p&gt;2016-05-17 11:08:49,554 | ERROR | config-pusher    | ConfigRegistryImpl               | 109 - org.opendaylight.controller.config-manager - 0.5.0.SNAPSHOT | Configuration Transaction failed on 2PC, server is unhealthy&lt;br/&gt;
java.lang.IllegalStateException: Error - getInstance() failed for ModuleIdentifier&lt;/p&gt;
{factoryName=&apos;rest-connector-impl&apos;, instanceName=&apos;rest-connector-default-impl&apos;}
&lt;p&gt; in transaction TransactionIdentifier&lt;/p&gt;
{name=&apos;ConfigTransaction-73-75&apos;}


&lt;p&gt;This doesn&apos;t look related to clustering. This bug should be moved to the netconf project.&lt;/p&gt;</comment>
                            <comment id="65107" author="jmorvay" created="Mon, 1 Oct 2018 14:58:24 +0000"  >&lt;p&gt;From the attached logs and log snippet mentioned by Tom P. it looks like this is related to config subsystem. Config subsystem is not supported nor present anymore.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="12670" name="5896.tgz" size="92965" author="jbehran@cisco.com" created="Wed, 18 May 2016 08:02:10 +0000"/>
                            <attachment id="12669" name="buggyrun.tgz" size="151825" author="jbehran@cisco.com" created="Tue, 17 May 2016 11:41:07 +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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5896</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=5896]]></customfieldvalue>

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

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