https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/CONTROLLER-1613 controller <p>The first symptom detected by Robot suites is constant 404 on jolokia URL. This Carbon bug does not happen in <del>only</del> jobs. This weekend it hit both Netconf and Controller jobs, previously this was only seen once <span class="error">&#91;0&#93;</span>.</p> <p>Karaf.log for this Bug contains reports on runtime-generated-mapping not finishing, followed by "giving up" from AbstractDataStore:</p> <p>2017-02-26 04:02:37,092 | WARN | saction-32-34'}} | DeadlockMonitor | 131 - org.opendaylight.controller.config-manager - 0.6.0.SNAPSHOT | ModuleIdentifier</p> {factoryName='runtime-generated-mapping', instanceName='runtime-mapping-singleton'} <p> did not finish after 169982 ms<br/> 2017-02-26 04:02:40,606 | ERROR | Event Dispatcher | AbstractDataStore | 216 - org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT | Shard leaders failed to settle in 90 seconds, giving up</p> <p>Possibly this is just a performance Bug (startup taking longer than expected), but when the restart succeeds <span class="error">&#91;1&#93;</span>, the instance is created in around 10 seconds. Most probably some ODL project tends to make WaitingServiceTracker not find BindingToNormalizedNodeCodec.</p> <p><span class="error">&#91;0&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/controller/job/controller-csit-3node-clustering-all-carbon/221/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/controller/job/controller-csit-3node-clustering-all-carbon/221/</a><br/> <span class="error">&#91;1&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-carbon/199/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-carbon/199/</a></p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1613

Clustering: Member fails to re-start sometimes in csit -all- jobs

Bug Resolved Cannot Reproduce Andrej Mak Vratko Polak Mon, 27 Feb 2017 13:59:11 +0000 Tue, 25 Jul 2023 08:24:25 +0000 Mon, 10 Apr 2017 13:49:14 +0000 clustering 0 4 <p>Is this still present?</p> <p>&gt; Is this still present?</p> <p>Yes, this still affects around half of netconf <span class="error">&#91;2&#93;</span> runs. Both 404 in robot <span class="error">&#91;3&#93;</span> and "giving up" in karaf.log <span class="error">&#91;4&#93;</span> are there.</p> <p><span class="error">&#91;2&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-carbon/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-carbon/</a><br/> <span class="error">&#91;3&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/222/archives/log.html.gz#s1-s6-t14-k2-k2-k5-k1-k2-k1-k1-k2-k1-k4-k5" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/222/archives/log.html.gz#s1-s6-t14-k2-k2-k5-k1-k2-k1-k1-k2-k1-k4-k5</a><br/> <span class="error">&#91;4&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/222/archives/odl2_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-carbon/222/archives/odl2_karaf.log.gz</a></p> <p>Seems like the underlying cause is that the rejoining node could not rejoin the cluster</p> <p>2017-03-27 08:54:01,343 | WARN | ult-dispatcher-5 | JoinSeedNodeProcess | 155 - com.typesafe.akka.slf4j - 2.4.17 | Couldn't join seed nodes after <span class="error">&#91;15&#93;</span> attmpts, will try again. seed-nodes=<span class="error">&#91;akka.tcp://opendaylight-cluster-data@10.29.12.12:2550, akka.tcp://opendaylight-cluster-data@10.29.13.54:2550&#93;</span></p> <p>these are all over the logs which explains the shard not being able to elect a leader. Now why cant the node rejoin? is it possible that there is an environment issue or an issue with the rejoin script?</p> <p>&gt; is it possible that there is an environment issue or an issue with the rejoin script?</p> <p>Unlikely. The suite is the same as in <del>only</del> job <span class="error">&#91;5&#93;</span>, where it passes.</p> <p><span class="error">&#91;5&#93;</span> <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-only-carbon" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-only-carbon</a></p> <p>Last runs of <a href="https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-carbon/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-all-carbon/</a> passed, so issue seems to be resolved for now.</p> Development External issue ID 7858 External issue URL Issue Type Rank 0|i02rnj: