The current behaviour implemented for service binding to a tunnel interface is:

• In table 0, the first service bound
• In table 17, the rest of the services bound

When some service is already bound and a new service is going to be bound and its priority is the highest, then this new service should be bound in table 0, and the previous service that was bound in table 0 needs to be move to table 17. When the service is moved to table 17, the priority is not being installed accordingly.

1) Create the tunnel interface:
POST http://localhost:8181/restconf/config/ietf-interfaces:interfaces/
{ "interface": [

]
}

2) Bind ELAN service
POST http://localhost:8181/restconf/config/elan:elan-interfaces/
{
"elan-interface":

}

3) Bind L3VPN service
POST http://localhost:8181/restconf/config/l3vpn:vpn-interfaces/
{
"vpn-interface":
{
"name": "tun999a999a9a9",
"vpn-instance-name": "949550c9-0ac8-4fcb-96fc-2cb5bceec569",
"is-router-interface": "false",
"odl-l3vpn:adjacency": [

]
}
}

Result:

cookie=0x8000001, duration=554.072s, table=0, n_packets=82, n_bytes=3444, priority=10,in_port=4 actions=write_metadata:0xc0000600000222e2/0xffffff00ffffffff,goto_table:19

cookie=0x8040000, duration=562.817s, table=17, n_packets=0, n_bytes=0, priority=6,metadata=0xa000060000000000/0xffffff0000000000 actions=write_metadata:0xc00006138c000000/0xfffffffffffffffe,goto_table:50

The entry in table 17 is wrong.

• The metadata should be: metadata=0xc000060000000000/0xffffff0000000000
• The write_metadata should be: write_metadata:0xe00006138c000000/0xfffffffffffffffe