[OPNFLWPLUG-356] Exceptions from TicketProcessorFactory when using the l2switch with a HP 8206zl under certain configurations Created: 09/Feb/15  Updated: 27/Sep/21  Resolved: 19/Aug/16

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Mario Willems Assignee: Renato Aguiar
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC

Attachments: File karaf-wireshark-hp.tar.gz    
External issue ID: 2693

 Description   

According to this (Test2):
https://lists.opendaylight.org/pipermail/openflowplugin-dev/2015-February/002512.html:

Using the l2switch with the 58-l2switchmain.xml configured to install a drop flow to table 100, leads to several exceptions from TicketFinisherImpl. Default hp drop flow gets overwritten and is on the switch, but there are serveral execptions in the log. More details on the posted link. I attached the karaf.log and a wireshark log from the communication.

 Comments   
Comment by Mario Willems [ 09/Feb/15 ]

Attachment karaf-wireshark-hp.tar.gz has been added with description: Archiv contains the karaf- and the wireshark-log

Comment by Abhijit Kumbhare [ 24/Feb/15 ]

Can you provide the exceptions that you are facing Mario?

Comment by Mario Willems [ 08/Apr/15 ]

Sorry for the late response, I'm currently very busy... the exceptions are in the attached .tar.gz file, i post it here too, see below.

I used the feature odl-l2switch-switch feature with the actual pre-build Helium SR3 zip file from the odl hp. The hp switch only accepts flows in table 100, so I changed the config file(s) of l2switch components to write the flows in table 100.

After the switch connects only the default drop flow gets installed:
cookie=0x2b00000000000001, duration=2.185s, table=100, n_packets=0, n_bytes=0, priority=0 actions=drop

No uptoctrl flow and therefore no further flows for host communication. After the switch is connected the karaf.log shows continuing errrors (every 5sec), hope this helps:

2015-04-08 15:45:00,203 | ERROR | OFmsgProcessor-0 | TicketProcessorFactoryImpl | 176 - org.opendaylight.openflowplugin - 0.0.6.Helium-SR3 | translation problem: null
2015-04-08 15:45:00,204 | WARN | OFmsgFinisher-0 | TicketFinisherImpl | 176 - org.opendaylight.openflowplugin - 0.0.6.Helium-SR3 | processing (translate, publish) of ticket failed
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)[78:com.google.guava:14.0.1]
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293)[78:com.google.guava:14.0.1]
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)[78:com.google.guava:14.0.1]
at org.opendaylight.openflowplugin.openflow.md.queue.TicketFinisherImpl.run(TicketFinisherImpl.java:49)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_75]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_75]
Caused by: java.lang.NullPointerException
at org.opendaylight.openflowplugin.openflow.md.core.sal.convertor.ActionConvertor.toMDSalActions(ActionConvertor.java:898)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at org.opendaylight.openflowplugin.openflow.md.core.sal.convertor.OFToMDSalFlowConvertor.toSALInstruction(OFToMDSalFlowConvertor.java:66)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at org.opendaylight.openflowplugin.openflow.md.core.sal.convertor.FlowStatsResponseConvertor.toSALFlowStats(FlowStatsResponseConvertor.java:103)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at org.opendaylight.openflowplugin.openflow.md.core.sal.convertor.FlowStatsResponseConvertor.toSALFlowStatsList(FlowStatsResponseConvertor.java:49)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at org.opendaylight.openflowplugin.openflow.md.core.translator.MultipartReplyTranslator.translate(MultipartReplyTranslator.java:134)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at org.opendaylight.openflowplugin.openflow.md.core.translator.MultipartReplyTranslator.translate(MultipartReplyTranslator.java:106)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at org.opendaylight.openflowplugin.openflow.md.queue.TicketProcessorFactoryImpl.translate(TicketProcessorFactoryImpl.java:166)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
at org.opendaylight.openflowplugin.openflow.md.queue.TicketProcessorFactoryImpl$1.run(TicketProcessorFactoryImpl.java:78)[176:org.opendaylight.openflowplugin:0.0.6.Helium-SR3]
... 3 more

Comment by Abhijit Kumbhare [ 10/Nov/15 ]

Renato,

Can you check this when you get time?

Thanks,
Abhijit

Comment by Andrej Leitner [ 19/Aug/16 ]

Hi Mario,
we could not reproduce this issue at this time and many things have changed since you reported the bug. Please raise a new bug if there are still any issues.

Generated at Wed Feb 07 20:32:15 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.