[OPNFLWPLUG-880] onFlowRemoved notification not recevied for NAT service Created: 18/Apr/17 Updated: 27/Sep/21 Resolved: 03/May/17 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Chetan Arakere Gowdru | Assignee: | Chetan Arakere Gowdru |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8238 |
| Description |
|
I'm observing the onFlowRemoved() is not getting called on Flow removal from Switch. NAT has implemented SalFlowListener and does certain clean-up on receiving Flow Removed Notification on specific table(on IDLE_TIME_OUT). public class NaptFlowRemovedEventHandler implements SalFlowListener { public void onFlowRemoved(FlowRemoved flowRemoved) { ...}} Because of this FlowRemoved() is not called, certain SNAT functionality is not working fine. |
| Comments |
| Comment by Tomas Slusny [ 25/Apr/17 ] |
|
This is probably duplicate of |
| Comment by Chetan Arakere Gowdru [ 26/Apr/17 ] |
|
Hi Tomas, I verified in stable/carbon and it's working fine. But,in master(as I see https://git.opendaylight.org/gerrit/#/c/55044/ merged), I tried to build netvirt project(couple of times), but the issue still persist. I see the master merge on this issue is in UNSTABLE state(not sure whether netvirt build picked the latest changes. I tired to decompile openflowlpugin jar to validate whether this review change exists, but somehow the content of DeviceContextImpl.java are getting decompiled). If possible, Request to point to the distribution build of master(in which this review change available) which I can download and validate this issue. Thanks, |
| Comment by Chetan Arakere Gowdru [ 03/May/17 ] |
|
Re-validated the issue with the latest build in master(nitrogen) and we are receiving the onFlowRemoved notification properly. Hence, closing this issue. |