YANG Model | Draft Name | Compilation | Compilation Results (pyang --ietf). 2.6.1 | Compilation Results (pyang). Note: also generates errors for imported files. 2.6.1 | |
---|---|---|---|---|---|
example-adm@2025-01-31.yang | draft-ietf-dtn-adm-yang-03.xml | Email Authors | PASSED WITH WARNINGS | example-adm@2025-01-31.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-" example-adm@2025-01-31.yang:3: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-adm" example-adm@2025-01-31.yang:18: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details). |
|
example-collection-manifest@2025-02-21.yang | draft-ietf-opsawg-collected-data-manifest-06.xml | Email Authors | PASSED WITH WARNINGS | example-collection-manifest@2025-02-21.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-" example-collection-manifest@2025-02-21.yang:3: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-collection-manifest" |
|
example-custom-module@2024-02-01.yang | draft-ietf-netconf-https-notif-15.txt | Email Authors | PASSED WITH WARNINGS | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" example-custom-module@2024-02-01.yang 2>&1": ietf-https-notif-transport@2024-02-01.yang:24: error: module "ietf-http-client" not found in search path ietf-https-notif-transport@2024-02-01.yang:95: error: node ietf-https-notif-transport::transport is not found |
example-custom-module@2024-02-01.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-" example-custom-module@2024-02-01.yang:3: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-custom-module" example-custom-module@2024-02-01.yang:20: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details). |
example-vendor-syslog-types@2024-03-19.yang | draft-ietf-netmod-syslog-model-33.txt | Email Authors | PASSED WITH WARNINGS | example-vendor-syslog-types@2024-03-19.yang:1: warning: RFC 8407: 4.1: the module name should start with one of the strings "ietf-" or "iana-" example-vendor-syslog-types@2024-03-19.yang:2: warning: RFC 8407: 4.9: namespace value should be "urn:ietf:params:xml:ns:yang:example-vendor-syslog-types" example-vendor-syslog-types@2024-03-19.yang:18: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details). |
|
ietf-ac-glue@2025-01-07.yang | draft-ietf-opsawg-ac-lxsm-lxnm-glue-14.xml | Email Authors | PASSED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-ac-glue@2025-01-07.yang 2>&1": ietf-ac-ntw@2025-01-07.yang:171: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for encryption-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:165) is not found ietf-ac-ntw@2025-01-07.yang:189: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for qos-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:183) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:226: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for forwarding-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:220) is not found ietf-ac-ntw@2025-01-07.yang:244: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for routing-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:238) is not found ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:1359): error: the key "lan" does not reference an existing leaf ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:1374): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:6: error: module "ietf-ac-common" not found in search path ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for encryption-profile-reference at ietf-ac-svc@2025-01-07.yang:94 is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for qos-profile-reference at ietf-ac-svc@2025-01-07.yang:105 is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile-reference at ietf-ac-svc@2025-01-07.yang:116 is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for forwarding-profile-reference at ietf-ac-svc@2025-01-07.yang:128 is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for routing-profile-reference at ietf-ac-svc@2025-01-07.yang:139 is not found ietf-ac-svc@2025-01-07.yang:308: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:325: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:395): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:415): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:520): error: the key "name" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:556) is not found ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:556) is not found |
|
ietf-ac-ntw@2025-01-07.yang | draft-ietf-opsawg-ntw-attachment-circuit-15.xml | Email Authors | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-ac-ntw@2025-01-07.yang 2>&1": ietf-ac-ntw@2025-01-07.yang:55: error: module "ietf-ac-common" not found in search path ietf-ac-ntw@2025-01-07.yang:171: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for encryption-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:165) is not found ietf-ac-ntw@2025-01-07.yang:189: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for qos-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:183) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:226: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for forwarding-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:220) is not found ietf-ac-ntw@2025-01-07.yang:244: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for routing-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:238) is not found ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:1359): error: the key "lan" does not reference an existing leaf ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:1374): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:827) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:827) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for encryption-profile-reference at ietf-ac-svc@2025-01-07.yang:94 is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:1066) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:1066) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for qos-profile-reference at ietf-ac-svc@2025-01-07.yang:105 is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:1030) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:1030) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile-reference at ietf-ac-svc@2025-01-07.yang:116 is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:1091) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:1091) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for forwarding-profile-reference at ietf-ac-svc@2025-01-07.yang:128 is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for routing-profile-reference at ietf-ac-svc@2025-01-07.yang:139 is not found ietf-ac-svc@2025-01-07.yang:308: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:325: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:395): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:415): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:520): error: the key "name" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:556) is not found ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:556) is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-ac-ntw@2025-01-07.yang --ietf 2>&1": ietf-ac-ntw@2025-01-07.yang:55: error: module "ietf-ac-common" not found in search path ietf-ac-ntw@2025-01-07.yang:171: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for encryption-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:165) is not found ietf-ac-ntw@2025-01-07.yang:189: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for qos-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:183) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:208: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for failure-detection-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:202) is not found ietf-ac-ntw@2025-01-07.yang:226: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for forwarding-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:220) is not found ietf-ac-ntw@2025-01-07.yang:244: error: "ietf-ac-ntw:valid-provider-identifiers" in the path for routing-profile-ref at ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:238) is not found ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:1359): error: the key "lan" does not reference an existing leaf ietf-ac-ntw@2025-01-07.yang:1994 (at ietf-ac-ntw@2025-01-07.yang:1374): error: the key "lan" does not reference an existing leaf |
ietf-ac-svc@2025-01-07.yang | draft-ietf-opsawg-teas-attachment-circuit-20.xml | Email Authors | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-ac-svc@2025-01-07.yang 2>&1": ietf-ac-svc@2025-01-07.yang:6: error: module "ietf-ac-common" not found in search path ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for encryption-profile-reference at ietf-ac-svc@2025-01-07.yang:94 is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for qos-profile-reference at ietf-ac-svc@2025-01-07.yang:105 is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile-reference at ietf-ac-svc@2025-01-07.yang:116 is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for forwarding-profile-reference at ietf-ac-svc@2025-01-07.yang:128 is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for routing-profile-reference at ietf-ac-svc@2025-01-07.yang:139 is not found ietf-ac-svc@2025-01-07.yang:308: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:325: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:395): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:415): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:520): error: the key "name" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:556) is not found ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:556) is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-ac-svc@2025-01-07.yang --ietf 2>&1": ietf-ac-svc@2025-01-07.yang:6: error: module "ietf-ac-common" not found in search path ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for encryption-profile-reference at ietf-ac-svc@2025-01-07.yang:94 is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for qos-profile-reference at ietf-ac-svc@2025-01-07.yang:105 is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile-reference at ietf-ac-svc@2025-01-07.yang:116 is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for forwarding-profile-reference at ietf-ac-svc@2025-01-07.yang:128 is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for routing-profile-reference at ietf-ac-svc@2025-01-07.yang:139 is not found ietf-ac-svc@2025-01-07.yang:308: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:325: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:395): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:415): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:520): error: the key "name" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:556) is not found ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:556) is not found |
ietf-bearer-svc@2025-01-07.yang | draft-ietf-opsawg-teas-attachment-circuit-19.xml | Email Authors | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-bearer-svc@2025-01-07.yang 2>&1": ietf-bearer-svc@2025-01-07.yang:17: error: module "ietf-ac-common" not found in search path ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:827) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:827) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for encryption-profile-reference at ietf-ac-svc@2025-01-07.yang:94 is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:1066) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:1066) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for qos-profile-reference at ietf-ac-svc@2025-01-07.yang:105 is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:1030) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:1030) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile-reference at ietf-ac-svc@2025-01-07.yang:116 is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:1091) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:1091) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for forwarding-profile-reference at ietf-ac-svc@2025-01-07.yang:128 is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for routing-profile-reference at ietf-ac-svc@2025-01-07.yang:139 is not found ietf-ac-svc@2025-01-07.yang:308: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:325: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:395): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:415): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:520): error: the key "name" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1159 (at ietf-ac-svc@2025-01-07.yang:556) is not found ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1246 (at ietf-ac-svc@2025-01-07.yang:556) is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-bearer-svc@2025-01-07.yang --ietf 2>&1": ietf-bearer-svc@2025-01-07.yang:17: error: module "ietf-ac-common" not found in search path |
ietf-bgp-communities@2025-03-13.yang | draft-ietf-grow-yang-bgp-communities-04.xml | Email Authors | PASSED | ||
ietf-energy-saving-common@2024-01-23.yang | draft-cwbgp-green-energy-saving-management-01.xml | Email Authors | PASSED | ||
ietf-foo@2016-03-20.yang | draft-ietf-netmod-rfc8407bis-21.xml | Email Authors | PASSED WITH WARNINGS | ietf-foo@2016-03-20.yang:7: warning: RFC 8407: 3.1: The IETF Trust Copyright statement seems to be missing or is not correct (see pyang --ietf-help for details). ietf-foo@2016-03-20.yang:7: warning: RFC 8407: Appendix B: The text about which RFC this module is part of seems to be missing or is not correct (see pyang --ietf-help for details). |
|
ietf-inet-types@2024-10-21.yang | draft-ietf-netmod-rfc6991-bis-17.xml | Email Authors | PASSED | ||
ietf-network-inventory-entitlements-features@2024-04-09.yang | draft-mcd-ivy-entitlements-inventory-00.xml | Email Authors | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-network-inventory-entitlements-features@2024-04-09.yang 2>&1": ietf-network-inventory-entitlements-features@2024-04-09.yang:3: error: the escape sequence "\ " is illegal in double quoted strings |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-network-inventory-entitlements-features@2024-04-09.yang --ietf 2>&1": ietf-network-inventory-entitlements-features@2024-04-09.yang:3: error: the escape sequence "\ " is illegal in double quoted strings |
ietf-network-slice-mapping@2025-01-29.yang | draft-dhody-teas-ietf-network-slice-mapping-06.xml | Email Authors | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-network-slice-mapping@2025-01-29.yang 2>&1": ietf-network-slice-mapping@2025-01-29.yang:18: error: module "ietf-te-service-mapping-types" not found in search path ietf-network-slice-mapping@2025-01-29.yang:34: error: module "ietf-nrp" not found in search path ietf-network-slice-service@2025-01-27.yang:39: error: module "ietf-ac-common" not found in search path ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for provider-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:828) is not found ietf-ac-svc@2025-01-07.yang:99: error: "ietf-ac-svc:valid-provider-identifiers" in the path for encryption-profile-reference at ietf-ac-svc@2025-01-07.yang:94 is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1067) is not found ietf-ac-svc@2025-01-07.yang:110: error: "ietf-ac-svc:valid-provider-identifiers" in the path for qos-profile-reference at ietf-ac-svc@2025-01-07.yang:105 is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:399) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:419) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:563) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1031) is not found ietf-ac-svc@2025-01-07.yang:122: error: "ietf-ac-svc:valid-provider-identifiers" in the path for failure-detection-profile-reference at ietf-ac-svc@2025-01-07.yang:116 is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for profile at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:1092) is not found ietf-ac-svc@2025-01-07.yang:133: error: "ietf-ac-svc:valid-provider-identifiers" in the path for forwarding-profile-reference at ietf-ac-svc@2025-01-07.yang:128 is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for id at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:372) is not found ietf-ac-svc@2025-01-07.yang:144: error: "ietf-ac-svc:valid-provider-identifiers" in the path for routing-profile-reference at ietf-ac-svc@2025-01-07.yang:139 is not found ietf-ac-svc@2025-01-07.yang:308: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:325: error: node ietf-ac-svc::allocation-type is not found ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:395): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:415): error: the key "lan" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:520): error: the key "name" does not reference an existing leaf ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1160 (at ietf-ac-svc@2025-01-07.yang:556) is not found ietf-ac-svc@2025-01-07.yang:558: error: "ietf-ac-svc:name" in the path for peer-group at ietf-ac-svc@2025-01-07.yang:1247 (at ietf-ac-svc@2025-01-07.yang:556) is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-network-slice-mapping@2025-01-29.yang --ietf 2>&1": ietf-network-slice-mapping@2025-01-29.yang:18: error: module "ietf-te-service-mapping-types" not found in search path ietf-network-slice-mapping@2025-01-29.yang:34: error: module "ietf-nrp" not found in search path |
ietf-ni-energy-saving@2024-01-23.yang | draft-cwbgp-green-energy-saving-management-01.xml | Email Authors | PASSED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-ni-energy-saving@2024-01-23.yang 2>&1": ietf-energy-efficiency-common@2024-01-23.yang:3: error: the escape sequence "\ " is illegal in double quoted strings |
|
ietf-ntw-energy-saving@2024-01-23.yang | draft-cwbgp-green-energy-saving-management-01.xml | Email Authors | PASSED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/yang/modules" ietf-ntw-energy-saving@2024-01-23.yang 2>&1": ietf-energy-efficiency-common@2024-01-23.yang:3: error: the escape sequence "\ " is illegal in double quoted strings |
|
ietf-system-tacacs-plus@2025-01-23.yang | draft-ietf-opsawg-secure-tacacs-yang-09.xml | Email Authors | PASSED | ||
ietf-yang-types@2024-10-21.yang | draft-ietf-netmod-rfc6991-bis-17.xml | Email Authors | PASSED |