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-364 OpenFlowPlugin <ul class="alternate" type="square"> <li>Unable to provision the node with flow containing ingressPort=LOCAL match.</li> <li>The following exception thrown during statistics collection when flow with match IN_PORT=LOCAL is created by ovs-ofctl utility:</li> </ul> <p>2015-01-30 10:51:15.891 EST <span class="error">&#91;md-sal-binding-notification-15&#93;</span> WARN o.o.c.s.c.ToSalConversionsUtils - nodeConnector construction failed<br/> org.opendaylight.controller.sal.core.ConstructionException: Type of incoming object:class java.lang.String not compatible with expected type:class java.lang.Short or Node type incompatible:PR<br/> at org.opendaylight.controller.sal.core.NodeConnector.&lt;init&gt;(NodeConnector.java:249) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.compatibility.NodeMapping.toADNodeConnector(NodeMapping.java:150) ~<span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.compatibility.ToSalConversionsUtils.fillFrom(ToSalConversionsUtils.java:413) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.compatibility.ToSalConversionsUtils.toMatch(ToSalConversionsUtils.java:398) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.compatibility.ToSalConversionsUtils.toFlow(ToSalConversionsUtils.java:139) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.toFlowOnNode(InventoryAndReadAdapter.java:789) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter.onFlowsStatisticsUpdate(InventoryAndReadAdapter.java:710) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.compatibility.InventoryAndReadAdapter$$Broker$ListenerInvoker.onNotification(InventoryAndReadAdapter$$Broker$ListenerInvoker.java) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.binding.impl.AbstractNotificationListenerRegistration.notify(AbstractNotificationListenerRegistration.java:38) <span class="error">&#91;bundlefile:na&#93;</span><br/> at org.opendaylight.controller.sal.binding.impl.NotifyTask.run(NotifyTask.java:42) <span class="error">&#91;bundlefile:na&#93;</span><br/> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) <span class="error">&#91;na:1.7.0_72&#93;</span><br/> at java.util.concurrent.FutureTask.run(FutureTask.java:262) <span class="error">&#91;na:1.7.0_72&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) <span class="error">&#91;na:1.7.0_72&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) <span class="error">&#91;na:1.7.0_72&#93;</span><br/> at java.lang.Thread.run(Thread.java:745) <span class="error">&#91;na:1.7.0_72&#93;</span></p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-364

Unable to create flow with match ingressPort=LOCAL

Bug Resolved Won't Do Igor Kondrakhin Igor Kondrakhin Wed, 18 Feb 2015 19:17:39 +0000 Mon, 27 Sep 2021 09:01:25 +0000 Fri, 13 Mar 2015 16:50:10 +0000 General 0 4 <p>Hi Igor,<br/> as you wrote, problem lies in statistics when they try to translate value LOCAL into port (short). We can solve this by setting permannent value as representation of LOCAL port, but this will lead to some inconsistencies (OF 1.0 vs OF 1.3). <br/> But however, this will be only temporary solution because ad-sal is planned to get deprecated after Lithium release.<br/> Do you have any proposal on how to solve the situation?</p> <p>Thank you.</p> <p>This bug report describes two issues:</p> <p>First, most important one, is that OpenDaylight does not provide an ability to provision a node with flow containing ingressPort=LOCAL match.</p> <p>Second, not really important at this moment, describes an exception that will be thrown when first issue will be fixed and node will be provided with flow containing ingressPort=LOCAL match.</p> <p>Hi Igor,<br/> I just tried to add flow containing &lt;in-port&gt;LOCAL&lt;/in-port&gt; in match element. It worked without any switch connected and it got pushed to switch upon connection established. <br/> I observed the complains of sal-compatibility as it is not able to deal with logical names of ports.</p> <p>Could you describe in detail how are you adding such a flow to ODL? Because the exception of yours emerges during processing of statistics notification containing such a flow. So I guess that the flow is on device. Could you check on that?</p> <p>Thank you.</p> <p>Hello Michal,</p> <p>I’ve done more testing and found out that the first issue described in my previous comment is reproducible only on ODL Hydrogen. Sorry for misleading bug description. It was discovered when I was working with ODL Hydrogen.<br/> You can not set up flow with "ingressPort":"LOCAL" using flowprogrammer, but it is probably well known issue. </p> <p>I was able to create a flow with in_port LOCAL using inventory manager on Helium/MD-SAL. So, the first issue described in my previous comment does not present in helium release.</p> <p>Thank you.</p> <p>Ok, does the second issue affect or break your application? </p> <p>I believe it just prohibits the ad-sal world from being notified about a flow presence on device. And only if the flow contains logical port name instead of number.</p> <p>The second issue does not break my application.</p> <p>OK, would you mind closing this bug as WONTFIX? </p> <p>Because while ad-sal does not support any other than numeric port value for openflow protocol then we can not do much about it.</p> Development External issue ID 2735 External issue URL Rank 0|i030p3: