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/OPNFLWPLUG-439 OpenFlowPlugin <p>log: <a href="https://gist.github.com/eaab1c31383ebb4088a8" class="external-link" target="_blank" rel="nofollow noopener">https://gist.github.com/eaab1c31383ebb4088a8</a></p> <p>$ bin/karaf<br/> karaf: Enabling Java debug options: -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005<br/> Listening for transport dt_socket at address: 5005</p> <p> ________ ________ .__ .__ .__ __<br/> &#95;____ \ ______ ____ ____ &#95;_____ \ _____ __<em>.</em><em>.| | |</em><em>| ____ | |</em>_<em>/ |</em><br/> / | <br class="atl-forced-newline" />____ &#95;/ __ \ / \ | | <br class="atl-forced-newline" />__ \&lt; | || | | |/ ___&#124; | \ __\<br/> / | \ |<em>&gt; &gt; ___/| | &#124; ` \/ __ <br class="atl-forced-newline" />___ || |</em>| / /_/ &gt; Y \ |<br/> &#95;______ / _<em>/ &#95;</em>_ &gt;__<em>| /</em>______ (____ / ___<em>||</em>__<em>/</em><em>&#95;</em>_ /|__<em>| /</em>_|<br/> \/|_<em>| \/ \/ \/ \/\/ /</em>____/ \/</p> <p>Hit '&lt;tab&gt;' for a list of available commands<br/> and '<span class="error">&#91;cmd&#93;</span> --help' for help on a specific command.<br/> Hit '&lt;ctrl-d&gt;' or type 'system:shutdown' or 'logout' to shutdown OpenDaylight.</p> <p>opendaylight-user@root&gt;Exception in thread "pool-11-thread-1" java.lang.IllegalStateException: TopologyManager startup fail! TM bundle needs restart.<br/> at org.opendaylight.openflowplugin.applications.topology.manager.DataChangeListenerImpl.&lt;init&gt;(DataChangeListenerImpl.java:66)<br/> at org.opendaylight.openflowplugin.applications.topology.manager.TerminationPointChangeListenerImpl.&lt;init&gt;(TerminationPointChangeListenerImpl.java:41)<br/> at org.opendaylight.openflowplugin.applications.topology.manager.FlowCapableTopologyProvider.onSessionInitiated(FlowCapableTopologyProvider.java:55)<br/> at org.opendaylight.controller.md.sal.binding.util.BindingContextUtils.createProviderContextAndInitialize(BindingContextUtils.java:56)<br/> at org.opendaylight.controller.sal.binding.impl.RootBindingAwareBroker.registerProvider(RootBindingAwareBroker.java:172)<br/> at org.opendaylight.controller.sal.binding.impl.RootBindingAwareBroker.registerProvider(RootBindingAwareBroker.java:160)<br/> at org.opendaylight.controller.sal.binding.api.AbstractBindingAwareProvider.onBrokerAvailable(AbstractBindingAwareProvider.java:18)<br/> at org.opendaylight.controller.sal.binding.api.AbstractBrokerAwareActivator$1$1.run(AbstractBrokerAwareActivator.java:34)<br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)<br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)<br/> at java.lang.Thread.run(Thread.java:745)<br/> Caused by: org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException: Class interface org.opendaylight.yang.gen.v1.urn.opendaylight.flow.inventory.rev130819.FlowCapableNodeConnector is not valid child of interface org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.node.NodeConnector<br/> at org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException.create(IncorrectNestingException.java:28)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext.childNonNull(DataContainerCodecContext.java:178)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.DataObjectCodecContext.bindingPathArgumentChild(DataObjectCodecContext.java:178)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.BindingCodecContext.getCodecContextNode(BindingCodecContext.java:127)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.InstanceIdentifierCodec.serialize(InstanceIdentifierCodec.java:29)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.InstanceIdentifierCodec.serialize(InstanceIdentifierCodec.java:19)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCodecRegistry.toYangInstanceIdentifier(BindingNormalizedNodeCodecRegistry.java:87)<br/> at org.opendaylight.controller.md.sal.binding.impl.BindingToNormalizedNodeCodec.toNormalized(BindingToNormalizedNodeCodec.java:89)<br/> at org.opendaylight.controller.md.sal.binding.impl.AbstractForwardedDataBroker.registerDataChangeListener(AbstractForwardedDataBroker.java:68)<br/> at org.opendaylight.openflowplugin.applications.topology.manager.DataChangeListenerImpl$1.call(DataChangeListenerImpl.java:58)<br/> at org.opendaylight.openflowplugin.applications.topology.manager.DataChangeListenerImpl$1.call(DataChangeListenerImpl.java:55)<br/> at org.opendaylight.openflowplugin.common.wait.SimpleTaskRetryLooper.loopUntilNoException(SimpleTaskRetryLooper.java:41)<br/> at org.opendaylight.openflowplugin.applications.topology.manager.DataChangeListenerImpl.&lt;init&gt;(DataChangeListenerImpl.java:55)<br/> ... 10 more</p> <p>opendaylight-user@root&gt;</p> <p>====</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-439

org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException: Class interface org.opendaylight.yang.gen.v1.urn.opendaylight.flow.inventory.rev130819.FlowCapableNodeConnector is not valid child of interface org.opendaylight.yang.gen.v1.urn.

Bug Resolved Cannot Reproduce Unassigned Flavio Fernandes Wed, 13 May 2015 19:14:17 +0000 Mon, 27 Sep 2021 09:01:31 +0000 Tue, 26 Jul 2016 14:19:35 +0000 General 0 6 <p><span class="error">&#91;15:07:13&#93;</span> &lt;flaviof&gt; vishnoianil: qq.<br/> <span class="error">&#91;15:07:23&#93;</span> &lt;vishnoianil&gt; flaviof, sure<br/> <span class="error">&#91;15:07:23&#93;</span> &lt;flaviof&gt; vishnoianil: If Isee this: <a href="https://gist.github.com/f000be830e77bcb20c43" class="external-link" target="_blank" rel="nofollow noopener">https://gist.github.com/f000be830e77bcb20c43</a><br/> <span class="error">&#91;15:07:54&#93;</span> &lt;flaviof&gt; vishnoianil: is that begign enough, so I can continue, or is that reason to start over?<br/> <span class="error">&#91;15:08:17&#93;</span> &lt;vishnoianil&gt; flaviof, for me that means stop the controller, delete the data directory and restart it<br/> <span class="error">&#91;15:08:19&#93;</span> &lt;vishnoianil&gt; <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/><br/> <span class="error">&#91;15:08:26&#93;</span> &lt;vishnoianil&gt; flaviof, no it's not benign<br/> <span class="error">&#91;15:08:38&#93;</span> &lt;flaviof&gt; vishnoianil: I'm glad I asked. <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/wink.png" height="16" width="16" align="absmiddle" alt="" border="0"/><br/> <span class="error">&#91;15:08:47&#93;</span> &lt;flaviof&gt; thanks!<br/> <span class="error">&#91;15:09:00&#93;</span> &lt;vishnoianil&gt; flaviof, i didn't get a chance to dig into that, because we have something more critical on plate <img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Partly duplicate of <a href="https://jira.opendaylight.org/browse/CONTROLLER-1278" title="Component gets started before models are available in mdsal" class="issue-link" data-issue-key="CONTROLLER-1278"><del>CONTROLLER-1278</del></a> <br/> but providing reference to topology model in initial config<br/> for topology provider will prevent app starting before models are loaded.</p> <p>Initial config contains capabilities section, where topology model and flow capable model should be listed.</p> <p>This will prevent it from starting before models are loaded.</p> <p>(In reply to Tony Tkacik from comment #2)<br/> &gt; Partly duplicate of <a href="https://jira.opendaylight.org/browse/CONTROLLER-1278" title="Component gets started before models are available in mdsal" class="issue-link" data-issue-key="CONTROLLER-1278"><del>CONTROLLER-1278</del></a> <br/> &gt; but providing reference to topology model in initial config<br/> &gt; for topology provider will prevent app starting before models are loaded.<br/> &gt; <br/> &gt; Initial config contains capabilities section, where topology model and flow<br/> &gt; capable model should be listed.<br/> &gt; <br/> &gt; This will prevent it from starting before models are loaded.</p> <p>thanks for the update, Tony!</p> <p>(In reply to Tony Tkacik from comment #2)<br/> &gt; Partly duplicate of <a href="https://jira.opendaylight.org/browse/CONTROLLER-1278" title="Component gets started before models are available in mdsal" class="issue-link" data-issue-key="CONTROLLER-1278"><del>CONTROLLER-1278</del></a> <br/> &gt; but providing reference to topology model in initial config<br/> &gt; for topology provider will prevent app starting before models are loaded.<br/> &gt; <br/> &gt; Initial config contains capabilities section, where topology model and flow<br/> &gt; capable model should be listed.<br/> &gt; <br/> &gt; This will prevent it from starting before models are loaded.</p> <p>Tony,</p> <p>does this mean out ovsdb netvirt app needs to be using config? Currently netvirt is activator based and does not use config. Changing to config has been difficult because there is a lot of dependency injection and callback code that we ahve not been able to convert.</p> <p>Thanks, Sam</p> <p>Hi, there is patch for controller which adds blocking behaviour for users<br/> Which uses different activation,<br/> That means if we detect situation such as class is present and schema<br/> Not available yet, we will block user thread and unblock<br/> It when schema is available or after 5sec.</p> <p>Tony</p> <p>Tony,</p> <p>could you post the gerrit for the patch?</p> <p>How does config determine that a schema is not loaded if the application does not use config to set a capability for the model?</p> <p>Thanks, Sam</p> <p>Flavio,</p> <p>I am tracking on this issue too. Looks like the bug that was noted as partly duplicate <a href="https://bugs.opendaylight.org/show_bug.cgi?id=3067" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=3067</a> had it's patch merged today <a href="https://git.opendaylight.org/gerrit/#/c/19607/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/19607/</a> . It didn't seem to fix my case though. Has it fixed your case? if so, I'll open a new bug to track it on my side.</p> <p>Thanks,<br/> JamO</p> <p>(In reply to Jamo Luhrsen from comment #7)<br/> &gt; Flavio,<br/> &gt; <br/> &gt; I am tracking on this issue too. Looks like the bug that was noted as<br/> &gt; partly duplicate <a href="https://bugs.opendaylight.org/show_bug.cgi?id=3067" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=3067</a> had it's<br/> &gt; patch merged today <a href="https://git.opendaylight.org/gerrit/#/c/19607/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/19607/</a> . It<br/> &gt; didn't seem to fix my case though. Has it fixed your case? if so, I'll<br/> &gt; open a new bug to track it on my side.<br/> &gt; <br/> &gt; Thanks,<br/> &gt; JamO</p> <p>Hi JamO!</p> <p>I have not seen this issue for a while. I'd say it's best if you<br/> open a new bug to track it on your side.</p> <p>&#8211; flavio</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/22804/1" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/22804/1</a> - improves reporting of this type of error in yangtools - which will result in md-sal waiting till schema for inventory augmentations is loaded.</p> <p>No longer an issue.</p> <p>Hi,</p> <p>why do I get this exception?<br/> .. </p> <p>IncorrectNestingException: Child interface org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.xxxxxxxxxxAugment is not valid child.<br/> at org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException.create(IncorrectNestingException.java:28)<br/> at org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext.childNonNull(DataContainerCodecContext.java:180)<span class="error">&#91;66:org.opendaylight.mdsal.binding-dom-codec:0.8.1.Beryllium-SR1&#93;</span><br/> at org.opendaylight.yangtools.binding.data.codec.impl.DataObjectCodecContext.streamChild(DataObjectCodecContext.java:149)<span class="error">&#91;66:org.opendaylight.mdsal.binding-dom-codec:0.8.1.Beryllium-SR1&#93;</span><br/> at org.opendaylight.yangtools.binding.data...</p> <p>(In reply to Harinath Mallepally from comment #11)<br/> &gt; Hi,<br/> &gt; <br/> &gt; why do I get this exception?<br/> &gt; .. <br/> &gt; <br/> &gt; IncorrectNestingException: Child interface<br/> &gt; org.opendaylight.yang.gen.v1.urn.ietf.params.xml.ns.yang.xxxxxxxxxxAugment<br/> &gt; is not valid child.<br/> &gt; at<br/> &gt; org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException.<br/> &gt; create(IncorrectNestingException.java:28)<br/> &gt; at<br/> &gt; org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext.<br/> &gt; childNonNull(DataContainerCodecContext.java:180)[66:org.opendaylight.mdsal.<br/> &gt; binding-dom-codec:0.8.1.Beryllium-SR1]<br/> &gt; at<br/> &gt; org.opendaylight.yangtools.binding.data.codec.impl.DataObjectCodecContext.<br/> &gt; streamChild(DataObjectCodecContext.java:149)[66:org.opendaylight.mdsal.<br/> &gt; binding-dom-codec:0.8.1.Beryllium-SR1]<br/> &gt; at org.opendaylight.yangtools.binding.data...</p> <p>Harinath,</p> <p>not sure if it is the same as in this bug here, but the cause was because certain models were not loaded when they were used. The solution was to add methods to ensure all models were loaded before using them. in the config.xml file you can add required-capabilities for your module to indicate what models to wait for. The patch mentioned below by Tony is for modules that don't use config.</p> <p>Sam</p> Blocks YANGTOOLS-470 Development External issue ID 3212 External issue URL Rank 0|i0315r: