When I run VTN Manager with the new OF plugin, I had VTN Manager install flow entries which has a value in IN_PORT match field, and I got information of flow entries using REST API provided by statistics service.
However, I cannot see IN_PORT match field in the response message of the REST API.

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

$ pwd
/home/odp/work/integration

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 bridge 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 '

'

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":

, "port": {"name": "s3-eth1"}}'

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":

, "port": {"name": "s7-eth2"}}'

3. Run Mininet and run OF1.3 switches.

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

4. Send ping packets from h1 to h8.

mininet> h1 ping h8

5. Check flow entries in mininet.

Confirm that a value is set in "in_port" match field in flow entries.

mininet> dpctl dump-flows -O OpenFlow13

• • • s1 ------------------------------------------------------------------------
      OFPST_FLOW reply (OF1.3) (xid=0x2):
      cookie=0x0, duration=7.587s, table=0, n_packets=7, n_bytes=630, send_flow_rem priority=10,in_port=1,vlan_tci=0x0000/0x1fff,dl_src=fe:96:3f:19:78:82,dl_dst=e6:b3:cc:03:9e:37 actions=output:2
      cookie=0x0, duration=7.626s, table=0, n_packets=7, n_bytes=630, send_flow_rem priority=10,in_port=2,vlan_tci=0x0000/0x1fff,dl_src=e6:b3:cc:03:9e:37,dl_dst=fe:96:3f:19:78:82 actions=output:1
      (sinp)

6. Get flow entries using REST API

curl --user "admin":"admin" -H "Accept: application/json" -H \
"Content-type: application/json" -X GET \
http://192.168.60.180:8080/controller/nb/v2/statistics/default/flow/node/MD_SAL/openflow:1

Confirm that the match values of the response doesn't contain "In Port" field.

{
"flowStatistic": [
{
"byteCount": 630,
"durationNanoseconds": 385000000,
"durationSeconds": 45,
"flow": {
"actions": [
{
"port": {
"id": "openflow:1:2",
"node":

,
"type": "MD_SAL"
},
"type": "OUTPUT"
}
],
"hardTimeout": 0,
"id": 0,
"idleTimeout": 0,
"match": {
"matchField": [

,

,

]
},
"priority": 10
},
"packetCount": 7,
"tableId": 0
},
{
"byteCount": 630,
"durationNanoseconds": 424000000,
"durationSeconds": 45,
"flow": {
"actions": [
{
"port": {
"id": "openflow:1:1",
"node":

,
"type": "MD_SAL"
},
"type": "OUTPUT"
}
],
"hardTimeout": 0,
"id": 0,
"idleTimeout": 0,
"match": {
"matchField": [

,

,

]
},
"priority": 10
},
"packetCount": 7,
"tableId": 0
}
],
"node":

}