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-1928 controller <p>This recent fix patch:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/controller/+/87043/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/controller/+/87043/</a></p> <p>Produced regression in these 2 cluster tests:</p> <p>1) <a href="https://jenkins.opendaylight.org/releng/job/controller-csit-3node-rest-clust-cars-perf-ask-only-sodium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/controller-csit-3node-rest-clust-cars-perf-ask-only-sodium/</a><br/> Cars performance test: 10K cars are configured in a cluster, the leader is isolated from the cluster, when new leader is elected, cars are verified in the new leader. This test fails because not all cars are seen in the new leader.</p> <p>2) <a href="https://jenkins.opendaylight.org/releng/job/controller-csit-1node-akka1-all-sodium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/job/controller-csit-1node-akka1-all-sodium/</a><br/> Upgrade test: A single controller is loaded with old SW (Carbon in the test) and some configuration, after that the node is shutdown and the data (snapshots folder) is transfered to a new SW (Sodium SR2) controller. The new controller fails to boot up and there are GC and OOM errors in the karaf.log.</p> CONTROLLER-1928

Regression detected in CSIT

Bug Highest Resolved Done Tomas Cere Luis Gomez Thu, 30 Jan 2020 01:00:38 +0000 Wed, 5 Feb 2020 19:23:00 +0000 Wed, 5 Feb 2020 15:14:53 +0000 Magnesium Sodium SR2 Magnesium Sodium SR2 clustering 0 3 <p>Candidate fix seems to work fine and addresses the first regression, however I still see problems in the second (upgrade) test. Even when I try to upgrade from Sodium SR1, and even when I run the "only" test, controller fails to boot up:<br/> <a href="https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-1node-akka1-all-sodium/478/odl_1/odl1_karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-1node-akka1-all-sodium/478/odl_1/odl1_karaf.log.gz</a></p> <p>Any idea why it is failing?</p> <p>Is it possible to grab the Carbon snapshot somewhere so I can try it out locally?</p> <p>as <a href="https://lists.opendaylight.org/g/controller-dev/message/14958" class="external-link" target="_blank" rel="nofollow noopener">reported here</a> I saw an OOM/GC crash when doing a simple<br/> netconf test to mount 10 devices. Each device has a relatively large yang schema. The test was done using the revert patch<br/> (87277) but now re-reading the comments here I realize it probably was not intended to fix the 2nd issue described (OOM).</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=tcere" class="user-hover" rel="tcere">tcere</a> I tried the CSIT test with several distributions, in theory the test should be using the previous ODL release (Sodium SR1) but I figured it is broken and uses old Carbon instead. Anyway, this is the ink if you want to download ODL distros: <a href="https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/karaf/" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/integration/karaf/</a></p> <p>That seems probably unrelated to this problem so lets:</p> <p>1) Wait for next RC CSIT results to confirm there is no issues with the revert.<br/> 2) Dig more into your issue, like is it present in Sodium SR1 or master?</p> <p>for the OOM/GC crash I am seeing with my one-off netconf mount test, I also see it in SR1. so, although likely a very<br/> serious bug, it's not a regression. I have filed a <a href="https://jira.opendaylight.org/browse/NETCONF-655" class="external-link" rel="nofollow">new jira </a> for this issue and we can discuss there if we would<br/> want to block SR2 on it or let it go since it's not exactly a regression. Not exactly, because it was not there in the<br/> original/first Sodium release.</p> Relates CONTROLLER-1927 Development Rank 0|i03qz3: