OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[ODLPARENT-86] Milestore: upgrade karaf to 4.1.2 or later https://jira.opendaylight.org/browse/ODLPARENT-86 odlparent <p>This is the next step in the catch-up game. Required to upgrade SSH to newer versions.</p> <p>Operating System: All<br/> Platform: All</p> ODLPARENT-86

Milestore: upgrade karaf to 4.1.2 or later

Bug Verified Done Stephen Kitt Robert Varga Thu, 20 Apr 2017 09:23:47 +0000 Wed, 24 Jan 2018 14:27:06 +0000 Wed, 24 Jan 2018 14:07:21 +0000 3.0.0 General 0 1 <p>I guess the upgrade will also speed up ODL boot-up process, as described here <span class="error">[0]</span>?</p> <p>I am not sure if there is an open Bug for ODL being slow to boot (as opposed to invalid claims it gets stuck), so I will list this Bug as a known issue for Integration/Distribution Nitrogen release notes.</p> <p><span class="error">[0]</span> <a href="https://lists.opendaylight.org/pipermail/odlparent-dev/2017-September/001336.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/odlparent-dev/2017-September/001336.html</a></p> <p>It will not, but it will speed up feature.xml generation at build time. Boot up speed improvement will require more work on our side – <a href="https://jira.opendaylight.org/browse/MDSAL-235" title="[INFO] Failed to fully assemble schema context for [...]" class="issue-link" data-issue-key="MDSAL-235"><del>MDSAL-235</del></a> tracks that.</p> <p>(In reply to Robert Varga from comment #2)<br/> > It will not, but it will speed up feature.xml generation at build time. Boot<br/> > up speed improvement will require more work on our side – <a href="https://jira.opendaylight.org/browse/MDSAL-235" title="[INFO] Failed to fully assemble schema context for [...]" class="issue-link" data-issue-key="MDSAL-235"><del>MDSAL-235</del></a> tracks<br/> > that.</p> <p>I do not agree.<br/> If you look into a short-ish karaf log <span class="error">[1]</span> from CSIT you see this:</p> <p>Sep 09, 2017 11:46:52 PM org.apache.karaf.main.Main$KarafLockCallback lockAquired<br/> INFO: Lock acquired. Setting startlevel to 100<br/> 2017-09-09 23:50:33,158 | INFO | pool-1-thread-2 | FeaturesServiceImpl | 6 - org.apache.karaf.features.core - 4.0.9 | Adding features: odl-integration-all/<span class="error">[0.7.0.SNAPSHOT,0.7.0.SNAPSHOT]</span>, standard/<span class="error">[4.0.9,4.0.9]</span>, wrap/<span class="error">[0,0.0.0]</span></p> <p>That is almost 4 minutes to figure out list of bundles to be installed. No chance schema context refreshes apply to that.<br/> Although it is an <del>all</del> job, so the list of bundles is quite long.</p> <p>But when I was fixing <span class="error">[2]</span> the offline job (mostly because of <a href="https://jira.opendaylight.org/browse/ODLPARENT-113" title="After hard reset, Robot fails to establish SSH connection to karaf" class="issue-link" data-issue-key="ODLPARENT-113"><del>ODLPARENT-113</del></a>), I had to add a waiting loop. The result is seen <span class="error">[3]</span> only on Sandbox so far, but it takes almost the same time for the native Karaf ssh server to start responding when there are no ODL features in featuresBoot. The offline job uses feature:install to add the feature to test (odl-integration-all).<br/> I guess the Karaf core was sifting through system/ repository in an ineffective <br/> way.</p> <p>2017-09-13 15:29:41,785 | INFO | bd4-8e1eaa0a7feb | Main | - - | Karaf started in 0s. Bundle stats: 10 active, 10 total<br/> 2017-09-13 15:34:01,050 | INFO | pool-1-thread-2 | FeaturesServiceImpl | 6 - org.apache.karaf.features.core - 4.0.9 | Adding features: standard/<span class="error">[4.0.9,4.0.9]</span>, wrap/<span class="error">[0,0.0.0]</span></p> <p>Does Karaf project need another contribution to avoid that? Should I open a separate ODL Bug?</p> <p><span class="error">[1]</span> <a href="https://logs.opendaylight.org/releng/jenkins092/distribution-deploy-nitrogen/46/karaf.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/distribution-deploy-nitrogen/46/karaf.log.gz</a><br/> <span class="error">[2]</span> <a href="https://git.opendaylight.org/gerrit/62903" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/62903</a><br/> <span class="error">[3]</span> <a href="https://jenkins.opendaylight.org/sandbox/job/distribution-offline-nitrogen/5/console" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/distribution-offline-nitrogen/5/console</a></p> <p>> Should I open a separate ODL Bug?</p> <p><a href="https://jira.opendaylight.org/browse/ODLPARENT-115" title="Karaf is slow to start processing features after start" class="issue-link" data-issue-key="ODLPARENT-115"><del>ODLPARENT-115</del></a> opened.</p> <p>Preliminary patch: <a href="https://git.opendaylight.org/gerrit/63272" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/63272</a></p> <p>This is blocking JDK9 build, as karaf-maven-plugin 4.0.9 fails on JDK9:</p> <p>org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.0.9:assembly (process-resources) on project opendaylight-karaf-resources: Unable to build assembly<br/> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)<br/> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)<br/> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)<br/> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)<br/> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)<br/> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)<br/> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)<br/> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)<br/> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)<br/> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)<br/> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)<br/> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)<br/> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)<br/> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br/> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)<br/> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<br/> at java.base/java.lang.reflect.Method.invoke(Method.java:564)<br/> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)<br/> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)<br/> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)<br/> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)<br/> Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to build assembly<br/> at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:243)<br/> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)<br/> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)<br/> ... 20 more<br/> Caused by: org.apache.karaf.features.internal.util.MultiException: Error<br/> at org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader.<init>(MavenDownloadManager.java:84)<br/> at org.apache.karaf.features.internal.download.impl.MavenDownloadManager.createDownloader(MavenDownloadManager.java:72)<br/> at org.apache.karaf.profile.assembly.Builder.loadRepositories(Builder.java:1167)<br/> at org.apache.karaf.profile.assembly.Builder.doGenerateAssembly(Builder.java:448)<br/> at org.apache.karaf.profile.assembly.Builder.generateAssembly(Builder.java:393)<br/> at org.apache.karaf.tooling.AssemblyMojo.doExecute(AssemblyMojo.java:401)<br/> at org.apache.karaf.tooling.AssemblyMojo.execute(AssemblyMojo.java:237)<br/> ... 22 more<br/> Suppressed: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException<br/> at org.apache.karaf.profile.assembly.Builder$4.downloaded(Builder.java:1184)<br/> at org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader$1.operationComplete(MavenDownloadManager.java:133)<br/> at org.apache.karaf.features.internal.download.impl.MavenDownloadManager$MavenDownloader$1.operationComplete(MavenDownloadManager.java:127)<br/> at org.apache.karaf.features.internal.download.impl.DefaultFuture.notifyListener(DefaultFuture.java:344)<br/> at org.apache.karaf.features.internal.download.impl.DefaultFuture.notifyListeners(DefaultFuture.java:329)<br/> at org.apache.karaf.features.internal.download.impl.DefaultFuture.setValue(DefaultFuture.java:255)<br/> at org.apache.karaf.features.internal.download.impl.AbstractDownloadTask.setFile(AbstractDownloadTask.java:61)<br/> at org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:61)</p> <p>According to <a href="https://issues.apache.org/jira/browse/KARAF-5029" class="external-link" target="_blank" rel="nofollow noopener">https://issues.apache.org/jira/browse/KARAF-5029</a>, 4.1.x branch should solve this.</p> Blocks MDSAL-235 NETCONF-242 ODLPARENT-113 ODLPARENT-119 INFRAUTILS-11 ODLPARENT-115 ODLPARENT-23 Development External issue ID 8258 External issue URL Issue Type ODL SR Target Milestone Rank 0|i0237z: