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/DAEXIM-11 daexim <p>Looking at the daily stable CI jobs (<a href="https://jenkins.opendaylight.org/releng/view/csit-stable-f/)" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/csit-stable-f/)</a> we observed that the daexim-csit-3node-clustering-basic-only-fluorine had a number of failures:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/csit-stable-f/job/daexim-csit-3node-clustering-basic-only-fluorine/249/robot/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/csit-stable-f/job/daexim-csit-3node-clustering-basic-only-fluorine/249/robot/</a></p> <p> </p> DAEXIM-11

CSIT blocker: daexim-csit-3node-clustering-basic-only-fluorine

Bug Highest Resolved Won't Do Shaleen Saxena Ariel Adam csit:stable:blocker Wed, 24 Oct 2018 07:58:20 +0000 Thu, 25 Oct 2018 05:25:09 +0000 Wed, 24 Oct 2018 19:27:15 +0000 0 3 <p>This looks to be an intermittent failure in cluster bring up.</p> <p>If this is a random failure appreciate if you could remove the failing tests or stabilize them. </p> <p>We need to reach a point where this subset always passes as a basis for a gate.</p> <p>Problem is definitely outside of daexim.</p> <p>Keyword "ClusterManagement .Start_Members_From_List_Or_All" fail to reach last node in cluster.</p> <p>There is nothing we can do about it other then disable failing test (but that will only hide real issue).</p> <p>Quick look at <a href="https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/daexim-csit-3node-clustering-basic-only-fluorine/249/odl_3/odl3_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/daexim-csit-3node-clustering-basic-only-fluorine/249/odl_3/odl3_karaf.log.gz</a></p> <p>shows:</p> <p>2018-10-23T03:06:37,040 | ERROR | opendaylight-cluster-data-akka.actor.default-dispatcher-40 | ActorSystemImpl                  | 43 - com.typesafe.akka.slf4j - 2.5.11 | Uncaught error from thread <span class="error">&#91;opendaylight-cluster-data-akka.actor.default-dispatcher-32&#93;</span>: org/w3c/dom/ElementTraversal, shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem<span class="error">&#91;opendaylight-cluster-data&#93;</span><br/> java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal</p> <p>which is similar to <a href="https://jira.opendaylight.org/browse/NETCONF-576" class="external-link" rel="nofollow">https://jira.opendaylight.org/browse/NETCONF-576</a></p> <p>In any case, we can't fix that in daexim.</p> <p> </p> <p> </p> <p> </p> <p>There is nothing to be done in daexim and problem is already tracked in <a href="https://jira.opendaylight.org/browse/CONTROLLER-1867" title="Cluster: Member fail to start with odl-netconf-clustered-topology feature " class="issue-link" data-issue-key="CONTROLLER-1867"><del>CONTROLLER-1867</del></a></p> <p>Appreciate the detailed answer.</p> <p>Will raise it today on the TSC call to decide how to progress.</p> <p>That fact that it's the same problem as in the netconf is a very important point. </p> Duplicate CONTROLLER-1867 Development Rank 0|i03jtb: