Create tunnel-type-gre interface via IFM generates wrong table=0 entry

Creating a tunnel-type-gre interface via IFM should generate a table=0 entry which goes to Ingress Service Dispatcher Table, right now it goes to table=18 (which is only valid for vxlan tunnels).

Version: Boron SR1

Steps to reproduce this bug:

POST http://localhost:8181/restconf/config/ietf-interfaces:interfaces/

{ "interface": [

{ "name": "tun999a999a9a9", "type": "iana-if-type:tunnel", "odl-interface:tunnel-interface-type": "odl-interface:tunnel-type-gre", "odl-interface:datapath-node-identifier": "75356950704695", "odl-interface:tunnel-source": "172.0.22.11", "odl-interface:tunnel-destination": "192.168.3.140", "enabled": true }

]
}

Entry created in pipeline:

cookie=0x8000001, duration=9.189s, table=0, n_packets=0, n_bytes=0, priority=5,in_port=2 actions=write_metadata:0x90000000001/0x1fffff0000000001,goto_table:18

I think it should go to table=17 instead, and I don't know if the last bit in metadata is properly set.