[SFC-148] Missing actions in SFF egress flows Created: 15/Jun/16 Updated: 19/Oct/17 Resolved: 20/Jun/16 |
|
| Status: | Resolved |
| Project: | sfc |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tomas Cechvala | 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: | 6068 |
| Priority: | Highest |
| Description |
|
The following actions are missing in egress flows: move:NXM_NX_NSI[]->NXM_NX_NSI[], Example: I looked into configureVxlanGpeLastHopTransportEgressFlow method here on line 1085 (priority of flows are FLOW_PRIORITY_TRANSPORT_EGRESS + 1) And I noticed, that all the missing actions are actually being configured. The misconfigured flow can be seen here: please notice the flow Nodes config and operational DS can be also seen on robot output: |
| Comments |
| Comment by Tomas Cechvala [ 15/Jun/16 ] |
|
The bug is in stable/beryllium, boron works well. |
| Comment by Tomas Cechvala [ 15/Jun/16 ] |
|
How can this be replicated. build beryllium groupbasedpolicy distribution-karaf withouth nsu so that sfc and openflowplugin are up to date (removing those project from m2 is also a good approach) run the following demo to sum it up at this point VMs are having OVS configured and data will be send to ODL afterwards. vagrant ssh gbpsfc2 this problematic flow should be spont on one of the VMs. |
| Comment by Tomas Cechvala [ 20/Jun/16 ] |