The code assumes that these leafs always exist when their complementary
leafs exist. For example, when processing `ipv4-exact-match`, the code
always expects to have access to `ipv4-prefix`. If those leafs are not
provided, code crashes. It doesn't happen when using the CLI because it
always does the right thing, but it can happen when using other
frontends.
Also fix incorrect description for prefix-list sequence leaf.
Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
leaf ipv4-prefix {
description "Configure IPv4 prefix to match";
type inet:ipv4-prefix;
+ mandatory true;
}
leaf ipv4-exact-match {
leaf ipv6-prefix {
description "Configure IPv6 prefix to match";
type inet:ipv6-prefix;
+ mandatory true;
}
leaf ipv6-exact-match {
key "sequence";
leaf sequence {
- description "Access list sequence value";
+ description "Prefix list sequence value";
type access-list-sequence;
}
leaf ipv4-prefix {
description "Configure IPv4 prefix to match";
type inet:ipv4-prefix;
+ mandatory true;
}
leaf ipv4-prefix-length-greater-or-equal {
leaf ipv6-prefix {
description "Configure IPv6 prefix to match";
type inet:ipv6-prefix;
+ mandatory true;
}
leaf ipv6-prefix-length-greater-or-equal {