Operating System: Mac OS
Platform: PC

Attachment ODL_VLAN.json has been added with description: Postman collection script to reproduce the problem

Using ODL I am trying to inject a flow in which actions are specified in order such that the VLAN header is pushed first followed by the the vlan id.

However when I dump the flow on the OVS using ovs-ofctl the order seems to be
reversed.

priority=1,arp,dl_src=01:aa:bb:cc:dd:ee actions=set_field:3333->vlan_vid,push_vlan:0x8100,goto_table:21

I am attaching a POSTMAN script (use Push_vlan) which will help reproduce the problem.

Here the XML data that I am pushing using ODL

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<flow xmlns="urn:opendaylight:flow:inventory">
<priority>1</priority>
<flow-name>PushVlan</flow-name>
<match>
<ethernet-match>
<ethernet-type>
<type>2054</type>
</ethernet-type>
<ethernet-source>
<address>01:aa:bb:cc:dd:ee</address>
</ethernet-source>
</ethernet-match>
</match>
<id>2</id>
<table_id>20</table_id>
<instructions>
<instruction>
<order>1</order>
<apply-actions>
<action>
<order>1</order>
<push-vlan-action>
<ethernet-type>0x8100</ethernet-type>
</push-vlan-action>
</action>
<action>
<order>2</order>
<set-field>
<vlan-match>
<vlan-id>
<vlan-id>3333</vlan-id>
<vlan-id-present>true</vlan-id-present>
</vlan-id>
</vlan-match>
</set-field>
</action>
</apply-actions>
</instruction>
<instruction>
<order>2</order>
<go-to-table>
<table_id>21</table_id>
</go-to-table>
</instruction>
</instructions>
</flow>

Actions are received from Openflow Plugin as a list. Openflowjava writes actions in the same order as the list is filled. So it is ofplugin's responsibility to handle actions according to order specified in someone's input.

Same bug already exists for openflowplugin project (1338) - it just needs to be reviewed and merged.