[NETVIRT-203] Vpn to Scf pipeline not installed when a VM is moved to a new DPN Created: 13/Oct/16 Updated: 19/Oct/17 Resolved: 25/Oct/16 |
|
| 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: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6934 |
| Description |
|
When a ServiceChain is built on top of a VPN, the flows that take the packets from L3VPN domain to SCF domain are installed in all those DPNs where the VPN has footprint. However, if one of the VMs belonging to the VPN is moved to another DPN (where the VPN does not have footprint yet!!), those flows are not being installed there. |
| Comments |
| Comment by Vivekanandan Narasimhan [ 25/Oct/16 ] |
|
This issue was partly fixed in stable/boron via review: |