[VTN-27] VTN Manager forgets flow entries when the controller enters container mode. Created: 15/Jul/14  Updated: 03/May/18  Resolved: 08/Oct/14

Status: Resolved
Project: vtn
Component/s: VTN Manager
Affects Version/s: unspecified
Fix Version/s: None

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

Operating System: Linux
Platform: PC


External issue ID: 1364

 Description   

How to reproduce:

1. Create VTN and vBridge in the default container, and map physical network
to the vBridge.
2. Install flow entries by sending packets to the vBridge.
3. Create a container. When the first container is created, FRM uninstalls all
flow entries from switches, and VTN Manager forgets those flow entries.
4. Destroy the container that was created by step 3. When the last container
is destroyed, FRM restores all flow entries that were uninstalled by step 3.
But those flow entries are out of control because VTN Manager no longer
manages.

VTN Manager should:

  • preserve flow entries during container mode.
  • ignore FLOW_REMOVED notifications during container mode.
  • behave as if no data flow is installed.


 Comments   
Comment by Shigeru Yasuda [ 08/Oct/14 ]

https://git.opendaylight.org/gerrit/9003 (master)
https://git.opendaylight.org/gerrit/11800 (stable/hydrogen)

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