Config ipv4 address(openconfig-interface-ip.yang) failed Error "Unexpected valid opaque node list "address" about sysrepo HOT 8 CLOSED

It all depends on the YANG modules you are using, I am guessing that address has a different key than ip or something like that.

from sysrepo.

It all depends on the YANG modules you are using, I am guessing that address has a different key than ip or something like that.

The yang content like this, address only have one key: ip

    container ipv4 {
      description
        "Parameters for the IPv4 address family.";

      container addresses {
        description
          "Enclosing container for address list";

        list address {
          key "ip";
          description
           "The list of configured IPv4 addresses on the interface.";

          leaf ip {
            type leafref {
              path "../config/ip";
            }
            description "References the configured IP address";
          }

          container config {
            description "Configuration data for each configured IPv4
            address on the interface";

            uses ipv4-address-config;

          }

          container state {

            config false;
            description "Operational state data for each IPv4 address
            configured on the interface";

            uses ipv4-address-config;
            uses ipv4-address-state;
          }

        }
      }

  grouping ipv4-address-config {

    description
      "Per IPv4 adresss configuration data for the
      interface.";

    leaf ip {
       type oc-inet:ipv4-address;
       description
        "The IPv4 address on the interface.";
    }

    leaf prefix-length {
      type uint8 {
       range "0..32";
      }
      description
       "The length of the subnet prefix.";
    }

    leaf gwaddr {
       type oc-inet:ipv4-address;
       description
        "The IPv4 gwaddress on the interface.";
    }
  }

And pyyang generate tree：

Is there any other possible reason？@michalvasko

from sysrepo.

If you provide the YANG modules (and all their imports) I can tell you exactly because I could not reproduce it (have tried it with some revisions that did not define mtu node).

from sysrepo.

yang.zip

My yang file is in the compressed file， thank you very much @michalvasko
Or you can delete mtu attribute

from sysrepo.

My version (current) prints the error

[ERR]: SR: Unsatisfied pattern - "8.8.177.28" does not conform to "^(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])$". (Data location "/openconfig-interfaces:interfaces/interface[name='Ethernet4']/subinterfaces/subinterface[index='0']/openconfig-if-ip:ipv4/addresses/address/ip".)

and the reason being discussed in openconfig/public#44.

from sysrepo.

Thansk for you replay!
I cannot upgrade to the latest version. When I upgrade, I have encountered issues, such as OpenSSL and libyang have already been used by other modules in the linux system.
Are there any other suggestions ? Which patch in sysrepo or libyang I merge to, maybe can solve this problem? @michalvasko

from sysrepo.

When I upgrade, I have encountered issues, such as OpenSSL and libyang have already been used by other modules in the linux system.

I do not understand, why should a newer version cause problems, you have packages that depend on an exact libyang version instead of specifying a minimal supported version?

But, strictly speaking, an update will not solve your problem, the value will still fail to load because the pattern is in an unsupported format (described in the issue I have referenced, please read it).

from sysrepo.

I upgrade to this version tag: netopeer v2.1.71, sysrepo v2.2.105, libyang v2.1.111, and now prints the pattern error. For this issue you have referenced above, I will try some methods mentioned in that issue.
Thanks for your help.

from sysrepo.