Previous story: [2]. > who would have to do what
Ideally, Netconf developers would unify their features, which does not seem to get done anytime soon [3]. There is a workaround in Int/Dist [4] prepared, but it keeps SFT unstable, this time due to (lack of) Karaf 4 memory efficiency [5]. Current road to stability seem to be fixing various ODL project features (like [6]) to be less taxing on Karaf 4 bundle resolver, and then merging [4]. > It would be nice if the exception included some context like the path. I have rebased my old [7]. In this case, it is multiple netconf features trying to update operational topology status for "controller-config" device. > How does SFT even pick this up to fail the test? In general, a "caused by" thrown by featuresService.installFeature. In this case there was an ISE (visible in surefire report [8] at 12:27:25,742) coming from here [9] (at least in Nitrogen), not sure which component gets to throw it. Vratko. [2] https://lists.opendaylight.org/pipermail/release/2017-October/012728.html [3] https://jira.opendaylight.org/browse/NETCONF-479 [4] https://git.opendaylight.org/gerrit/64410 [5] https://jira.opendaylight.org/browse/ODLPARENT-125 [6] https://jira.opendaylight.org/browse/INTDIST-92 [7] https://git.opendaylight.org/gerrit/48118 [8] https://logs.opendaylight.org/releng/jenkins092/infrautils-distribution-check-oxygen/144/distribution/features/singles/odl-integration-compatible-with-all/target/surefire-reports/org.opendaylight.odlparent.featuretest.SingleFeatureTest-output.txt.gz [9] https://github.com/opendaylight/netconf/blob/release/nitrogen/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/sal/NetconfDeviceTopologyAdapter.java#L243 From: controller-dev-boun...@lists.opendaylight.org [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Tom Pantelis Sent: 23 October, 2017 15:24 To: Michael Vorburger <vorbur...@redhat.com> Cc: controller-dev <controller-dev@lists.opendaylight.org> Subject: Re: [controller-dev] SingleFeatureTest (SFT) failure on odl-integration-compatible-with-all due to ConflictingModificationAppliedException: Node was created by other transaction. On Mon, Oct 23, 2017 at 8:41 AM, Michael Vorburger <vorbur...@redhat.com<mailto:vorbur...@redhat.com>> wrote: Hello, Any idea who would have to do what to precent SFT from (only occassionally?!) failing on odl-integration-compatible-with-all due to ConflictingModificationAppliedException: Node was created by other transaction, as seen on https://logs.opendaylight.org/releng/jenkins092/infrautils-distribution-check-oxygen/144/console.log.gz for https://git.opendaylight.org/gerrit/#/c/63466/ ? It would be nice if the exception included some context like the path. Does this test install all netconf features? I've seen such sporadic issues with the callhome feature when it's installed with all the other netconf features. How does SFT even pick this up to fail the test? Log scraping? Or was it a "caused by" thrown on blueprint startup? Tx, M. -- Michael Vorburger, Red Hat vorbur...@redhat.com<mailto:vorbur...@redhat.com> | IRC: vorburger @freenode | ~ = http://vorburger.ch<http://vorburger.ch/> _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org> https://lists.opendaylight.org/mailman/listinfo/controller-dev
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
