Details
-
Bug
-
Status: Resolved
-
Resolution: Done
-
(unspecified)
-
None
-
None
-
Operating System: All
Platform: All
-
6776
-
Low
Description
getEgressInstructionsForInterface rpc method in interface manager component returns incorrect instructions. E.g, for a given vlan interface, the returned instructions:
<instructions>
<instruction>
<order>0</order>
<write-actions>
<action>
<order>1</order>
<nx-resubmit>
<table>220</table>
</nx-resubmit>
</action>
<action>
<order>0</order>
<nx-reg-load>
<value>512</value>
<dst>
<nx-reg>x:nxm-nx-reg6</nx-reg>
<start>0</start>
<end>31</end>
</dst>
</nx-reg-load>
</action>
</write-actions>
</instruction>
</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