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/AAA-126 aaa <p>2017-05-04 14:13:27,606 | ERROR | rint Extender: 3 | BlueprintContainerImpl | 11 - org.apache.aries.blueprint.core - 1.7.1 | Unable to start blueprint container for bundle org.opendaylight.aaa.idmlight/0.5.0.SNAPSHOT due to unresolved dependencies <span class="error">&#91;(objectClass=org.opendaylight.aaa.api.IIDMStore)&#93;</span><br/> java.util.concurrent.TimeoutException<br/> at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:371)<span class="error">&#91;11:org.apache.aries.blueprint.core:1.7.1&#93;</span><br/> at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)<span class="error">&#91;11:org.apache.aries.blueprint.core:1.7.1&#93;</span><br/> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:266)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.lang.Thread.run(Thread.java:745)<span class="error">&#91;:1.8.0_121&#93;</span></p> <p>Operating System: All<br/> Platform: All</p> AAA-126

Unable to start blueprint container for bundle org.opendaylight.aaa.idmlight

Bug Verified Done Andrej Mak Ivan Hrasko Thu, 4 May 2017 12:35:54 +0000 Thu, 21 Mar 2019 11:56:48 +0000 Tue, 9 May 2017 05:40:19 +0000 General 0 6 <p>This blocks 8364.</p> <p>After second installation of odl-restconf feature aaa is not initialized again.</p> <p>Only on second installation of odl-restconf?</p> <p>I suspect that this is basically that idmlight doesn't handle being reloaded well, and that Karaf 4's default lifecycle management is reloading when later features are installed because they include aaa (transitively?) and don't use dependency=true in the inclusion.</p> <p>See: <a href="https://lists.opendaylight.org/pipermail/release/2017-May/010691.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/release/2017-May/010691.html</a></p> <p>That being said, I don't have a great way to test it. I think Lori (now cc'ed on the bug) is also seeing this though.</p> <p>I just encountered this bug yesterday. I built integration/distribution and started karaf. The container comes up with just the basic karaf features, no Opendaylight features, as expected. I loaded odl-lispflowmapping-msmr manually from the console. Things work well for southbound only operations. When I try to use RESTCONF, on the client side I get 401 unauthorized, and the karaf console throws this excpetion:</p> <p>2017-05-04 06:37:04,085 | ERROR | rint Extender: 1 | BlueprintContainerImpl | 11 - org.apache.aries.blueprint.core - 1.7.1 | Unable to start blueprint container for bundle org.opendaylight.aaa.idmlight/0.5.0.SNAPSHOT due to unresolved dependencies <span class="error">&#91;(objectClass=org.opendaylight.aaa.api.IIDMStore)&#93;</span><br/> java.util.concurrent.TimeoutException<br/> at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:371)<span class="error">&#91;11:org.apache.aries.blueprint.core:1.7.1&#93;</span><br/> at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)<span class="error">&#91;11:org.apache.aries.blueprint.core:1.7.1&#93;</span><br/> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)<span class="error">&#91;:1.8.0_131&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:266)<span class="error">&#91;:1.8.0_131&#93;</span><br/> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)<span class="error">&#91;:1.8.0_131&#93;</span><br/> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)<span class="error">&#91;:1.8.0_131&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)<span class="error">&#91;:1.8.0_131&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)<span class="error">&#91;:1.8.0_131&#93;</span><br/> at java.lang.Thread.run(Thread.java:748)<span class="error">&#91;:1.8.0_131&#93;</span></p> <p>I have also seen this error intermittently failing odl-vbd-distribution in Nitrogen. E.g: <a href="https://logs.opendaylight.org/releng/jenkins092/vbd-distribution-check-nitrogen/23/console.log.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/vbd-distribution-check-nitrogen/23/console.log.gz</a></p> <p>"2017-05-02 17:06:42,391 | ERROR | rint Extender: 1 | BlueprintContainerImpl | 69 - org.apache.aries.blueprint.core - 1.7.1 | Unable to start blueprint container for bundle org.opendaylight.aaa.idmlight/0.6.0.SNAPSHOT due to unresolved dependencies <span class="error">&#91;(objectClass=org.opendaylight.aaa.api.IIDMStore)&#93;</span><br/> java.util.concurrent.TimeoutException<br/> at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:371)<span class="error">&#91;69:org.apache.aries.blueprint.core:1.7.1&#93;</span><br/> at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)<span class="error">&#91;69:org.apache.aries.blueprint.core:1.7.1&#93;</span><br/> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:266)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)<span class="error">&#91;:1.8.0_121&#93;</span><br/> at java.lang.Thread.run(Thread.java:745)<span class="error">&#91;:1.8.0_121&#93;</span>"</p> <p>Not sure if this is correct solution, but we can set destroy method for blueprint container, which closes its resources.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/56543/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/56543/</a></p> <p>Not sure that fixes this issue, but I merged since it was definitely needed either way. Anyone still seeing this?</p> <p>It looks to be fixed.</p> <p>Awesome, thanks Ivan and Andrej. Please switch to "Verified" if this has been verified fixed.</p> <p>I have verified that problem was fixed.</p> Blocks NETCONF-358 NETCONF-416 Development External issue ID 8373 External issue URL Rank 0|i0249b: