[NETVIRT-532] SNAT: IDLE_TIME_OUT check required when flowRemoved notification received for OUTBOUND_NAPT_TABLE Created: 15/Mar/17  Updated: 15/Dec/17  Resolved: 21/Mar/17

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

Type: Bug
Reporter: Chetan Arakere Gowdru Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 7984

 Description   

Its been observed that with https://git.opendaylight.org/gerrit/#/c/49214/, when we no longer receiving onSwitchFlowRemoved(), instead onFlowRemoved() was getting removed, the check for IDLE_TIME_OUT been removed.

As a result, the we end-up freeing of the allocated external-ports in both IDLE_TIMEOUT(which is valid) and it the switch goes down(which in invalid). When the switch goes down, we elect a new NAPT switch and re-install the on-going SNAT session flows in it. So, we may end-up in not installing the going SNAT session flows.

Support to provide Flow removed reason has been provided when onFlowRemoved is triggered with https://git.opendaylight.org/gerrit/#/c/53288/ which can be made used and adding back the IdleTimeOutCheck.



 Comments   
Comment by Chetan Arakere Gowdru [ 15/Mar/17 ]

Plugin support available with review - https://git.opendaylight.org/gerrit/#/c/50335/

Comment by Chetan Arakere Gowdru [ 21/Mar/17 ]

Fix review - https://git.opendaylight.org/gerrit/#/c/53288/

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