Wrong value in OFPXMT_OFB_VLAN_VID in FLOW_MOD using new OF plugin for OF 1.3 switches.

Values in OFPXMT_OFB_VLAN_VID field of FLOW_MOD messages were wrong, when VTN Manager run on MD-SAL and the new OF plugin, connected to OF 1.3 switches, and tried to install flow entries which match packets with VLAN tag for VLAN 100.
In this situation, the controller must set 100 into the OFPXMT_OFB_VLAN_VID field.
However, it set 0, so packets with VLAN tag for VLAN 100 didn't match the flow entries.

[What I used]
The latest version of the Virtualization Edition on 5th June.

/work/integration/distributions
odc180 $ git log -3 --oneline
90e2f0c INTEGRAT-4: Remove toaster from virt edition
64e608a Adding extra TCs for RESTCONF
3516960 Uploaded working AD-SAL cluster testcases

[How to produce]

1. Start up the Virtualization edition with of13 and vtn option.

$ ./run.sh -of13 -virt vtn

2. Create a virtual brige using REST API exposed by VTN Manager.

curl --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X POST \
http://192.168.60.180:8080/controller/nb/v2/vtn/default/vtns/vtn1 \
-d '

{"description": "Virtual Tenat 1 for Hackfest network"}

'

curl --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X POST \
http://192.168.60.180:8080/controller/nb/v2/vtn/default/vtns/vtn1/vbridges/vbr1 \
-d '{}'

curl --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X POST \
http://192.168.60.180:8080/controller/nb/v2/vtn/default/vtns/vtn1/vbridges/vbr1/interfaces/if1 \
-d '{}'

curl --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X POST \
http://192.168.60.180:8080/controller/nb/v2/vtn/default/vtns/vtn1/vbridges/vbr1/interfaces/if2 \
-d '{}'

curl --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X PUT \
http://192.168.60.180:8080/controller/nb/v2/vtn/default/vtns/vtn1/vbridges/vbr1/interfaces/if1/portmap \
-d '{"node":

{"type":"MD_SAL","id":"openflow:3"}

, "port":

{"name": "s3-eth1"}

, "vlan": "100"}'

curl --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X PUT \
http://192.168.60.180:8080/controller/nb/v2/vtn/default/vtns/vtn1/vbridges/vbr1/interfaces/if2/portmap \
-d '{"node":

{"type":"MD_SAL","id":"openflow:7"}

, "port":

{"name": "s7-eth2"}

, "vlan": "100"}'

3. Run Mininet and run OF1.3 switches.

$ sudo mn --controller=remote,192.168.60.180 --topo tree,3 --switch=ovsk,protocols=of13

4. Configure hosts for sending packets with VLAN tag.

h1 ifconfig h1-eth0 inet 0.0.0.0
h1 vconfig add h1-eth0 100
h1 ifconfig h1-eth0.100
h1 ifconfig h1-eth0.100 inet 10.0.0.1/8

h8 ifconfig h8-eth0 inet 0.0.0.0
h8 vconfig add h8-eth0 100
h8 ifconfig h8-eth0.100
h8 ifconfig h8-eth0.100 inet 10.0.0.8/8

5. Send ping packets from h1 to h8 (10.0.0.8).

mininet> h1 ping 10.0.0.8

At this time, VTN Manager tries to install flow entries to forward packets between h1 and h8 based on the vtn configuration (See step 2).