[GENIUS-22] getEgressInstructionsForInterface: Bad instructions returned Created: 21/Sep/16 Updated: 05/Oct/16 Resolved: 05/Oct/16 |
|
| Status: | Resolved |
| Project: | genius |
| Component/s: | General |
| Affects Version/s: | (unspecified) |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Diego Granados | Assignee: | Miguel Duarte de Mora Barroso |
| 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: | 6776 |
| Priority: | Low |
| Description |
|
getEgressInstructionsForInterface rpc method in interface manager component returns incorrect instructions. E.g, for a given vlan interface, the returned instructions: <instructions> are incorrect (i.e. contain nx-reg-load action inside a write-action deferred set, which fails when written to OVS (BADACTION / BADTYPE error code). A valid workaround is to use getEgressActions() instead and then wrap the returned actions into an applyAction container. This bug is created so getEgressInstructions method can also be corrected Reported in: Boron release |
| Comments |
| Comment by Miguel Duarte de Mora Barroso [ 05/Oct/16 ] |
|
Like indicated in the bug report, the actions returned (which are correct) should be encapsulated in an apply-actions instruction - not within a write-actions instruction - given the need for those actions to be acted upon immediately, and not at the end of the pipeline. |
| Comment by Miguel Duarte de Mora Barroso [ 05/Oct/16 ] |