"Zero priority for ternary match" error when inserting exact entries into tables with optional keys. #587
Closed
Description
Trying to run a PTF test on the attached program fails with the message
Zero priority for ternary match
This is the table:
table acl_ingress_table {
key = {
h.ethernet.dst_addr : exact @name("dst_mac");
h.ipv4.src_addr : exact @name("src_ip");
h.ipv4.dst_addr : exact @name("dst_ip");
h.ipv4.ttl : optional @name("ttl");
h.ipv4.dscp : optional @name("dscp");
h.ipv4.ecn : optional @name("ecn");
h.ipv4.protocol : optional @name("ip_protocol");
}
actions = {
acl_drop(s);
@defaultonly NoAction;
}
const default_action = NoAction;
}
The PTF test omits the optional keys as they are, well, optional. However, the P4Runtime server still seems to expect some entry. Since any entry on tables with optional keys needs a priority but no priority is provided the response is an error. Is this behavior intended? Is it always required to supply a priority even though no optional key is present?
bmv2_table_opt.json.txt
bmv2_table_opt.p4info.txt
bmv2_table_opt.py.txt
ptf.log
switchlog.txt
Metadata
Assignees
Labels
No labels