[CONTROLLER-16] Clarify a message in case of connectivity issues between controller and switch Created: 16/May/13  Updated: 19/Oct/17  Resolved: 19/May/16

Status: Resolved
Project: controller
Component/s: adsal
Affects Version/s: 0.4.0
Fix Version/s: None

Type: Improvement
Reporter: Albert Fishman Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Windows
Platform: PC



 Description   

When the network connection between the controller and the switch is not stable, flow mods attempted to get installed from the controller may not go on the wire, but the message from UI says: "The failure is: Failed to add the flow: Request Timed Out". This is not clear.

For example:
2013-05-15 11:18:18.420 PDT [http-bio-8080-exec-5] WARN o.o.c.f.i.ForwardingRulesManagerImpl - SDN Plugin failed to program the flow: FlowEntry[flowName = Marvell Test 1, groupName = **StaticFlows,node = OF|00:00:02:5f:b8:47:63:c9, flow = Flow[match = Match[[DL_TYPE(2048,null), IN_PORT(OF|7@OF|00:00:02:5f:b8:47:63:c9,null)]], actions = [DROP], priority = 123, id = 0, idleTimeout = 0, hardTimeout = 0]]. The failure is: Failed to add the flow: Request Timed Out

On controller side the issue I see is that SwitchHandler.syncMessageInternal(…) catches on the generic Exception and assumes it is always because of switch barrier reply timeout…
With a more granular catching, the proper error message could be returned and save debug time…



 Comments   
Comment by Carol Sanders [ 04/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL

Comment by Robert Varga [ 19/May/16 ]

AD-SAL has been removed, this issue will not be fixed.

Generated at Wed Feb 07 19:51:58 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.