<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:09:10 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[MDSAL-235] [INFO] Failed to fully assemble schema context for [...]</title>
                <link>https://jira.opendaylight.org/browse/MDSAL-235</link>
                <project id="10137" key="MDSAL">mdsal</project>
                    <description>&lt;p&gt;when running SingleFeatureTest (SFT) on a Karaf 4 feature, e.g. by &quot;mvn -o -Dsft.diag.skip=true clean install&quot; in genius/features/features4-genius from &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/51966/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/51966/&lt;/a&gt;,&lt;/p&gt;

&lt;p&gt;but I think completely unrelated to that change, and this happens even on Karaf 3 not just 4 and also in production instances, there are typically a lot of &quot;scary looking&quot; (because they have a stack trace..) INFO messages like the one below in the log.&lt;/p&gt;

&lt;p&gt;I&apos;m not aware of any actual issues - just sayin&apos; that this looks quite confusing, e.g. when you scan logs for other errors.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-298&quot; title=&quot;o.o.y.y.p.r.SharedSchemaContextFactory  - Failed to assemble sources org.opendaylight.yangtools.yang.model.repo.api.SchemaResolutionException&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-298&quot;&gt;&lt;del&gt;YANGTOOLS-298&lt;/del&gt;&lt;/a&gt; looks like it may be vaguely related.. should the level of this particular log perhaps be reduced from INFO to DEBUG? Or should it at least not log it&apos;s stack trace?&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;2017-03-08 00:14:14,824 | INFO | Framework stop | YangTextSchemaContextResolver | 244 - org.opendaylight.yangtools.yang-parser-impl - 1.1.0.SNAPSHOT | Failed to fully assemble schema context for [RevisionSourceIdentifier [name=config@2013-04-05], RevisionSourceIdentifier [n
 ame=rpc-context@2013-06-17], RevisionSourceIdentifier [name=netconf-node-inventory@2014-01-08], RevisionSourceIdentifier [name=opendaylight-inventory@2013-08-19], RevisionSourceIdentifier [name=opendaylight-topology-inventory@2013-10-30], RevisionSourceIdentifier [name=opendaylig
 ht-topology-view@2013-10-30], RevisionSourceIdentifier [name=opendaylight-topology@2013-10-30], RevisionSourceIdentifier [name=netty@2013-11-19], RevisionSourceIdentifier [name=netty-event-executor@2013-11-12], RevisionSourceIdentifier [name=threadgroup@2013-11-07], RevisionSourc
 eIdentifier [name=netty-timer@2013-11-19], RevisionSourceIdentifier [name=opendaylight-sal-binding-broker-impl@2013-10-28], RevisionSourceIdentifier [name=opendaylight-md-sal-binding-v1-codec@2016-07-14], RevisionSourceIdentifier [name=opendaylight-md-sal-binding@2013-10-28], Rev
 isionSourceIdentifier [name=cluster-admin-provider@2015-10-13], RevisionSourceIdentifier [name=actor-system-provider-service@2015-10-05], RevisionSourceIdentifier [name=general-entity@2015-08-20], RevisionSourceIdentifier [name=opendaylight-entity-ownership-service@2015-08-10], R
 evisionSourceIdentifier [name=actor-system-provider-impl@2015-10-05], RevisionSourceIdentifier [name=distributed-datastore-provider@2014-06-12], RevisionSourceIdentifier [name=entity-owners@2015-08-04], RevisionSourceIdentifier [name=odl-concurrent-data-broker-cfg@2014-11-24], Re
 visionSourceIdentifier [name=opendaylight-sal-dom-broker-impl@2013-10-28], RevisionSourceIdentifier [name=opendaylight-pingpong-broker@2014-11-07], RevisionSourceIdentifier [name=cluster-singleton-service-impl@2016-07-18], RevisionSourceIdentifier [name=cluster-singleton-service-
 spi@2016-07-18], RevisionSourceIdentifier [name=opendaylight-config-dom-datastore@2014-06-17], RevisionSourceIdentifier [name=opendaylight-legacy-entity-ownership-service-provider@2016-02-26], RevisionSourceIdentifier [name=opendaylight-md-sal-common@2013-10-28], RevisionSourceId
 entifier [name=opendaylight-md-sal-dom@2013-10-28], RevisionSourceIdentifier [name=opendaylight-operational-dom-datastore@2014-06-17], RevisionSourceIdentifier [name=opendaylight-inmemory-datastore-provider@2014-06-17], RevisionSourceIdentifier [name=shutdown@2013-12-18], Revisio
 nSourceIdentifier [name=shutdown-impl@2013-12-18], RevisionSourceIdentifier [name=threadpool@2013-04-09], RevisionSourceIdentifier [name=threadpool-impl-fixed@2013-12-01], RevisionSourceIdentifier [name=threadpool-impl-flexible@2013-12-01], RevisionSourceIdentifier [name=threadpo
 ol-impl-scheduled@2013-12-01], RevisionSourceIdentifier [name=threadpool-impl@2013-04-05], RevisionSourceIdentifier [name=odl-general-entity@2015-09-30], RevisionSourceIdentifier [name=iana-afn-safi@2013-07-04], RevisionSourceIdentifier [name=iana-if-type@2014-05-08], RevisionSou
 rceIdentifier [name=ietf-access-control-list@2016-02-18], RevisionSourceIdentifier [name=ietf-inet-types@2010-09-24], RevisionSourceIdentifier [name=ietf-inet-types@2013-07-15], RevisionSourceIdentifier [name=ietf-interfaces@2014-05-08], RevisionSourceIdentifier [name=ietf-networ
 k-topology@2015-06-08], RevisionSourceIdentifier [name=ietf-network@2015-06-08], RevisionSourceIdentifier [name=ietf-packet-fields@2016-02-18], RevisionSourceIdentifier [name=ietf-restconf@2013-10-19], RevisionSourceIdentifier [name=ted@2013-07-12], RevisionSourceIdentifier [name
 =ted@2013-10-21], RevisionSourceIdentifier [name=network-topology@2013-07-12], RevisionSourceIdentifier [name=network-topology@2013-10-21], RevisionSourceIdentifier [name=isis-topology@2013-07-12], RevisionSourceIdentifier [name=isis-topology@2013-10-21], RevisionSourceIdentifier
 [name=ospf-topology@2013-07-12], RevisionSourceIdentifier [name=ospf-topology@2013-10-21], RevisionSourceIdentifier [name=ietf-yang-types@2010-09-24], RevisionSourceIdentifier [name=ietf-yang-types@2013-07-15], RevisionSourceIdentifier [name=opendaylight-l2-types@2013-08-27], Re
 visionSourceIdentifier [name=yang-ext@2013-07-09], RevisionSourceIdentifier [name=openflow-action@2015-02-03], RevisionSourceIdentifier [name=openflow-approved-extensions@2016-08-02], RevisionSourceIdentifier [name=openflow-augments@2015-02-25], RevisionSourceIdentifier [name=ope
 nflow-configuration@2014-06-30], RevisionSourceIdentifier [name=openflow-extensible-match@2015-02-25], RevisionSourceIdentifier [name=openflow-instruction@2013-07-31], RevisionSourceIdentifier [name=openflow-protocol@2013-07-31], RevisionSourceIdentifier [name=openflow-types@2013
 -07-31], RevisionSourceIdentifier [name=system-notifications@2013-09-27], RevisionSourceIdentifier [name=openflow-switch-connection-provider-impl@2014-03-28], RevisionSourceIdentifier [name=openflow-switch-connection-config@2016-05-06], RevisionSourceIdentifier [name=openflow-swi
 tch-connection-provider@2014-03-28], RevisionSourceIdentifier [name=openflow-provider-impl@2014-03-26], RevisionSourceIdentifier [name=openflow-provider@2014-03-26], RevisionSourceIdentifier [name=openflow-provider-config@2016-05-10], RevisionSourceIdentifier [name=openflow-provi
 der@2015-03-31], RevisionSourceIdentifier [name=statistics-manager-control@2015-08-12], RevisionSourceIdentifier [name=forwarding-rules-manager-config@2016-05-11], RevisionSourceIdentifier [name=lldp-speaker-config@2016-05-12], RevisionSourceIdentifier [name=lldp-speaker@2014-10-
 23], RevisionSourceIdentifier [name=topology-lldp-discovery-config@2016-05-11], RevisionSourceIdentifier [name=openflowplugin-experimenter-types@2015-10-20], RevisionSourceIdentifier [name=openflowplugin-extension-general@2014-07-14], RevisionSourceIdentifier [name=openflowplugin
 -extension-registry@2015-04-25], RevisionSourceIdentifier [name=sal-experimenter-message@2015-10-20], RevisionSourceIdentifier [name=sal-experimenter-mp-message@2015-10-20], RevisionSourceIdentifier [name=openflow-plugin-provider-impl@2015-03-27], RevisionSourceIdentifier [name=o
 pendaylight-action-types@2013-11-12], RevisionSourceIdentifier [name=opendaylight-arbitrary-bitmask-fields@2016-01-30], RevisionSourceIdentifier [name=opendaylight-flow-types@2013-10-26], RevisionSourceIdentifier [name=opendaylight-group-types@2013-10-18], RevisionSourceIdentifie
 r [name=opendaylight-ipv6-arbitrary-bitmask-fields@2016-02-24], RevisionSourceIdentifier [name=opendaylight-match-types@2013-10-26], RevisionSourceIdentifier [name=opendaylight-meter-types@2013-09-18], RevisionSourceIdentifier [name=opendaylight-multipart-types@2017-01-12], Revis
 ionSourceIdentifier [name=opendaylight-port-types@2013-09-25], RevisionSourceIdentifier [name=opendaylight-queue-types@2013-09-25], RevisionSourceIdentifier [name=opendaylight-table-types@2013-10-26], RevisionSourceIdentifier [name=barrier-common@2016-03-15], RevisionSourceIdenti
 fier [name=batch-common@2016-03-22], RevisionSourceIdentifier [name=flow-capable-transaction@2015-03-04], RevisionSourceIdentifier [name=flow-errors@2013-11-16], RevisionSourceIdentifier [name=flow-node-inventory@2013-08-19], RevisionSourceIdentifier [name=flow-topology-discovery
 @2013-08-19], RevisionSourceIdentifier [name=node-config@2014-10-15], RevisionSourceIdentifier [name=node-error@2014-04-10], RevisionSourceIdentifier [name=packet-processing@2013-07-09], RevisionSourceIdentifier [name=sal-echo@2015-03-05], RevisionSourceIdentifier [name=sal-flat-
 batch@2016-03-21], RevisionSourceIdentifier [name=sal-flow@2013-08-19], RevisionSourceIdentifier [name=sal-flows-batch@2016-03-14], RevisionSourceIdentifier [name=sal-group@2013-09-18], RevisionSourceIdentifier [name=sal-groups-batch@2016-03-15], RevisionSourceIdentifier [name=sa
 l-meter@2013-09-18], RevisionSourceIdentifier [name=sal-meters-batch@2016-03-16], RevisionSourceIdentifier [name=sal-port@2013-11-07], RevisionSourceIdentifier [name=sal-queue@2015-03-05], RevisionSourceIdentifier [name=sal-role@2015-07-27], RevisionSourceIdentifier [name=sal-tab
 le@2013-10-26], RevisionSourceIdentifier [name=opendaylight-direct-statistics@2016-05-11], RevisionSourceIdentifier [name=opendaylight-flow-statistics@2013-08-19], RevisionSourceIdentifier [name=opendaylight-flow-table-statistics@2013-12-15], RevisionSourceIdentifier [name=openda
 ylight-group-statistics@2013-11-11], RevisionSourceIdentifier [name=opendaylight-meter-statistics@2013-11-11], RevisionSourceIdentifier [name=opendaylight-port-statistics@2013-12-14], RevisionSourceIdentifier [name=opendaylight-queue-statistics@2013-12-16], RevisionSourceIdentifi
 er [name=opendaylight-statistics-types@2013-09-25]]
 SchemaResolutionException{unsatisfiedImports={RevisionSourceIdentifier [name=isis-topology@2013-10-21]=[ModuleImportImpl [name=l3-unicast-igp-topology, revision=2013-10-21, semanticVersion=0.0.0]], RevisionSourceIdentifier [name=isis-topology@2013-07-12]=[ModuleImportImpl [name=l
 3-unicast-igp-topology, revision=2013-07-12, semanticVersion=0.0.0]], RevisionSourceIdentifier [name=ospf-topology@2013-10-21]=[ModuleImportImpl [name=l3-unicast-igp-topology, revision=2013-10-21, semanticVersion=0.0.0]], RevisionSourceIdentifier [name=ospf-topology@2013-07-12]=[
 ModuleImportImpl [name=l3-unicast-igp-topology, revision=2013-07-12, semanticVersion=0.0.0]]}}
 at org.opendaylight.yangtools.yang.parser.repo.SharedSchemaContextFactory$AssembleSources.apply(SharedSchemaContextFactory.java:203)
 at org.opendaylight.yangtools.yang.parser.repo.SharedSchemaContextFactory$AssembleSources.apply(SharedSchemaContextFactory.java:170)
 at com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:906)
 at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
 at com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
 at com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
 at com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
 at com.google.common.util.concurrent.Futures.transform(Futures.java:567)
 at org.opendaylight.yangtools.yang.parser.repo.SharedSchemaContextFactory.createSchemaContext(SharedSchemaContextFactory.java:104)
 at org.opendaylight.yangtools.yang.parser.repo.SharedSchemaContextFactory.createSchemaContext(SharedSchemaContextFactory.java:72)
 at org.opendaylight.yangtools.yang.model.repo.api.SchemaContextFactory.createSchemaContext(SchemaContextFactory.java:54)
 at org.opendaylight.yangtools.yang.parser.repo.YangTextSchemaContextResolver.getSchemaContext(YangTextSchemaContextResolver.java:220)
 at org.opendaylight.yangtools.yang.parser.repo.YangTextSchemaContextResolver.getSchemaContext(YangTextSchemaContextResolver.java:186)
 at org.opendaylight.mdsal.dom.broker.osgi.OsgiBundleScanningSchemaService.tryToUpdateSchemaContext(OsgiBundleScanningSchemaService.java:247)
 at org.opendaylight.mdsal.dom.broker.osgi.OsgiBundleScanningSchemaService$BundleScanner.removedBundle(OsgiBundleScanningSchemaService.java:227)
 at org.opendaylight.mdsal.dom.broker.osgi.OsgiBundleScanningSchemaService$BundleScanner.removedBundle(OsgiBundleScanningSchemaService.java:165)
 at org.osgi.util.tracker.BundleTracker$Tracked.customizerRemoved(BundleTracker.java:495)[org.osgi.core-6.0.0.jar:]
 at org.osgi.util.tracker.BundleTracker$Tracked.customizerRemoved(BundleTracker.java:415)[org.osgi.core-6.0.0.jar:]
 at org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)[org.osgi.core-6.0.0.jar:]
 at org.osgi.util.tracker.BundleTracker.close(BundleTracker.java:192)[org.osgi.core-6.0.0.jar:]
 at org.opendaylight.mdsal.dom.broker.osgi.OsgiBundleScanningSchemaService.close(OsgiBundleScanningSchemaService.java:132)
 at org.opendaylight.mdsal.dom.broker.osgi.SchemaServiceActivator.stop(SchemaServiceActivator.java:32)
 at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:827)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at java.security.AccessController.doPrivileged(Native Method)[:1.8.0_121]
 at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:820)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:955)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:323)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.Module.doStop(Module.java:626)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.Module.stop(Module.java:488)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1623)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1542)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:248)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:144)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.Module.doStop(Module.java:626)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.Module.stop(Module.java:488)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:186)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:159)[org.eclipse.osgi-3.10.101.v20150820-1432.jar:]
 at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27057">MDSAL-235</key>
            <summary>[INFO] Failed to fully assemble schema context for [...]</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="rovarga">Robert Varga</assignee>
                                    <reporter username="vorburger">Michael Vorburger</reporter>
                        <labels>
                    </labels>
                <created>Wed, 8 Mar 2017 01:54:34 +0000</created>
                <updated>Fri, 28 Feb 2020 14:58:39 +0000</updated>
                            <resolved>Fri, 28 Feb 2020 14:58:39 +0000</resolved>
                                                    <fixVersion>6.0.0</fixVersion>
                                    <component>DOM runtime</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="54598" author="vorburger" created="Wed, 8 Mar 2017 02:15:50 +0000"  >&lt;p&gt;I just noticed that these errors are from &quot;Framework stop&quot; (which I hadn&apos;t noticed before..) in SFT, and also similarly below when you Ctrl-D a non-SFT real Karaf - IMHO it probably should be more silent particularly when it goes down...&lt;/p&gt;

&lt;p&gt;2017-03-07 21:25:12,616 | INFO  |  Bundle Shutdown | YangTextSchemaContextResolver    | 107 - org.opendaylight.yangtools.yang-parser-impl - 1.1.0.SNAPSHOT | Failed to fully assemble schema context for [RevisionSourceIdentifier &lt;span class=&quot;error&quot;&gt;&amp;#91;name=fib-rpc@2016-01-21&amp;#93;&lt;/span&gt;, RevisionSourceIdentifier &lt;span class=&quot;error&quot;&gt;&amp;#91;name=l3nexthop@2015-04-09&amp;#93;&lt;/span&gt;, RevisionSourceIdentifier &lt;span class=&quot;error&quot;&gt;&amp;#91;name=odl-fib@2015-03-30&amp;#93;&lt;/span&gt;]&lt;/p&gt;</comment>
                            <comment id="54599" author="vorburger" created="Wed, 8 Mar 2017 02:25:33 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/MDSAL-236&quot; title=&quot;Too Extensive several MBs [INFO] logs from yang-parser-impl during shutdown&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MDSAL-236&quot;&gt;&lt;del&gt;MDSAL-236&lt;/del&gt;&lt;/a&gt; opened for a generalization (this bug is re. 1 particularly frequent message).&lt;/p&gt;</comment>
                            <comment id="54600" author="rovarga" created="Fri, 24 Mar 2017 16:46:37 +0000"  >&lt;p&gt;Well, the crux of the problem is that the caller (mdsal/controller?) does not interact with Karaf feature service enough to be plugged into the lifecycle, hence it ends up recomputing the schema context during installation/shutdown process as the set of available models is still in flux.&lt;/p&gt;

&lt;p&gt;If we silence these logs, we can end up with a karaf instance which does not work due to a single model missing, hence INFO is appropriate here.&lt;/p&gt;

&lt;p&gt;Once the root cause is fixed, these will automatically go away.&lt;/p&gt;</comment>
                            <comment id="54601" author="rovarga" created="Wed, 26 Apr 2017 19:27:05 +0000"  >&lt;p&gt;Opened &lt;a href=&quot;https://issues.apache.org/jira/browse/KARAF-5107&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://issues.apache.org/jira/browse/KARAF-5107&lt;/a&gt; upstream.&lt;/p&gt;</comment>
                            <comment id="54602" author="rovarga" created="Thu, 27 Apr 2017 18:11:46 +0000"  >&lt;p&gt;Once &lt;a href=&quot;https://jira.opendaylight.org/browse/MDSAL-248&quot; title=&quot;Split out OsgiBundleScanningSchemaService&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MDSAL-248&quot;&gt;&lt;del&gt;MDSAL-248&lt;/del&gt;&lt;/a&gt; is addressed, we need to create mdsal-dom-schema-service-karaf, which will talk to Karaf&apos;s FeatureService and do bundle scan throttling based on the events from it.&lt;/p&gt;</comment>
                            <comment id="54603" author="rovarga" created="Thu, 27 Apr 2017 18:13:16 +0000"  >&lt;p&gt;This new implementation should then be packaged into the feature in place of the osgi scanner, hence our karaf deployments will not see the log entries mentioned.&lt;/p&gt;</comment>
                            <comment id="54604" author="rovarga" created="Tue, 2 May 2017 00:21:44 +0000"  >&lt;p&gt;Karaf 4.1.2 and 4.2.0 will have FeatureService.registerListener(DeploymentListener), which gives events on start, resolve and end of deployment.&lt;/p&gt;</comment>
                            <comment id="67919" author="rovarga" created="Fri, 28 Feb 2020 13:37:12 +0000"  >&lt;p&gt;Resolved by adding a Karaf-specific wrapper around YangModuleInfoRegistry, which is bypassed if FeaturesService is not available.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="23217">YANGTOOLS-797</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="27070">MDSAL-248</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="22209">ODLPARENT-86</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="31053">MDSAL-392</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>7925</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=7925]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10305"><![CDATA[Improvement]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02x5b:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>