[#NETVIRT-335] Adding a DPN to an Elan Footprint was not installing Elan Pseudo-port flows in that DPN

[NETVIRT-335] Adding a DPN to an Elan Footprint was not installing Elan Pseudo-port flows in that DPN Created: 07/Dec/16 Updated: 19/Oct/17 Resolved: 07/Jan/17
Status:	Resolved
Project:	netvirt
Component/s:	General
Affects Version/s:	Boron
Fix Version/s:	None

Type:

Bug

Reporter:

Miguel Perez

Assignee:

Unassigned

Resolution:

Done

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: All
Platform: All

External issue ID:

7321

Description

There are 3 flows (2 in LPortDispatcher table and 1 in External Tunnel table) that are in charge of handling packets from Elan domain to SCF domain and viceversa.

These 3 flows must be installed in each and every DPN that belongs to the Elan Footprint when a ServiceChain is created over that Elan.

It's been observed that when a new DPN is added to the Elan's footprint, those 3 flows were not being installed there.

Comments

Comment by Alon Kochba [ 07/Jan/17 ]

https://git.opendaylight.org/gerrit/#/c/49097

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

[NETVIRT-335] Adding a DPN to an Elan Footprint was not installing Elan Pseudo-port flows in that DPN Created: 07/Dec/16 Updated: 19/Oct/17 Resolved: 07/Jan/17