[OPNFLWPLUG-530] [FLOW RECONCILIATION]Expirable flows appear in the switch post reconnect Created: 10/Aug/15  Updated: 27/Sep/21  Resolved: 10/Sep/18

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: Fluorine-SR2, Neon

Type: Improvement Priority: High
Reporter: Shuva Jyoti Kar Assignee: Anil Vishnoi
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Other


Issue Links:
Duplicate
duplicates OPNFLWPLUG-971 Node reconciliation installs old, exp... Open

 Description   

Description:

An application might want to add flows on the flows that expire after a given time – idle/hard timeout of 't'seconds.

So as an application it is desired that the flows do not exist on the switch after 't' seconds. But if

1. the switch restarts before the timers expire, the flows are re-provisioned resulting in rest of the timers.

2. the tcp connection is severed, the flows do expire, but when the switch reconnects the flows are replayed again to the switch , which is undesirable.

So in all cases where the switch reactively removes flows, the switch ends up with an undesirable flow-set post restart or reconnect.

Marking the Bug as critical as it might require a change in the way the reconciliation framework works.

Also it affects the traffic since the traffic is routed through undesirable routes affecting the application intent.



 Comments   
Comment by Muthukumaran Kothandaraman [ 02/Nov/15 ]

This requires changes in inventory model and additional integration TCs. It would be better if we defer this for now

Comment by Abhijit Kumbhare [ 25/Jan/16 ]

Deferred as per Muthu's comments.

Comment by Abhijit Kumbhare [ 30/Jan/16 ]

Marked as normal - as Muthu/Shuva are deferring this issue.

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