Missing flow for wanedge

[akry]

One of the flows required for address translation is missing. This rarely happens thus it is quite difficult to reproduce but mostly can be recognized when vna receives the packets during its initialization. Almost the same issue happens in the integration test for service scenario.

Expected flows for wanedge on table 35 is following:

(35): TABLE_ROUTE_EGRESS_LOOKUP
 35-00        0       0 => SWITCH(0x0)               actions=drop
 35-20        0       0 => INTERFACE(0x4)[0x12]     metadata=VALUE_PAIR(0x8000000400000000/0xffffffff00000000)(0x0) actions=write_metadata:0x702000000000004,goto_table:TABLE_ROUTE_EGRESS_TRANSLATION(36)
 35-20     2832       0 => INTERFACE(0x5)[0x12]     metadata=VALUE_PAIR(0x8000000500000000/0xffffffff00000000)(0x0) actions=write_metadata:0x702000000000005,goto_table:TABLE_ROUTE_EGRESS_TRANSLATION(36)
 35-50     1536       0 => TRANSLATION(0x1)         ip,metadata=VALUE_PAIR(0x8000000400000001/0xffffffff7fffffff)(0x1),nw_src=10.100.0.3 actions=set_field:10.255.213.100->ip_src,write_metadata:0x702000000000004,goto_table:TABLE_ROUTE_EGRESS_INTERFACE(37)

35-50     1536       0 => TRANSLATION(0x1)         ip,metadata=VALUE_PAIR(0x8000000400000001/0xffffffff7fffffff)(0x1),nw_src=10.100.0.3 actions=set_field:10.255.213.100->ip_src,write_metadata:0x702000000000004,goto_table:TABLE_ROUTE_EGRESS_INTERFACE(37)

This flow is missing because of this issue. If you wait long enough until the initialization gets done then start sending the packets, this issue won't happen.