[VTN-79] [Helium] Unwanted flow entries are removed when link-down is detected. Created: 07/Jul/15 Updated: 19/Oct/17 Resolved: 07/Jul/15 |
|
| 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: All |
||
| External issue ID: | 3949 |
| Description |
|
VTN Manager in Helium release may remove unwanted flow entries when link-down is detected. How to reproduce: 1. Start mininet with 3 depth tree topology. % sudo mn --controller=remote,ip=controller-ip --topo tree,3 2. Create a VTN and a vBridge, and map untagged frames using VLAN mapping. POST /controller/nb/v2/vtn/default/vtns/vtn_1 3. Establish unicast flows by sending ICMP echo. mininet> pingall 4. Shut down the network interface in host h1. mininet> h1 ifconfig h1-eth0 down This should uninstall flow entries whose source or destination host is h1. |
| Comments |
| Comment by Shigeru Yasuda [ 07/Jul/15 ] |
|
VTN Manager in Helium release uses sal-compatibility, and it forwards data change events detected in MD-SAL inventory tree via AD-SAL IInventoryListener. When a node-connector in MD-SAL inventory tree is changed, sal-compatibility invokes notifyNode() with specifying a node which contains that node-connector though a node itself is not changed. VTN Manager should ignore those bogus notifications. |
| Comment by Shigeru Yasuda [ 07/Jul/15 ] |
|
https://git.opendaylight.org/gerrit/23820 (stable/helium) This issue is specific to Helium, and never happen in Lithium. |