-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
None
Nested list filtering does not work for l2-fib-entry list.
To reproduce, use HC V3PO postman collection to configure BD and L2 Fib table entries,
then issue following request:
<rpc message-id="m-1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter>
<bridge-domains-state xmlns="urn:opendaylight:params:xml:ns:yang:v3po">
<bridge-domain>
<name>testBD</name>
<l2-fib-table>
<l2-fib-entry>
<phys-address>11:22:33:44:55:66</phys-address>
</l2-fib-entry>
</l2-fib-table>
</bridge-domain>
</bridge-domains-state>
</filter>
</get>
</rpc>
]]>]]>
Reply includes all fib entries that were defined:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-1"> <data> <bridge-domains-state xmlns="urn:opendaylight:params:xml:ns:yang:v3po"> <bridge-domain> <name>testBD</name> <forward>false</forward> <learn>false</learn> <flood>true</flood> <arp-termination>false</arp-termination> <unknown-unicast-flood>false</unknown-unicast-flood> <l2-fib-table> <l2-fib-entry> <phys-address>11:22:33:44:55:66</phys-address> <static-config>true</static-config> <bridged-virtual-interface>false</bridged-virtual-interface> <action>l2-fib-forward</action> <outgoing-interface>local0</outgoing-interface> </l2-fib-entry> <l2-fib-entry> <phys-address>aa:bb:cc:dd:ee:ff</phys-address> <static-config>false</static-config> <bridged-virtual-interface>false</bridged-virtual-interface> <action>l2-fib-forward</action> <outgoing-interface>local0</outgoing-interface> </l2-fib-entry> </l2-fib-table> </bridge-domain> </bridge-domains-state> </data> </rpc-reply> ]]>]]>
Model:
grouping l2-fib-attributes {
container l2-fib-table {
list l2-fib-entry {
key "phys-address";
leaf phys-address {
type yang:phys-address;
}
[...]
}
[...]
container bridge-domains-state {
config "false";
list bridge-domain {
key "name";
leaf name {
type string;
}
[...]
uses l2-fib-attributes;
[...]
}
Following request