| YANG Model | Compilation | Compilation Results (pyang --lint). 2.6.1 | Compilation Results (pyang). Note: also generates errors for imported files. 2.6.1 | Compilation Results (confdc). Note: also generates errors for imported files. confd-8.0 | Compilation Results (yangdump-pro). Note: also generates errors for imported files. yangdump-sdk 21.10-12 | Compilation Results (yanglint -i). Note: also generates errors for imported files. yanglint 2.1.111 |
|---|---|---|---|---|---|---|
| dhcp-client-dev@2015-09-11.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/dhcp-client-dev.yang 2>&1": dhcp-client-dev.yang:5: error: module 'dhcp-client' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" dhcp-client-dev.yang --lint 2>&1": dhcp-client-dev.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/dhcp-client-dev.yang 2>&1": Error: 'dhcp-client-dev.yang' import of module 'dhcp-client' failed dhcp-client-dev.yang:5.5: error(236): module not found Error: object 'clientv4' not found in module dhcp-client-dev in Xpath target /dhcp:clientv4/dhcp:client-if dhcp-client-dev.yang:42.2: error(250): definition not found Error: object 'serverv4' not found in module dhcp-client-dev in Xpath target /dhcp:serverv4 dhcp-client-dev.yang:42.2: error(250): definition not found Error: object 'relayv4' not found in module dhcp-client-dev in Xpath target /dhcp:relayv4 dhcp-client-dev.yang:42.2: error(250): definition not found |
||
| dhcp-client@2014-12-18.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" dhcp-client@2014-12-18.yang --lint 2>&1": dhcp-client@2014-12-18.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement dhcp-client@2014-12-18.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement dhcp-client@2014-12-18.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement dhcp-client@2014-12-18.yang:14: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:15: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:16: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client@2014-12-18.yang:20: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:21: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:22: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:26: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:27: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:28: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:29: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:33: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:34: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:35: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:39: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:40: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:41: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:45: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:52: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:53: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:54: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:58: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:60: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:64: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:65: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:66: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:70: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:71: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:72: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:74: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:78: error: keyword "key" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:79: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:82: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:86: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:90: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:98: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:102: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:110: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:114: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:118: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:122: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:130: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:134: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:142: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:143: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:147: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:151: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:155: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:159: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:163: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:167: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:171: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:175: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:179: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:183: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:187: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:191: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:195: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:199: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:203: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:207: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client@2014-12-18.yang:213: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:214: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:217: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:218: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:221: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:222: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:226: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:227: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:230: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:231: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:234: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:235: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client@2014-12-18.yang:239: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:240: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:243: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:247: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:248: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:251: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:253: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:256: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:257: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:258: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:262: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:263: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:264: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:267: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:268: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client@2014-12-18.yang:272: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:273: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:276: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:280: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:281: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:282: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:283: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:287: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:288: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:289: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:290: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:292: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:295: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:296: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:297: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:301: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:302: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:303: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:307: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:308: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:309: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:313: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:314: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:315: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:325: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:326: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:329: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:330: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:334: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:335: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:338: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:339: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:343: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:344: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:347: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:348: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:353: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:354: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:355: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:359: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:360: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:363: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:367: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:368: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:369: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:373: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:374: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:388: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:390: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:394: error: keyword "key" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:397: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:398: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:401: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:405: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:406: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:407: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:411: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:412: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:415: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:419: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:420: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:423: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:427: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:430: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:431: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:432: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:436: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:437: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:438: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:442: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:443: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:444: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:448: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:449: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:450: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:455: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client@2014-12-18.yang:458: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:459: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:460: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:464: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:465: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:466: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:470: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:471: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:472: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:476: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:477: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:478: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:482: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:483: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:484: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:488: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:489: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:490: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:494: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:495: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:496: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:500: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:501: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:502: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:506: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:507: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:508: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:512: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:513: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:514: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:521: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client@2014-12-18.yang:525: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:526: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:527: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:531: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:532: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:533: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:534: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:541: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:542: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:549: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:553: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:554: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:555: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:559: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:560: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:561: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:569: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:570: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:571: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:575: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:576: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:577: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:581: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:582: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:583: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:587: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:588: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:589: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:593: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:594: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:595: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:599: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:600: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:601: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:605: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:606: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:607: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:611: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:612: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client@2014-12-18.yang:613: error: keyword "config" not in canonical order (see RFC 6020, Section 12) |
||||
| dhcpv6-client-dev@2016-03-10.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/dhcpv6-client-dev.yang 2>&1": dhcpv6-client-dev.yang:5: error: module 'dhcpv6-client' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" dhcpv6-client-dev.yang --lint 2>&1": dhcpv6-client-dev.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/dhcpv6-client-dev.yang 2>&1": Error: 'dhcpv6-client-dev.yang' import of module 'dhcpv6-client' failed dhcpv6-client-dev.yang:5.3: error(236): module not found Error: object 'serverv6' not found in module dhcpv6-client-dev in Xpath target /dhcpv6:serverv6 dhcpv6-client-dev.yang:43.2: error(250): definition not found Error: object 'relayv6' not found in module dhcpv6-client-dev in Xpath target /dhcpv6:relayv6 dhcpv6-client-dev.yang:43.2: error(250): definition not found Error: object 'clientv6' not found in module dhcpv6-client-dev in Xpath target /dhcpv6:clientv6/dhcpv6:client-if dhcpv6-client-dev.yang:43.2: error(250): definition not found |
||
| dhcpv6-client@2015-10-16.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" dhcpv6-client@2015-10-16.yang --lint 2>&1": dhcpv6-client@2015-10-16.yang:136: error: RFC 8407: 4.10: top-level node serverv6 must not be mandatory dhcpv6-client@2015-10-16.yang:1677: error: RFC 8407: 4.10: top-level node relayv6 must not be mandatory |
Warning: top-level NP container 'serverv6' is mandatory dhcpv6-client@2015-10-16.yang:136.3: warning(1048): top-level object is mandatory Warning: top-level NP container 'relayv6' is mandatory dhcpv6-client@2015-10-16.yang:1677.3: warning(1048): top-level object is mandatory |
|||
| fujitsu-access-control-list@2015-11-09.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-access-control-list@2015-11-09.yang 2>&1": fujitsu-access-control-list@2015-11-09.yang:51: error: the node 'access-lists' from module 'ietf-access-control-list' is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-access-control-list@2015-11-09.yang 2>&1": fujitsu-access-control-list@2015-11-09.yang:12: warning: imported module "ietf-yang-types" not used fujitsu-access-control-list@2015-11-09.yang:51: error: "ietf-access-control-list:access-lists" in the path for acl-name at fujitsu-access-control-list@2015-11-09.yang:47 is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-access-control-list@2015-11-09.yang --lint 2>&1": fujitsu-access-control-list@2015-11-09.yang:9: warning: imported module "ietf-access-control-list" not used fujitsu-access-control-list@2015-11-09.yang:12: warning: imported module "ietf-yang-types" not used fujitsu-access-control-list@2015-11-09.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-access-control-list@2015-11-09.yang:42: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-access-control-list@2015-11-09.yang:49: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-access-control-list@2015-11-09.yang:50: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/fujitsu-access-control-list@2015-11-09.yang 2>&1": libyang err : Not found node "access-lists" in path. (Schema location "/ietf-interfaces:interfaces/interface/fujitsu-access-control-list:acl/acl-name".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-access-control-list@2015-11-09.yang 2>&1": Error: 'fujitsu-access-control-list@2015-11-09.yang' import of module 'ietf-access-control-list' failed fujitsu-access-control-list@2015-11-09.yang:9.3: error(236): module not found Error: path failed (module not found): '/acl:access-lists/acl:acl/acl:acl-name' Error: Module for prefix 'acl' not found fujitsu-access-control-list@2015-11-09.yang:51.17: error(236): module not found Warning: Module 'ietf-yang-types' not used fujitsu-access-control-list@2015-11-09.yang:12.3: warning(1015): import not used |
| fujitsu-ains-keywords@2018-05-17.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ains-keywords@2018-05-17.yang --lint 2>&1": fujitsu-ains-keywords@2018-05-17.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ains-keywords@2018-05-17.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ains-keywords@2018-05-17.yang:58: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ains-keywords@2018-05-17.yang:59: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ains-keywords@2018-05-17.yang:61: warning: RFC 8407: 4.4: statement "mandatory" is given with its default value "false" fujitsu-ains-keywords@2018-05-17.yang:62: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ains-keywords@2018-05-17.yang:64: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ains-keywords@2018-05-17.yang:68: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
||||
| fujitsu-alarm-types@2018-06-01.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-alarm-types@2018-06-01.yang 2>&1": fujitsu-alarm-types@2018-06-01.yang:155: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:159: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:163: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:169: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:173: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:177: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:181: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:185: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:189: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:193: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:197: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:201: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:205: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:209: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:213: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:217: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:221: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:225: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:229: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:233: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:237: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:241: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:245: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:249: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:253: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:257: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:261: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:265: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:269: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:273: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:277: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:281: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:285: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:289: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:293: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:297: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:301: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:305: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:309: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:313: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:317: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:321: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:325: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:329: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:333: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:337: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:341: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:345: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:349: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:353: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:357: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:361: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:365: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:369: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:373: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:377: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:381: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:385: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:389: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:393: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:397: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:401: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:405: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:409: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:413: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:417: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:421: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:425: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:429: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:433: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:437: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:441: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:445: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:449: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:453: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:457: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:461: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:465: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:469: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:473: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:477: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:481: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:485: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:489: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:493: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:497: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:501: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:505: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:509: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:513: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:517: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:521: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:525: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:529: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:533: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:537: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:541: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:545: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:549: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:553: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:557: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:561: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:565: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:569: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:573: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:577: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:581: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:585: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:589: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:593: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:597: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:601: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:605: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:609: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:613: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:617: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:621: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:625: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:629: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:633: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:637: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:641: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:645: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:649: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:653: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:657: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:661: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:665: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:669: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:673: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:677: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:681: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:685: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:689: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:693: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:697: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:701: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:705: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:709: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:713: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:717: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:721: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:725: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:729: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:733: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:737: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:741: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:745: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:749: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:753: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:757: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:761: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:765: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:769: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:773: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:777: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:781: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:785: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:789: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:793: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:797: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:801: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:805: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:809: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:813: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:817: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:821: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:825: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:829: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:833: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:837: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:841: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:845: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:849: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:853: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:857: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:861: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:865: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:869: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:873: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:877: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:881: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:885: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:889: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:893: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:897: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:901: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:905: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:909: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:913: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:917: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:921: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:925: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:929: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:933: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:937: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:941: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:945: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:949: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:953: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:957: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:961: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:965: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:969: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:973: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:977: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:981: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:985: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:989: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:993: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:997: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1001: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1005: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1009: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1013: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1017: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1021: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1025: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1029: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1033: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1037: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1041: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1045: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1049: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1053: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1057: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1061: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1065: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1069: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1073: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1077: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1081: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1085: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1089: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1093: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1097: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1101: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1105: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1109: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1113: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1117: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1121: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1125: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1129: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1133: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1137: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1141: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1145: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1149: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1153: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1157: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1161: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1165: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1169: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1173: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1177: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1181: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1185: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1189: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1193: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1197: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1201: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1205: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1209: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1213: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1217: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1221: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1225: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1229: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1233: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1237: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1241: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1245: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1249: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1253: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1257: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1261: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1265: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1269: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1273: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1277: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1281: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1285: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1289: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1293: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1297: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1301: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1305: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1309: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1313: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1317: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1321: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1325: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1329: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1333: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1337: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1341: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1345: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1349: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1353: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1357: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1361: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1365: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1369: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1373: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1377: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1381: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1385: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1389: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1393: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1397: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1401: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1405: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1409: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1413: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1417: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1421: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1425: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1429: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1433: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1437: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1441: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1445: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1449: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1453: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1457: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1461: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1465: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1469: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1473: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1477: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1481: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1485: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1489: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1493: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1497: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1501: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1505: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1509: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1513: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1517: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1521: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1525: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1529: error: identity 'alarm-identity' in module 'ietf-alarms' not found fujitsu-alarm-types@2018-06-01.yang:1533: error: identity 'alarm-identity' in module 'ietf-alarms' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-alarm-types@2018-06-01.yang 2>&1": fujitsu-alarm-types@2018-06-01.yang:155: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:159: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:163: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:169: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:533: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:537: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:541: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:545: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:549: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:553: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:557: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:561: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:565: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:569: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:573: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:577: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:581: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:585: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:589: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:593: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:597: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:601: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:605: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:609: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:613: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:617: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:621: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:625: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:629: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:633: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:637: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:641: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:645: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:649: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:653: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:657: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:661: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:665: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:669: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:673: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:677: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:681: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:685: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:689: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:693: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:697: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:701: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:705: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:709: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:713: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:717: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:721: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:725: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:729: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:733: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:737: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:741: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:745: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:749: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:753: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:757: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:761: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:765: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:769: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:773: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:777: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:781: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:785: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:789: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:793: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:797: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:801: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:805: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:809: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:813: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:817: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:821: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:825: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:829: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:833: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:837: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:841: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:845: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:849: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:853: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:857: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:861: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:865: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:869: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:873: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:877: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:881: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:885: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:889: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:893: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:897: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:901: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:905: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:909: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:913: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:917: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:921: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:925: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:929: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:933: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:937: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:941: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:945: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:949: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:953: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:957: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:961: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:965: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:969: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:973: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:977: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:981: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:985: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:989: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:993: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:997: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1001: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1005: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1009: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1013: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1017: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1021: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1025: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1029: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1033: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1037: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1041: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1045: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1049: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1053: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1057: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1061: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1065: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1069: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1073: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1077: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1081: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1085: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1089: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1093: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1097: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1101: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1105: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1109: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1113: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1117: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1121: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1125: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1129: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1133: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1137: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1141: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1145: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1149: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1153: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1157: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1161: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1165: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1169: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1533: error: identity "alarm-identity" not found in module "ietf-alarms" |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-alarm-types@2018-06-01.yang --lint 2>&1": fujitsu-alarm-types@2018-06-01.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:74: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:78: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:82: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:86: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:90: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:94: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:98: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:102: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:106: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:110: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:115: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:121: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:125: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:130: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:135: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:139: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:143: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:147: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:151: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:155: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:155: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:159: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:159: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:163: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types@2018-06-01.yang:163: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types@2018-06-01.yang:168: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:169: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:172: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:176: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:180: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:184: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:188: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:192: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:196: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:200: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:204: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:208: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:212: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:216: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:220: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:224: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:228: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:232: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:236: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:240: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:244: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:248: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:252: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:256: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:260: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:264: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:268: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:272: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:276: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:280: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:284: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:288: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:292: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:296: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:300: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:304: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:308: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:312: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:316: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:320: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:324: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:328: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:332: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:336: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:340: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:344: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:348: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:352: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:356: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:360: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:364: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:368: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:372: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:376: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:380: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:384: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:388: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:392: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:396: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:400: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:404: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:408: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:412: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:416: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:420: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:424: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:428: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:432: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:436: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:440: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:444: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:448: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:452: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:456: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:460: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:464: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:468: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:472: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:476: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:480: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:484: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:488: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:492: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:496: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:500: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:504: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:508: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:512: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:516: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:520: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:524: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:528: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:532: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:533: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:536: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:537: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:540: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:541: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:544: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:545: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:548: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:549: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:552: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:553: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:556: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:557: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:560: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:561: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:564: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:565: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:568: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:569: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:572: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:573: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:576: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:577: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:580: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:581: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:584: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:585: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:588: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:589: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:592: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:593: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:596: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:597: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:600: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:601: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:604: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:605: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:608: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:609: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:612: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:613: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:616: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:617: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:620: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:621: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:624: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:625: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:628: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:629: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:632: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:633: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:636: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:637: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:640: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:641: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:644: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:645: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:648: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:649: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:652: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:653: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:656: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:657: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:660: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:661: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:664: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:665: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:668: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:669: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:672: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:673: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:676: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:677: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:680: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:681: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:684: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:685: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:688: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:689: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:692: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:693: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:696: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:697: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:700: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:701: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:704: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:705: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:708: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:709: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:712: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:713: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:716: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:717: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:720: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:721: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:724: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:725: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:728: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:729: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:732: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:733: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:736: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:737: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:740: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:741: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:744: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:745: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:748: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:749: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:752: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:753: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:756: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:757: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:760: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:761: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:764: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:765: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:768: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:769: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:772: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:773: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:776: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:777: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:780: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:781: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:784: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:785: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:788: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:789: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:792: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:793: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:796: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:797: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:800: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:801: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:804: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:805: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:808: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:809: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:812: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:813: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:816: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:817: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:820: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:821: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:824: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:825: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:828: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:829: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:832: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:833: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:836: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:837: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:840: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:841: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:844: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:845: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:848: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:849: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:852: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:853: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:856: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:857: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:860: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:861: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:864: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:865: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:868: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:869: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:872: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:873: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:876: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:877: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:880: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:881: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:884: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:885: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:888: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:889: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:892: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:893: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:896: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:897: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:900: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:901: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:904: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:905: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:908: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:909: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:912: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:913: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:916: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:917: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:920: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:921: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:924: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:925: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:928: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:929: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:932: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:933: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:936: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:937: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:940: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:941: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:944: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:945: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:948: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:949: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:952: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:953: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:956: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:957: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:960: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:961: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:964: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:965: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:968: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:969: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:972: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:973: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:976: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:977: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:980: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:981: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:984: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:985: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:988: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:989: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:992: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:993: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:996: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:997: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1000: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1001: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1004: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1005: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1008: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1009: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1012: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1013: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1016: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1017: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1020: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1021: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1024: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1025: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1028: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1029: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1032: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1033: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1036: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1037: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1040: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1041: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1044: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1045: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1048: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1049: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1052: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1053: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1056: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1057: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1060: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1061: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1064: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1065: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1068: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1069: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1072: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1073: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1076: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1077: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1080: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1081: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1084: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1085: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1088: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1089: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1092: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1093: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1096: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1097: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1100: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1101: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1104: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1105: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1108: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1109: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1112: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1113: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1116: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1117: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1120: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1121: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1124: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1125: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1128: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1129: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1132: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1133: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1136: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1137: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1140: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1141: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1144: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1145: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1148: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1149: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1152: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1153: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1156: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1157: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1160: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1161: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1164: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1165: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1168: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1169: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1172: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1176: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1180: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1184: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1188: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1192: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1196: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1200: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1204: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1208: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1212: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1216: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1220: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1224: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1228: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1232: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1236: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1240: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1244: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1248: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1252: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1256: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1260: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1264: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1268: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1272: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1276: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1280: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1284: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1288: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1292: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1296: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1300: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1304: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1308: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1312: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1316: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1320: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1324: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1328: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1332: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1336: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1340: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1344: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1348: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1352: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1356: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1360: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1364: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1368: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1372: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1376: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1380: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1384: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1388: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1392: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1396: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1400: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1404: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1408: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1412: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1416: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1420: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1424: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1428: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1432: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1436: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1440: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1444: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1448: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1452: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1456: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1460: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1464: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1468: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1472: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1476: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1480: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1484: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1488: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1492: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1496: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1500: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1504: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1508: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1512: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1516: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1520: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1524: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1528: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types@2018-06-01.yang:1532: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types@2018-06-01.yang:1533: error: identity "alarm-identity" not found in module "ietf-alarms" |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/fujitsu-alarm-types@2018-06-01.yang 2>&1": libyang err : Unable to find base (al:alarm-identity) of identity "equipmentFault". (Path "/fujitsu-alarm-types:{identity='equipmentFault'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-alarm-types@2018-06-01.yang 2>&1": Error: 'fujitsu-alarm-types@2018-06-01.yang' import of module 'ietf-alarms' failed fujitsu-alarm-types@2018-06-01.yang:5.3: error(236): module not found Warning: revision with same date on line 54 fujitsu-alarm-types@2018-06-01.yang:58.3: warning(1054): Revision date has already been used Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:168.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:172.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:176.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:180.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:184.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:188.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:192.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:196.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:200.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:204.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:208.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:212.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:216.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:220.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:224.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:228.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:232.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:236.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:240.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:244.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:248.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:252.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:256.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:260.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:264.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:268.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:272.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:276.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:280.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:284.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:288.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:292.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:296.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:300.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:304.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:308.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:312.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:316.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:320.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:324.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:328.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:332.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:336.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:340.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:344.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:348.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:352.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:356.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:360.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:364.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:368.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:372.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:376.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:380.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:384.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:388.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:392.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:396.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:400.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:404.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:408.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:412.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:416.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:420.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:424.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:428.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:432.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:436.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:440.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:444.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:448.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:452.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:456.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:460.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:464.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:468.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:472.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:476.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:480.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:484.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:488.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:492.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:496.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:500.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:504.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:508.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:512.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:516.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:520.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:524.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:528.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:532.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:536.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:540.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:544.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:548.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:552.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:556.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:560.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:564.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:568.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:572.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:576.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:580.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:584.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:588.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:592.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:596.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:600.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:604.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:608.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:612.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:616.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:620.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:624.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:628.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:632.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:636.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:640.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:644.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:648.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:652.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:656.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:660.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:664.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:668.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:672.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:676.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:680.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:684.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:688.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:692.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:696.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:700.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:704.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:708.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:712.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:716.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:720.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:724.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:728.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:732.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:736.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:740.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:744.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:748.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:752.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:756.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:760.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:764.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:768.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:772.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:776.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:780.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:784.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:788.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:792.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:796.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:800.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:804.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:808.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:812.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:816.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:820.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:824.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:828.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:832.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:836.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:840.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:844.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:848.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:852.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:856.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:860.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:864.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:868.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:872.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:876.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:880.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:884.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:888.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:892.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:896.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:900.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:904.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:908.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:912.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:916.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:920.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:924.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:928.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:932.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:936.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:940.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:944.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:948.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:952.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:956.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:960.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:964.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:968.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:972.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:976.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:980.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:984.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:988.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:992.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:996.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1000.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1004.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1008.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1012.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1016.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1020.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1024.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1028.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1032.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1036.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1040.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1044.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1048.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1052.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1056.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1060.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1064.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1068.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1072.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1076.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1080.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1084.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1088.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1092.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1096.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1100.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1104.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1108.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1112.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1116.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1120.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1124.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1128.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1132.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1136.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1140.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1144.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1148.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1152.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1156.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1160.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1164.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1168.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1172.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1176.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1180.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1184.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1188.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1192.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1196.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1200.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1204.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1208.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1212.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1216.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1220.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1224.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1228.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1232.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1236.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1240.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1244.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1248.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1252.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1256.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1260.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1264.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1268.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1272.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1276.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1280.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1284.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1288.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1292.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1296.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1300.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1304.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1308.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1312.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1316.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1320.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1324.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1328.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1332.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1336.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1340.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1344.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1348.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1352.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1356.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1360.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1364.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1368.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1372.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1376.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1380.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1384.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1388.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1392.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1396.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1400.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1404.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1408.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1412.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1416.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1420.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1424.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1428.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1432.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1436.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1440.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1444.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1448.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1452.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1456.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1460.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1464.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1468.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1472.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1476.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1480.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1484.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1488.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1492.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1496.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1500.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1504.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1508.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1512.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1516.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1520.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1524.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1528.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types@2018-06-01.yang:1532.3: error(236): module not found |
| fujitsu-alarms-ext@2017-04-21.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-alarms-ext@2017-04-21.yang --lint 2>&1": fujitsu-alarms-ext@2017-04-21.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarms-ext@2017-04-21.yang:45: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:48: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:51: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:57: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:66: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:103: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext@2017-04-21.yang:116: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext@2017-04-21.yang:120: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:142: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-alarms-ext@2017-04-21.yang:191: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext@2017-04-21.yang:204: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext@2017-04-21.yang:263: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-alarms-ext@2017-04-21.yang 2>&1": Error: 'fujitsu-alarms-ext@2017-04-21.yang' import of module 'ietf-alarms' failed fujitsu-alarms-ext@2017-04-21.yang:5.3: error(236): module not found Error: typedef definition for 'al:alarm-type-id' not found in module ietf-alarms fujitsu-alarms-ext@2017-04-21.yang:73.12: error(250): definition not found Error: typedef definition for 'al:alarm-type-id' not found in module ietf-alarms fujitsu-alarms-ext@2017-04-21.yang:161.14: error(250): definition not found Error: typedef definition for 'al:alarm-type-id' not found in module ietf-alarms fujitsu-alarms-ext@2017-04-21.yang:218.14: error(250): definition not found Error: object 'alarms' not found in module fujitsu-alarms-ext in Xpath target /al:alarms fujitsu-alarms-ext@2017-04-21.yang:142.3: error(250): definition not found Error: object 'alarm-notification' not found in module fujitsu-alarms-ext in Xpath target /al:alarm-notification fujitsu-alarms-ext@2017-04-21.yang:263.3: error(250): definition not found Error: object 'alarms' not found in module fujitsu-alarms-ext in Xpath target /al:alarms/al:alarm-list/al:alarm fujitsu-alarms-ext@2017-04-21.yang:120.3: error(250): definition not found Error: object 'alarm-type-id' not found in module fujitsu-alarms-ext in Xpath target alarm-type-id fujitsu-alarms-ext@2017-04-21.yang:144.7: error(250): definition not found Error: invalid identifier in key for list 'alarm-severity-assignment' (alarm-type-id) fujitsu-alarms-ext@2017-04-21.yang:144.7: error(250): definition not found Error: object 'alarm-type-id' not found in module fujitsu-alarms-ext in Xpath target alarm-type-id fujitsu-alarms-ext@2017-04-21.yang:151.7: error(250): definition not found Error: invalid identifier in key for list 'alarm-severity-status' (alarm-type-id) fujitsu-alarms-ext@2017-04-21.yang:151.7: error(250): definition not found Error: object 'alarm-type-id' not found in module fujitsu-alarms-ext in Xpath target alarm-type-id fujitsu-alarms-ext@2017-04-21.yang:208.7: error(250): definition not found Error: invalid identifier in key for list 'severity-defaults' (alarm-type-id) fujitsu-alarms-ext@2017-04-21.yang:208.7: error(250): definition not found |
|||
| fujitsu-database@2017-11-13.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-database@2017-11-13.yang --lint 2>&1": fujitsu-database@2017-11-13.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-database@2017-11-13.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-database@2017-11-13.yang:54: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement |
||||
| fujitsu-dhcp-client@2018-01-22.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-dhcp-client@2018-01-22.yang 2>&1": ./fujitsu-license@2015-08-02.yang:32: warning: the revision statements are not given in reverse chronological order ./tailf-aaa@2023-03-06.yang:103: error: unexpected keyword 'tailf:internal-dp' |
fujitsu-dhcp-client@2018-01-22.yang:18: warning: imported module "fujitsu-system" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-system@2019-02-07.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system@2019-02-07.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system@2019-02-07.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system@2019-02-07.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security@2018-07-18.yang:9: warning: imported module "tailf-aaa" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-dhcp-client@2018-01-22.yang --lint 2>&1": fujitsu-dhcp-client@2018-01-22.yang:6: warning: imported module "ietf-inet-types" not used fujitsu-dhcp-client@2018-01-22.yang:12: warning: imported module "ietf-interfaces" not used fujitsu-dhcp-client@2018-01-22.yang:15: warning: imported module "ietf-ip" not used fujitsu-dhcp-client@2018-01-22.yang:18: warning: imported module "fujitsu-system" not used fujitsu-dhcp-client@2018-01-22.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client@2018-01-22.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client@2018-01-22.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client@2018-01-22.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client@2018-01-22.yang:56: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcp-client@2018-01-22.yang:57: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-dhcp-client@2018-01-22.yang:58: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-dhcp-client@2018-01-22.yang:63: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:64: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:68: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:69: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:73: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:74: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:85: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcp-client@2018-01-22.yang:99: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:100: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:106: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:107: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:108: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client@2018-01-22.yang:109: error: keyword "must" not in canonical order (see RFC 6020, Section 12) |
libyang warn: File name "fujitsu-license@2015-08-02.yang" does not match module revision "2017-06-13". | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-dhcp-client@2018-01-22.yang 2>&1": Error: 'fujitsu-dhcp-client@2018-01-22.yang' import of module 'dhcp-client' failed fujitsu-dhcp-client@2018-01-22.yang:9.3: error(236): module not found Error: 'fujitsu-dhcp-client@2018-01-22.yang' import of module 'fujitsu-system' failed fujitsu-dhcp-client@2018-01-22.yang:18.3: error(236): module not found Error: object 'clientv4' not found in module fujitsu-dhcp-client in Xpath target /dhcp:clientv4 fujitsu-dhcp-client@2018-01-22.yang:56.3: error(250): definition not found Error: object 'clientv4' not found in module fujitsu-dhcp-client in Xpath target /dhcp:clientv4 fujitsu-dhcp-client@2018-01-22.yang:85.3: error(250): definition not found Warning: Module 'fujitsu-system' not used fujitsu-dhcp-client@2018-01-22.yang:18.3: warning(1015): import not used |
| fujitsu-dhcpv6-client@2018-01-22.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-dhcpv6-client@2018-01-22.yang 2>&1": ./fujitsu-license@2015-08-02.yang:32: warning: the revision statements are not given in reverse chronological order ./tailf-aaa@2023-03-06.yang:103: error: unexpected keyword 'tailf:internal-dp' |
fujitsu-dhcpv6-client@2018-01-22.yang:18: warning: imported module "fujitsu-system" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-system@2019-02-07.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system@2019-02-07.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system@2019-02-07.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system@2019-02-07.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security@2018-07-18.yang:9: warning: imported module "tailf-aaa" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-dhcpv6-client@2018-01-22.yang --lint 2>&1": fujitsu-dhcpv6-client@2018-01-22.yang:12: warning: imported module "ietf-interfaces" not used fujitsu-dhcpv6-client@2018-01-22.yang:15: warning: imported module "ietf-ip" not used fujitsu-dhcpv6-client@2018-01-22.yang:18: warning: imported module "fujitsu-system" not used fujitsu-dhcpv6-client@2018-01-22.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client@2018-01-22.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client@2018-01-22.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client@2018-01-22.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client@2018-01-22.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client@2018-01-22.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcpv6-client@2018-01-22.yang:61: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-dhcpv6-client@2018-01-22.yang:62: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-dhcpv6-client@2018-01-22.yang:129: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcpv6-client@2018-01-22.yang:154: error: keyword "must" not in canonical order (see RFC 6020, Section 12) |
libyang warn: File name "fujitsu-license@2015-08-02.yang" does not match module revision "2017-06-13". | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-dhcpv6-client@2018-01-22.yang 2>&1": Error: 'fujitsu-dhcpv6-client@2018-01-22.yang' import of module 'dhcpv6-client' failed fujitsu-dhcpv6-client@2018-01-22.yang:9.3: error(236): module not found Error: 'fujitsu-dhcpv6-client@2018-01-22.yang' import of module 'fujitsu-system' failed fujitsu-dhcpv6-client@2018-01-22.yang:18.3: error(236): module not found Error: object 'clientv6' not found in module fujitsu-dhcpv6-client in Xpath target /dhcpv6:clientv6 fujitsu-dhcpv6-client@2018-01-22.yang:60.3: error(250): definition not found Error: object 'clientv6' not found in module fujitsu-dhcpv6-client in Xpath target /dhcpv6:clientv6 fujitsu-dhcpv6-client@2018-01-22.yang:129.3: error(250): definition not found Warning: Module 'fujitsu-system' not used fujitsu-dhcpv6-client@2018-01-22.yang:18.3: warning(1015): import not used |
| fujitsu-entity-maintenance-loopback@2015-09-10.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-entity-maintenance-loopback@2015-09-10.yang --lint 2>&1": fujitsu-entity-maintenance-loopback@2015-09-10.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-loopback@2015-09-10.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement |
||||
| fujitsu-entity-maintenance-testsignal@2015-09-10.yang | FAILED | fujitsu-entity-maintenance-testsignal@2015-09-10.yang:0: warning: expected revision '2015-09-10', got '2018-06-21' fujitsu-entity-maintenance-testsignal@2015-09-10.yang:26: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal@2015-09-10.yang:30: warning: the revision statements are not given in reverse chronological order |
fujitsu-entity-maintenance-testsignal@2015-09-10.yang:1: warning: unexpected latest revision "2018-06-21" in fujitsu-entity-maintenance-testsignal@2015-09-10.yang, should be "2015-09-10" fujitsu-entity-maintenance-testsignal@2015-09-10.yang:26: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal@2015-09-10.yang:30: warning: the revision statements are not given in reverse chronological order |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-entity-maintenance-testsignal@2015-09-10.yang --lint 2>&1": fujitsu-entity-maintenance-testsignal@2015-09-10.yang:1: warning: unexpected latest revision "2018-06-21" in fujitsu-entity-maintenance-testsignal@2015-09-10.yang, should be "2015-09-10" fujitsu-entity-maintenance-testsignal@2015-09-10.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-testsignal@2015-09-10.yang:26: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal@2015-09-10.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-testsignal@2015-09-10.yang:30: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal@2015-09-10.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-testsignal@2015-09-10.yang:35: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement |
libyang warn: File name "fujitsu-entity-maintenance-testsignal@2015-09-10.yang" does not match module revision "2018-06-21". | Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal@2015-09-10.yang:26.3: warning(1035): bad revision-stmt order Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal@2015-09-10.yang:30.3: warning(1035): bad revision-stmt order |
| fujitsu-entity-states@2017-03-02.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-entity-states@2017-03-02.yang --lint 2>&1": fujitsu-entity-states@2017-03-02.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-states@2017-03-02.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-states@2017-03-02.yang:38: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-entity-states@2017-03-02.yang:80: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-entity-states@2017-03-02.yang:101: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-entity-states@2017-03-02.yang:111: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-entity-states@2017-03-02.yang:121: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-entity-states@2017-03-02.yang:128: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-entity-states@2017-03-02.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-entity-states@2017-03-02.yang 2>&1": Error: 'fujitsu-entity-states@2017-03-02.yang' import of module 'fujitsu-notifications' failed fujitsu-entity-states@2017-03-02.yang:5.3: error(236): module not found Error: 'fujitsu-entity-states@2017-03-02.yang' import of module 'fujitsu-notification-types' failed fujitsu-entity-states@2017-03-02.yang:8.3: error(236): module not found Error: Module for prefix 'notifications' not found fujitsu-entity-states@2017-03-02.yang:124.10: error(236): module not found Error: object 'event-notification' not found in module fujitsu-entity-states in Xpath target /notifications:event-notification fujitsu-entity-states@2017-03-02.yang:121.3: error(250): definition not found Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states@2017-03-02.yang:8.3: warning(1015): import not used |
|||
| fujitsu-eqpt-operations-dev@2017-02-28.yang | FAILED | fujitsu-eqpt-operations-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-eqpt-operations-dev.prod.yang --lint 2>&1": fujitsu-eqpt-operations-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-eqpt-operations-dev.prod.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-eqpt-operations-dev.prod.yang 2>&1": Error: 'fujitsu-eqpt-operations-dev.prod.yang' import of module 'tailf-common' failed fujitsu-eqpt-operations-dev.prod.yang:5.5: error(236): module not found Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:40.5: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:13.3: warning(1015): import not used Warning: Module 'tailf-common' not used fujitsu-eqpt-operations-dev.prod.yang:5.5: warning(1015): import not used |
||
| fujitsu-eqpt-operations@2015-09-28.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-eqpt-operations@2015-09-28.yang --lint 2>&1": fujitsu-eqpt-operations@2015-09-28.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations@2015-09-28.yang:31: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-eqpt-operations@2015-09-28.yang:42: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-eqpt-operations@2015-09-28.yang:74: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-eqpt-operations@2015-09-28.yang:102: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-eqpt-operations@2015-09-28.yang:130: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations@2015-09-28.yang:148: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations@2015-09-28.yang:166: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations@2015-09-28.yang:178: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-eqpt-operations@2015-09-28.yang 2>&1": Error: 'fujitsu-eqpt-operations@2015-09-28.yang' import of module 'fujitsu-equipment' failed fujitsu-eqpt-operations@2015-09-28.yang:5.3: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-eqpt-operations@2015-09-28.yang:45.15: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-eqpt-operations@2015-09-28.yang:53.15: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-eqpt-operations@2015-09-28.yang:60.15: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-eqpt-operations@2015-09-28.yang:67.15: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-eqpt-operations@2015-09-28.yang:34.15: error(236): module not found |
||
| fujitsu-equipment-dev@2018-12-11.yang | FAILED | fujitsu-equipment-dev.prod.yang:92: warning: the revision statements are not given in reverse chronological order | fujitsu-equipment-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-equipment-dev.prod.yang:14: warning: imported module "fujitsu-pm-types" not used fujitsu-equipment-dev.prod.yang:92: warning: the revision statements are not given in reverse chronological order fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-equipment-dev.prod.yang --lint 2>&1": fujitsu-equipment-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-equipment-dev.prod.yang:14: warning: imported module "fujitsu-pm-types" not used fujitsu-equipment-dev.prod.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:72: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:82: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:87: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:92: warning: the revision statements are not given in reverse chronological order fujitsu-equipment-dev.prod.yang:92: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
libyang warn: Invalid value "binned" which does not fit the type (Invalid enumeration value "binned".). libyang warn: Previous warning generated by XPath subexpression[3] "pm-type = 'binned'" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/subport/pm/pm-threshold/pm-th-binned". libyang warn: Previous warning generated by XPath subexpression[3] "pm-type = 'binned'" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/pm/pm-threshold/pm-th-binned". |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment-dev.prod.yang 2>&1": Error: 'fujitsu-equipment-dev.prod.yang' import of module 'tailf-common' failed fujitsu-equipment-dev.prod.yang:5.5: error(236): module not found Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:40.5: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:13.3: warning(1015): import not used Warning: Module 'tailf-common' not used fujitsu-equipment-dev.prod.yang:5.5: warning(1015): import not used Warning: Module 'fujitsu-pm-types' not used fujitsu-equipment-dev.prod.yang:14.5: warning(1015): import not used |
| fujitsu-equipment@2017-07-10.yang | FAILED | fujitsu-equipment@2017-07-10.yang:11: warning: imported module "fujitsu-notification-types" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-equipment@2017-07-10.yang --lint 2>&1": fujitsu-equipment@2017-07-10.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-equipment@2017-07-10.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment@2017-07-10.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment@2017-07-10.yang:48: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-equipment@2017-07-10.yang:53: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-equipment@2017-07-10.yang 2>&1": Error: 'fujitsu-equipment@2017-07-10.yang' import of module 'fujitsu-shelf' failed fujitsu-equipment@2017-07-10.yang:5.3: error(236): module not found Error: 'fujitsu-equipment@2017-07-10.yang' import of module 'fujitsu-notifications' failed fujitsu-equipment@2017-07-10.yang:8.3: error(236): module not found Error: 'fujitsu-equipment@2017-07-10.yang' import of module 'fujitsu-notification-types' failed fujitsu-equipment@2017-07-10.yang:11.3: error(236): module not found Error: 'fujitsu-equipment@2017-07-10.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-equipment@2017-07-10.yang:14.3: error(236): module not found Error: grouping definition for 'shelf:Shelf' not found in module fujitsu-shelf fujitsu-equipment@2017-07-10.yang:50.7: error(250): definition not found Error: grouping definition for 'pi:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-equipment@2017-07-10.yang:57.7: error(250): definition not found Error: grouping 'Shelf' not found fujitsu-equipment@2017-07-10.yang:50.7: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-equipment@2017-07-10.yang:57.7: error(250): definition not found Error: object 'event-notification' not found in module fujitsu-equipment in Xpath target /notifications:event-notification fujitsu-equipment@2017-07-10.yang:53.3: error(250): definition not found Error: object 'shelfId' not found in module fujitsu-equipment in Xpath target shelfId fujitsu-equipment@2017-07-10.yang:49.7: error(250): definition not found Error: invalid identifier in key for list 'shelf' (shelfId) fujitsu-equipment@2017-07-10.yang:49.7: error(250): definition not found Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment@2017-07-10.yang:11.3: warning(1015): import not used |
||
| fujitsu-ethernet-interfaces-common@2018-06-07.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ethernet-interfaces-common@2018-06-07.yang --lint 2>&1": fujitsu-ethernet-interfaces-common@2018-06-07.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-common@2018-06-07.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-common@2018-06-07.yang:46: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ethernet-interfaces-common@2018-06-07.yang:50: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces-common@2018-06-07.yang:63: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces-common@2018-06-07.yang:64: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces-common@2018-06-07.yang:65: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-ethernet-interfaces-common@2018-06-07.yang 2>&1": Error: 'fujitsu-ethernet-interfaces-common@2018-06-07.yang' import of module 'fujitsu-entity-states' failed fujitsu-ethernet-interfaces-common@2018-06-07.yang:6.3: error(236): module not found Error: 'fujitsu-ethernet-interfaces-common@2018-06-07.yang' import of module 'fujitsu-entity-maintenance-loopback' failed fujitsu-ethernet-interfaces-common@2018-06-07.yang:9.3: error(236): module not found Error: 'fujitsu-ethernet-interfaces-common@2018-06-07.yang' import of module 'fujitsu-entity-maintenance-testsignal' failed fujitsu-ethernet-interfaces-common@2018-06-07.yang:12.3: error(236): module not found Error: 'fujitsu-ethernet-interfaces-common@2018-06-07.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-ethernet-interfaces-common@2018-06-07.yang:15.3: error(236): module not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-ethernet-interfaces-common@2018-06-07.yang:47.5: error(250): definition not found Error: grouping definition for 'fujitsu-loopback:maint-loopback' not found in module fujitsu-entity-maintenance-loopback fujitsu-ethernet-interfaces-common@2018-06-07.yang:78.5: error(250): definition not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-ethernet-interfaces-common@2018-06-07.yang:79.5: error(250): definition not found Error: grouping definition for 'fujitsu-testsignal:maint-testsignal' not found in module fujitsu-entity-maintenance-testsignal fujitsu-ethernet-interfaces-common@2018-06-07.yang:84.5: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-ethernet-interfaces-common@2018-06-07.yang:98.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-ethernet-interfaces-common@2018-06-07.yang:47.5: error(250): definition not found Error: grouping 'maint-loopback' not found fujitsu-ethernet-interfaces-common@2018-06-07.yang:78.5: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-ethernet-interfaces-common@2018-06-07.yang:79.5: error(250): definition not found Error: grouping 'maint-testsignal' not found fujitsu-ethernet-interfaces-common@2018-06-07.yang:84.5: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-ethernet-interfaces-common@2018-06-07.yang:98.5: error(250): definition not found |
|||
| fujitsu-ethernet-interfaces-dev@2019-01-16.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ethernet-interfaces-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:30: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:36: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:38: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:41: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security.yang:12: error: module 'tailf-aaa' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security.yang:308: error: the node 'user' from module 'tailf-aaa' is not found |
fujitsu-ethernet-interfaces-dev.prod.yang:13: warning: imported module "fujitsu-equipment" not used fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:9: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:21: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:25: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:41: warning: imported module "fujitsu-license" not used fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security.yang:12: warning: imported module "tailf-aaa" not used fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ethernet-interfaces-dev.prod.yang --lint 2>&1": fujitsu-ethernet-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-ethernet-interfaces-dev.prod.yang:13: warning: imported module "fujitsu-equipment" not used fujitsu-ethernet-interfaces-dev.prod.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:61: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces-dev.prod.yang:66: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces-dev.prod.yang:71: error: keyword "description" not in canonical order (see RFC 6020, Section 12) |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ethernet-interfaces-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\^'. (Line number 157.) libyang err : Parsing module "fujitsu-user-security-typedefs" failed. libyang err : Loading "fujitsu-user-security-typedefs" module failed. libyang err : Parsing module "fujitsu-user-security" failed. libyang err : Loading "fujitsu-user-security" module failed. libyang err : Parsing module "fujitsu-security-certificates" failed. libyang err : Loading "fujitsu-security-certificates" module failed. libyang err : Parsing module "fujitsu-system" failed. libyang err : Loading "fujitsu-system" module failed. libyang err : Parsing module "fujitsu-ethernet-interfaces" failed. libyang err : Loading "fujitsu-ethernet-interfaces" module failed. libyang err : Parsing module "fujitsu-ethernet-interfaces-dev.prod" failed. |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ethernet-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:28.5: warning(1035): bad revision-stmt order Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:32.5: warning(1035): bad revision-stmt order Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-ethernet-interfaces.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-ethernet-interfaces.yang:17.5: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-common' failed fujitsu-system.yang:5.3: error(236): module not found Warning: revision with same date on line 34 fujitsu-port.yang:40.5: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:13.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-common' failed fujitsu-user-security.yang:9.3: error(236): module not found Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:12.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:259.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:260.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:261.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:267.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:269.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:273.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:275.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:285.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:287.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:291.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:293.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:308.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:320.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:321.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:322.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:323.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:337.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:338.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:344.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:345.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:357.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:358.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:359.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:362.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:373.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:374.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:380.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:386.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:387.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:389.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:393.11: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:96.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:12.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:4.3: error(236): module not found Warning: no revision statements for module 'fujitsu-security-certificates' Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:7.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:53.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:28.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:31.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:35.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-system.yang:38.3: error(332): imported module has errors Warning: revision dates not in descending order fujitsu-license.yang:38.6: warning(1035): bad revision-stmt order Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-system.yang:862.4: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1628.17: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1768.16: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:663.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:684.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:741.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:804.10: error(236): module not found Error: grouping 'ains-prov-keywords' not found fujitsu-system.yang:862.4: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:866.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:867.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:868.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:915.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1481.14: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1482.14: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1732.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1733.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1734.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1735.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1736.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1737.12: error(236): module not found Warning: top-level NP container 'system' is mandatory fujitsu-system.yang:874.3: warning(1048): top-level object is mandatory Error: Module for prefix 'secu' not found fujitsu-system.yang:1661.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:9.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:21.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:25.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:41.3: warning(1015): import not used Error: 'fujitsu-ethernet-interfaces.yang' import of module 'fujitsu-system' failed fujitsu-ethernet-interfaces.yang:21.5: error(236): module not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-ethernet-interfaces.yang:649.15: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-ethernet-interfaces.yang:649.15: error(250): definition not found Error: object 'defaults' not found in module fujitsu-ethernet-interfaces in Xpath target /sys:defaults fujitsu-ethernet-interfaces.yang:655.5: error(250): definition not found Error: 'fujitsu-ethernet-interfaces-dev.prod.yang' import of module 'fujitsu-ethernet-interfaces' failed fujitsu-ethernet-interfaces-dev.prod.yang:9.5: error(250): definition not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:actual-vstimer' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:link-oam' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:policy-profile' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:fec' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:rate' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:location' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:testPattern' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:transport-signal-failure' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:backward-transport-signal-failure' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:direction' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:tx-clock-source' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-type' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-th-metered' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-th-binned/eth:pm-time-periods/eth:pm-time-period' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-th-binned/eth:pm-time-periods/eth:pm-value' fujitsu-ethernet-interfaces-dev.prod.yang:238.5: error(251): definition segment not found Warning: Module 'fujitsu-equipment' not used fujitsu-ethernet-interfaces-dev.prod.yang:13.5: warning(1015): import not used |
| fujitsu-ethernet-interfaces@2018-10-26.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-ethernet-interfaces@2018-10-26.yang 2>&1": ./fujitsu-license@2015-08-02.yang:32: warning: the revision statements are not given in reverse chronological order ./tailf-aaa@2023-03-06.yang:103: error: unexpected keyword 'tailf:internal-dp' |
/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-system@2019-02-07.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system@2019-02-07.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system@2019-02-07.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system@2019-02-07.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security@2018-07-18.yang:9: warning: imported module "tailf-aaa" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ethernet-interfaces@2018-10-26.yang --lint 2>&1": fujitsu-ethernet-interfaces@2018-10-26.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:84: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:100: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:101: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:114: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:180: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces@2018-10-26.yang:317: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:341: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:344: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:368: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:373: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:376: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:379: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:382: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:385: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:388: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:442: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ethernet-interfaces@2018-10-26.yang:443: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces@2018-10-26.yang:626: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:645: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:653: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:664: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement |
libyang warn: File name "fujitsu-license@2015-08-02.yang" does not match module revision "2017-06-13". | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-ethernet-interfaces@2018-10-26.yang 2>&1": Error: 'fujitsu-ethernet-interfaces@2018-10-26.yang' import of module 'fujitsu-ethernet-interfaces-common' failed fujitsu-ethernet-interfaces@2018-10-26.yang:9.3: error(236): module not found Error: 'fujitsu-ethernet-interfaces@2018-10-26.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-ethernet-interfaces@2018-10-26.yang:13.3: error(236): module not found Error: 'fujitsu-ethernet-interfaces@2018-10-26.yang' import of module 'fujitsu-system' failed fujitsu-ethernet-interfaces@2018-10-26.yang:16.3: error(236): module not found Error: grouping definition for 'eth-common:common-eth-attributes' not found in module fujitsu-ethernet-interfaces-common fujitsu-ethernet-interfaces@2018-10-26.yang:650.7: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-ethernet-interfaces@2018-10-26.yang:660.9: error(250): definition not found Error: grouping 'common-eth-attributes' not found fujitsu-ethernet-interfaces@2018-10-26.yang:650.7: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-ethernet-interfaces@2018-10-26.yang:660.9: error(250): definition not found Error: object 'defaults' not found in module fujitsu-ethernet-interfaces in Xpath target /sys:defaults fujitsu-ethernet-interfaces@2018-10-26.yang:664.3: error(250): definition not found |
| fujitsu-factory@2015-10-13.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-factory@2015-10-13.yang --lint 2>&1": fujitsu-factory@2015-10-13.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
||||
| fujitsu-file-transfer-webui@2017-06-26.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-file-transfer-webui@2017-06-26.yang --lint 2>&1": fujitsu-file-transfer-webui@2017-06-26.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer-webui@2017-06-26.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer-webui@2017-06-26.yang:44: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-file-transfer-webui@2017-06-26.yang:48: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer-webui@2017-06-26.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer-webui@2017-06-26.yang:53: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer-webui@2017-06-26.yang:54: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer-webui@2017-06-26.yang:58: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer-webui@2017-06-26.yang:61: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
||||
| fujitsu-file-transfer@2017-06-26.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-file-transfer@2017-06-26.yang --lint 2>&1": fujitsu-file-transfer@2017-06-26.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer@2017-06-26.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer@2017-06-26.yang:53: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-file-transfer@2017-06-26.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-file-transfer@2017-06-26.yang:65: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-file-transfer@2017-06-26.yang:69: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer@2017-06-26.yang:70: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer@2017-06-26.yang:74: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer@2017-06-26.yang:75: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer@2017-06-26.yang:79: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer@2017-06-26.yang:82: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
||||
| fujitsu-fwdl@2015-09-28.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-fwdl@2015-09-28.yang --lint 2>&1": fujitsu-fwdl@2015-09-28.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-fwdl@2015-09-28.yang:31: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-fwdl@2015-09-28.yang:86: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-fwdl@2015-09-28.yang:204: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-fwdl@2015-09-28.yang:216: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-fwdl@2015-09-28.yang:234: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-fwdl@2015-09-28.yang 2>&1": Error: 'fujitsu-fwdl@2015-09-28.yang' import of module 'fujitsu-equipment' failed fujitsu-fwdl@2015-09-28.yang:5.3: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-fwdl@2015-09-28.yang:34.15: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-fwdl@2015-09-28.yang:42.15: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-fwdl@2015-09-28.yang:49.15: error(236): module not found |
||
| fujitsu-gcc@2015-09-14.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-gcc@2015-09-14.yang --lint 2>&1": fujitsu-gcc@2015-09-14.yang:72: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement |
||||
| fujitsu-if-type@2019-03-08.yang | FAILED | fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-if-type.yang --lint 2>&1": fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used fujitsu-if-type.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-if-type.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-if-type.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Warning: Module 'ietf-interfaces' not used fujitsu-if-type.yang:5.3: warning(1015): import not used |
||
| fujitsu-inventory@2014-12-02.yang | FAILED | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-inventory@2014-12-02.yang 2>&1": Error: 'fujitsu-inventory@2014-12-02.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-inventory@2014-12-02.yang:5.3: error(236): module not found Error: grouping definition for 'physical-inventory:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-inventory@2014-12-02.yang:41.5: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-inventory@2014-12-02.yang:41.5: error(250): definition not found |
||||
| fujitsu-ip@2018-04-17.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ip@2018-04-17.yang --lint 2>&1": fujitsu-ip@2018-04-17.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip@2018-04-17.yang:66: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip@2018-04-17.yang:76: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip@2018-04-17.yang:79: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ip@2018-04-17.yang:82: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ip@2018-04-17.yang:87: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-ip@2018-04-17.yang:94: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip@2018-04-17.yang:95: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ip@2018-04-17.yang:101: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip@2018-04-17.yang:102: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ip@2018-04-17.yang:104: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ip@2018-04-17.yang:107: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
||||
| fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang 2>&1": fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'routing-instance' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'routing-protocols' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'routing-protocol' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'static-routes' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'ipv4' in module 'ietf-ipv4-unicast-routing' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'route' in module 'ietf-ipv4-unicast-routing' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'next-hop' in module 'ietf-ipv4-unicast-routing' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node 'next-hop-options' in module 'ietf-ipv4-unicast-routing' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:65: error: the node 'routing-instance' from module 'ietf-routing' (in node 'routing' from 'ietf-routing') is not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'routing-instance' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'ribs' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'rib' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'routes' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'route' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'next-hop' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'next-hop-options' not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node 'simple-next-hop' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang 2>&1": fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:11: warning: imported module "ietf-interfaces" not used fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:17: warning: imported module "ietf-yang-types" not used fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node ietf-routing::routing-instance is not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:65: error: "ietf-routing:routing-instance" in the path for onlink-outgoing-intf at fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:62 is not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang --lint 2>&1": fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:11: warning: imported module "ietf-interfaces" not used fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:17: warning: imported module "ietf-yang-types" not used fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60: error: node ietf-routing::routing-instance is not found fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:63: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:64: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:71: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:72: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78: error: node ietf-routing::routing-instance is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route/v4ur:next-hop/v4ur:next-hop-options" from module "fujitsu-ipv4-unicast-routing-ext" was not found. (Path "/fujitsu-ipv4-unicast-routing-ext:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route/v4ur:next-hop/v4ur:next-hop-options'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop" from module "fujitsu-ipv4-unicast-routing-ext" was not found. (Path "/fujitsu-ipv4-unicast-routing-ext:{augment='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route/v4ur:next-hop/v4ur:next-hop-options' fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:60.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop' fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:78.3: error(251): definition segment not found Warning: Module 'ietf-ipv4-unicast-routing' not used fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:8.3: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:11.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-ipv4-unicast-routing-ext@2018-01-22.yang:17.3: warning(1015): import not used |
| fujitsu-ipv6-unicast-routing@2018-01-22.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-ipv6-unicast-routing@2018-01-22.yang 2>&1": fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'routing-instance' not found fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'ribs' not found fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'rib' not found fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'routes' not found fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'route' not found fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'next-hop' not found fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'next-hop-options' not found fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node 'simple-next-hop' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ipv6-unicast-routing@2018-01-22.yang 2>&1": fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ipv6-unicast-routing@2018-01-22.yang --lint 2>&1": fujitsu-ipv6-unicast-routing@2018-01-22.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv6-unicast-routing@2018-01-22.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ipv6-unicast-routing@2018-01-22.yang:42: error: node ietf-routing::routing-instance is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/fujitsu-ipv6-unicast-routing@2018-01-22.yang 2>&1": libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop" from module "fujitsu-ipv6-unicast-routing" was not found. (Path "/fujitsu-ipv6-unicast-routing:{augment='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-ipv6-unicast-routing@2018-01-22.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop' fujitsu-ipv6-unicast-routing@2018-01-22.yang:42.3: error(251): definition segment not found Warning: Module 'ietf-ipv6-unicast-routing' not used fujitsu-ipv6-unicast-routing@2018-01-22.yang:8.3: warning(1015): import not used |
| fujitsu-license@2015-08-02.yang | FAILED | fujitsu-license@2015-08-02.yang:0: warning: expected revision '2015-08-02', got '2017-06-13' fujitsu-license@2015-08-02.yang:32: warning: the revision statements are not given in reverse chronological order |
fujitsu-license@2015-08-02.yang:1: warning: unexpected latest revision "2017-06-13" in fujitsu-license@2015-08-02.yang, should be "2015-08-02" fujitsu-license@2015-08-02.yang:32: warning: the revision statements are not given in reverse chronological order |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-license@2015-08-02.yang --lint 2>&1": fujitsu-license@2015-08-02.yang:1: warning: unexpected latest revision "2017-06-13" in fujitsu-license@2015-08-02.yang, should be "2015-08-02" fujitsu-license@2015-08-02.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-license@2015-08-02.yang:38: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-license@2015-08-02.yang:50: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-license@2015-08-02.yang:58: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-license@2015-08-02.yang:59: error: keyword "when" not in canonical order (see RFC 6020, Section 12) fujitsu-license@2015-08-02.yang:60: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-license@2015-08-02.yang:183: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-license@2015-08-02.yang:185: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-license@2015-08-02.yang:317: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
libyang warn: File name "fujitsu-license@2015-08-02.yang" does not match module revision "2017-06-13". | Warning: revision dates not in descending order fujitsu-license@2015-08-02.yang:32.3: warning(1035): bad revision-stmt order |
| fujitsu-lldp-dev@2017-02-15.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-lldp-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-lldp.yang:18: error: module 'iana-afn-safi' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-lldp-dev.prod.yang 2>&1": fujitsu-lldp.yang:6: warning: imported module "ietf-yang-types" not used fujitsu-lldp.yang:155: error: XPath function "re-match" is not defined in the XPath context |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-lldp-dev.prod.yang --lint 2>&1": fujitsu-lldp-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-lldp-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-lldp-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-lldp-dev.prod.yang:13: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-lldp-dev.prod.yang 2>&1": Error: 'fujitsu-protocols.yang' import of module 'tailf-common' failed fujitsu-protocols.yang:9.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-protocols.yang:52.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-protocols.yang:56.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-protocols.yang:60.15: error(236): module not found Error: 'fujitsu-lldp-dev.prod.yang' import of module 'fujitsu-protocols' failed fujitsu-lldp-dev.prod.yang:5.5: error(236): module not found Error: 'fujitsu-lldp.yang' import of module 'iana-afn-safi' failed fujitsu-lldp.yang:18.3: error(236): module not found Error: 'fujitsu-lldp.yang' import of module 'tailf-common' failed fujitsu-lldp.yang:22.3: error(236): module not found Error: 'fujitsu-lldp.yang' import of module 'fujitsu-protocols' failed fujitsu-lldp.yang:26.3: error(236): module not found Error: Module for prefix 'fjproto' not found fujitsu-lldp.yang:86.16: error(236): module not found Error: typedef definition for 'ianaaf:address-family' not found in module iana-afn-safi fujitsu-lldp.yang:224.30: error(250): definition not found Load module 'fujitsu-protocols' failed (imported module has errors) Error: failure importing module 'fujitsu-protocols' fujitsu-lldp.yang:76.3: error(332): imported module has errors Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:131.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:164.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:198.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:211.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:221.15: error(236): module not found Error: object 'protocols' not found in module fujitsu-lldp in Xpath target /fjproto:protocols/fjproto:protocol fujitsu-lldp.yang:82.3: error(250): definition not found Warning: Module 'ietf-yang-types' not used fujitsu-lldp.yang:6.3: warning(1015): import not used Error: 'fujitsu-lldp-dev.prod.yang' import of module 'fujitsu-lldp' failed fujitsu-lldp-dev.prod.yang:9.5: error(250): definition not found Error: object 'protocols' not found in module fujitsu-lldp-dev.prod in Xpath target /fjproto:protocols/fjproto:protocol/lldp:lldp-instance/lldp:port/lldp:adminStatus fujitsu-lldp-dev.prod.yang:34.2: error(250): definition not found Warning: Module 'fujitsu-lldp' not used fujitsu-lldp-dev.prod.yang:9.5: warning(1015): import not used |
|
| fujitsu-lldp@2017-06-01.yang | FAILED | fujitsu-lldp@2017-06-01.yang:6: warning: imported module "ietf-yang-types" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-lldp@2017-06-01.yang --lint 2>&1": fujitsu-lldp@2017-06-01.yang:6: warning: imported module "ietf-yang-types" not used fujitsu-lldp@2017-06-01.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp@2017-06-01.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp@2017-06-01.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp@2017-06-01.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp@2017-06-01.yang:67: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-lldp@2017-06-01.yang:90: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp@2017-06-01.yang:98: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp@2017-06-01.yang:106: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp@2017-06-01.yang:112: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp@2017-06-01.yang:135: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp@2017-06-01.yang:140: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp@2017-06-01.yang:141: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp@2017-06-01.yang:147: error: RFC 8407: 4.14: statement "list" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-lldp@2017-06-01.yang 2>&1": Error: 'fujitsu-lldp@2017-06-01.yang' import of module 'iana-afn-safi' failed fujitsu-lldp@2017-06-01.yang:15.3: error(236): module not found Error: 'fujitsu-lldp@2017-06-01.yang' import of module 'fujitsu-protocols' failed fujitsu-lldp@2017-06-01.yang:18.3: error(236): module not found Error: Module for prefix 'fjproto' not found fujitsu-lldp@2017-06-01.yang:69.16: error(236): module not found Error: typedef definition for 'ianaaf:address-family' not found in module iana-afn-safi fujitsu-lldp@2017-06-01.yang:149.20: error(250): definition not found Load module 'fujitsu-protocols' failed (module not found) Error: failure importing module 'fujitsu-protocols' fujitsu-lldp@2017-06-01.yang:61.3: error(236): module not found Error: object 'protocols' not found in module fujitsu-lldp in Xpath target /fjproto:protocols/fjproto:protocol fujitsu-lldp@2017-06-01.yang:67.3: error(250): definition not found Warning: Module 'ietf-yang-types' not used fujitsu-lldp@2017-06-01.yang:6.3: warning(1015): import not used |
||
| fujitsu-log@2018-09-24.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-log@2018-09-24.yang --lint 2>&1": fujitsu-log@2018-09-24.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:76: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log@2018-09-24.yang:78: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-log@2018-09-24.yang:99: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log@2018-09-24.yang:114: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-log@2018-09-24.yang:158: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log@2018-09-24.yang:206: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-log@2018-09-24.yang:208: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-log@2018-09-24.yang:245: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement fujitsu-log@2018-09-24.yang:263: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log@2018-09-24.yang:271: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-log@2018-09-24.yang:309: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log@2018-09-24.yang:340: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-log@2018-09-24.yang:346: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-log@2018-09-24.yang:349: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-log@2018-09-24.yang 2>&1": Error: 'fujitsu-log@2018-09-24.yang' import of module 'fujitsu-equipment' failed fujitsu-log@2018-09-24.yang:5.3: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-log@2018-09-24.yang:197.17: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-log@2018-09-24.yang:256.17: error(236): module not found Error: Module for prefix 'eqpt' not found fujitsu-log@2018-09-24.yang:322.17: error(236): module not found |
||
| fujitsu-mac-addr@2016-02-01.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-mac-addr@2016-02-01.yang --lint 2>&1": fujitsu-mac-addr@2016-02-01.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-mac-addr@2016-02-01.yang:34: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-mac-addr@2016-02-01.yang:50: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-mac-addr@2016-02-01.yang 2>&1": Error: 'fujitsu-mac-addr@2016-02-01.yang' import of module 'fujitsu-equipment' failed fujitsu-mac-addr@2016-02-01.yang:8.3: error(236): module not found Error: object 'eqpt' not found in module fujitsu-mac-addr in Xpath target /eqpt:eqpt/eqpt:shelf/eqpt:slot fujitsu-mac-addr@2016-02-01.yang:34.3: error(250): definition not found Error: object 'eqpt' not found in module fujitsu-mac-addr in Xpath target /eqpt:eqpt/eqpt:shelf/eqpt:slot/eqpt:subslot fujitsu-mac-addr@2016-02-01.yang:50.3: error(250): definition not found |
||
| fujitsu-nat@2016-04-01.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-nat@2016-04-01.yang --lint 2>&1": fujitsu-nat@2016-04-01.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-nat@2016-04-01.yang:42: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-nat@2016-04-01.yang:70: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat@2016-04-01.yang:86: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-nat@2016-04-01.yang:116: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat@2016-04-01.yang:131: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat@2016-04-01.yang:149: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat@2016-04-01.yang:165: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-nat@2016-04-01.yang:195: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat@2016-04-01.yang:210: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat@2016-04-01.yang:228: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat@2016-04-01.yang:256: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-nat@2016-04-01.yang:293: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat@2016-04-01.yang:312: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat@2016-04-01.yang:331: error: RFC 8407: 4.14: statement "list" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-nat@2016-04-01.yang 2>&1": Error: 'fujitsu-nat@2016-04-01.yang' import of module 'fujitsu-protocols' failed fujitsu-nat@2016-04-01.yang:9.3: error(236): module not found Error: Module for prefix 'fjproto' not found fujitsu-nat@2016-04-01.yang:258.15: error(236): module not found Error: Module for prefix 'fjproto' not found fujitsu-nat@2016-04-01.yang:265.20: error(236): module not found Error: Module for prefix 'fjproto' not found fujitsu-nat@2016-04-01.yang:272.20: error(236): module not found Error: Module for prefix 'fjproto' not found fujitsu-nat@2016-04-01.yang:279.20: error(236): module not found Load module 'fujitsu-protocols' failed (module not found) Error: failure importing module 'fujitsu-protocols' fujitsu-nat@2016-04-01.yang:36.3: error(236): module not found Error: object 'protocols' not found in module fujitsu-nat in Xpath target /fjproto:protocols/fjproto:protocol fujitsu-nat@2016-04-01.yang:256.3: error(250): definition not found |
|||
| fujitsu-net-ospf@2018-01-22.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-net-ospf@2018-01-22.yang 2>&1": ./ietf-ospf@2015-03-09.yang:704: error: grouping 'crypto-algorithm-types' in module 'ietf-key-chain' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-instance' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocols' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocol' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-instance' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocols' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocol' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'ribs' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'rib' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'routes' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'route' not found ./ietf-ospf@2015-03-09.yang:2435: error: typedef 'routing-instance-ref' in module 'ietf-routing' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-net-ospf@2018-01-22.yang 2>&1": fujitsu-net-ospf@2018-01-22.yang:83: error: node ietf-routing::routing-instance is not found fujitsu-net-ospf@2018-01-22.yang:86: warning: node "ietf-ospf::af" is not found in "fujitsu-net-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1970 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2121 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:601: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2151 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1458): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2151 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1467): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2169 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1486): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2169 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1495): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2187 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1514): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2187 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1523): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1946 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1614): warning: node "ietf-routing::routing-instance" is not found in "ietf-routing::routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1868: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1907: error: type "routing-instance-ref" not found in module "ietf-routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2003: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2020: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2018 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2038: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2052: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2050 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2064: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2087: error: type "routing-instance-ref" not found in module "ietf-routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2134: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2193: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2207: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2205 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2224: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2238: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2236 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2292: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2331: error: type "routing-instance-ref" not found in module "ietf-routing" |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-net-ospf@2018-01-22.yang --lint 2>&1": fujitsu-net-ospf@2018-01-22.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-net-ospf@2018-01-22.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-net-ospf@2018-01-22.yang:46: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:52: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:58: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:63: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:70: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:83: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-net-ospf@2018-01-22.yang:83: error: node ietf-routing::routing-instance is not found fujitsu-net-ospf@2018-01-22.yang:86: warning: node "ietf-ospf::af" is not found in "fujitsu-net-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/fujitsu-net-ospf@2018-01-22.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "fujitsu-net-ospf" was not found. (Path "/fujitsu-net-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-net-ospf@2018-01-22.yang 2>&1": Error: 'ietf-ospf@2015-03-09.yang' import of module 'ietf-key-chain' failed ietf-ospf@2015-03-09.yang:24.3: error(236): module not found Error: typedef definition for 'key-chain:key-chain-ref' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:692.18: error(250): definition not found Error: grouping definition for 'key-chain:crypto-algorithm-types' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:704.13: error(250): definition not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /var/yang/all_modules/ietf-routing@2018-03-13.yang ietf-ospf@2015-03-09.yang:2435.12: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:1952.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:2155.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2095.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2309.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route' ietf-ospf@2015-03-09.yang:2397.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface' ietf-ospf@2015-03-09.yang:2129.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces' ietf-ospf@2015-03-09.yang:2340.3: error(251): definition segment not found Warning: path failed (no nodes available): '/rt:routing/rt:routing-instance/rt:ribs/rt:rib/rt:name' Error: 'fujitsu-net-ospf@2018-01-22.yang' import of module 'ietf-ospf' revision '2015-03-09' failed fujitsu-net-ospf@2018-01-22.yang:14.3: error(250): definition not found Error: Module for prefix 'ospf' not found fujitsu-net-ospf@2018-01-22.yang:86.12: error(236): module not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' fujitsu-net-ospf@2018-01-22.yang:83.3: error(251): definition segment not found |
| fujitsu-notification-types@2018-05-31.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-notification-types@2018-05-31.yang --lint 2>&1": fujitsu-notification-types@2018-05-31.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:60: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:69: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:80: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types@2018-05-31.yang:84: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-notification-types@2018-05-31.yang 2>&1": Error: 'fujitsu-notification-types@2018-05-31.yang' import of module 'fujitsu-notifications' failed fujitsu-notification-types@2018-05-31.yang:5.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:89.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:95.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:101.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:107.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:113.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:119.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:125.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:131.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:137.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:143.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:149.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:155.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:161.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:167.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:173.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:179.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:185.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:191.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:197.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:203.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:209.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:215.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:221.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:227.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:233.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:239.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:245.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:251.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:257.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:263.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:269.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:275.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:281.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:287.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:293.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:299.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:305.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:311.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:317.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:323.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:329.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:335.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:341.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:347.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:353.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:367.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:373.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:379.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:385.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:391.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:397.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:403.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:409.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:415.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:421.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:427.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:433.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:439.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:445.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:451.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:457.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:463.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:469.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:475.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:481.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:487.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:493.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:499.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:505.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:511.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:517.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:523.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:529.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:535.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:541.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:547.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:553.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:559.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:565.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:571.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:577.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:583.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:589.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:595.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:601.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:607.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:613.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:619.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:625.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:631.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:637.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-notification-types@2018-05-31.yang:643.3: error(236): module not found |
|||
| fujitsu-notifications@2015-11-20.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-notifications@2015-11-20.yang --lint 2>&1": fujitsu-notifications@2015-11-20.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
||||
| fujitsu-optical-channel-interfaces-dev@2018-01-29.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-optical-channel-interfaces-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-optical-channel-interfaces.yang:12: error: module 'iana-if-type' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-optical-channel-interfaces.yang:49: warning: the revision statements are not given in reverse chronological order |
fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-optical-channel-interfaces.yang:49: warning: the revision statements are not given in reverse chronological order fujitsu-optical-channel-interfaces.yang:412: warning: explicit config statement is ignored |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-optical-channel-interfaces-dev.prod.yang --lint 2>&1": fujitsu-optical-channel-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:13: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:138: warning: RFC 8407: 4.4: statement "config" is given with its default value "true" fujitsu-optical-channel-interfaces-dev.prod.yang:139: error: keyword "units" not in canonical order (see RFC 6020, Section 12) |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-optical-channel-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config true" which is not present. (Path "/fujitsu-optical-channel-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/och:och/och:slot-width'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-optical-channel-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-optical-channel-interfaces.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-optical-channel-interfaces.yang:20.5: error(332): imported module has errors Warning: revision dates not in descending order fujitsu-optical-channel-interfaces.yang:49.5: warning(1035): bad revision-stmt order Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-optical-channel-interfaces.yang:378.12: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-optical-channel-interfaces.yang:410.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-optical-channel-interfaces.yang:378.12: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-optical-channel-interfaces.yang:410.13: error(250): definition not found Error: 'fujitsu-optical-channel-interfaces-dev.prod.yang' import of module 'fujitsu-optical-channel-interfaces' failed fujitsu-optical-channel-interfaces-dev.prod.yang:9.5: error(250): definition not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:channel-width' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:remote-tp-type' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:actual-vstimer' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:modulation-format' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:center-frequency' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:center-frequency-rx' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:lambda' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:lambda-rx' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:slot-width' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:admin-status' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:ais-pt' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:direction' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:roadm-type' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:Nyquist' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:confmode-type' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:tx-target-power' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found Error: object 'och' not found in path '/if:interfaces/if:interface/och:och/och:circuit-id' fujitsu-optical-channel-interfaces-dev.prod.yang:224.2: error(251): definition segment not found |
| fujitsu-optical-channel-interfaces@2017-07-14.yang | FAILED | fujitsu-optical-channel-interfaces@2017-07-14.yang:0: warning: expected revision '2017-07-14', got '2018-04-11' fujitsu-optical-channel-interfaces@2017-07-14.yang:42: warning: the revision statements are not given in reverse chronological order |
fujitsu-optical-channel-interfaces@2017-07-14.yang:1: warning: unexpected latest revision "2018-04-11" in fujitsu-optical-channel-interfaces@2017-07-14.yang, should be "2017-07-14" fujitsu-optical-channel-interfaces@2017-07-14.yang:42: warning: the revision statements are not given in reverse chronological order fujitsu-optical-channel-interfaces@2017-07-14.yang:411: warning: explicit config statement is ignored /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-optical-channel-interfaces@2017-07-14.yang --lint 2>&1": fujitsu-optical-channel-interfaces@2017-07-14.yang:1: warning: unexpected latest revision "2018-04-11" in fujitsu-optical-channel-interfaces@2017-07-14.yang, should be "2017-07-14" fujitsu-optical-channel-interfaces@2017-07-14.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:42: warning: the revision statements are not given in reverse chronological order fujitsu-optical-channel-interfaces@2017-07-14.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:116: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces@2017-07-14.yang:349: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:352: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:376: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:384: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces@2017-07-14.yang:385: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces@2017-07-14.yang:402: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:403: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:408: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-optical-channel-interfaces@2017-07-14.yang:411: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces@2017-07-14.yang:411: warning: explicit config statement is ignored fujitsu-optical-channel-interfaces@2017-07-14.yang:412: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
libyang warn: File name "fujitsu-optical-channel-interfaces@2017-07-14.yang" does not match module revision "2018-04-11". | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-optical-channel-interfaces@2017-07-14.yang 2>&1": Error: 'fujitsu-optical-channel-interfaces@2017-07-14.yang' import of module 'fujitsu-entity-states' failed fujitsu-optical-channel-interfaces@2017-07-14.yang:12.3: error(236): module not found Error: 'fujitsu-optical-channel-interfaces@2017-07-14.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-optical-channel-interfaces@2017-07-14.yang:15.3: error(236): module not found Warning: revision dates not in descending order fujitsu-optical-channel-interfaces@2017-07-14.yang:42.3: warning(1035): bad revision-stmt order Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-optical-channel-interfaces@2017-07-14.yang:112.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-optical-channel-interfaces@2017-07-14.yang:113.5: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-optical-channel-interfaces@2017-07-14.yang:382.7: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-optical-channel-interfaces@2017-07-14.yang:409.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-optical-channel-interfaces@2017-07-14.yang:112.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-optical-channel-interfaces@2017-07-14.yang:113.5: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-optical-channel-interfaces@2017-07-14.yang:382.7: error(250): definition not found Error: object 'oper-status' not found in module fujitsu-optical-channel-interfaces in Xpath target oper-status fujitsu-optical-channel-interfaces@2017-07-14.yang:392.7: error(250): definition not found Error: refinement node 'oper-status' not found in grouping 'och-attributes' fujitsu-optical-channel-interfaces@2017-07-14.yang:393.9: error(366): missing refine target Error: grouping 'ains-prov-keywords' not found fujitsu-optical-channel-interfaces@2017-07-14.yang:409.7: error(250): definition not found |
| fujitsu-optical-tributary-signal-dev@2016-09-10.yang | FAILED | fujitsu-optical-tributary-signal-dev.prod.yang:23: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:28: warning: the revision statements are not given in reverse chronological order |
fujitsu-optical-tributary-signal-dev.prod.yang:23: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:28: warning: the revision statements are not given in reverse chronological order fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-optical-tributary-signal-dev.prod.yang --lint 2>&1": fujitsu-optical-tributary-signal-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-optical-tributary-signal-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-optical-tributary-signal-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-optical-tributary-signal-dev.prod.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:23: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:28: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:45: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-dev.prod.yang:49: error: keyword "description" not in canonical order (see RFC 6020, Section 12) |
Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-if-type.yang:5.3: warning(1015): import not used Warning: compare value 'fjift:fujitsuOtsi' invalid for object 'ietf-interfaces:type type:identityref' XPath:(../if:type = 'fjift:fujitsuOtsi') or (../if:type = 'fjift:fujitsuOtsiV2') fujitsu-optical-tributary-signal.yang: line 464: warning(1052): XPath compare value invalid for YANG type Warning: compare value 'fjift:fujitsuOtsiV2' invalid for object 'ietf-interfaces:type type:identityref' XPath:(../if:type = 'fjift:fujitsuOtsi') or (../if:type = 'fjift:fujitsuOtsiV2') fujitsu-optical-tributary-signal.yang: line 464: warning(1052): XPath compare value invalid for YANG type Warning: revision dates not in descending order fujitsu-optical-tributary-signal-dev.prod.yang:23.5: warning(1035): bad revision-stmt order Warning: revision dates not in descending order fujitsu-optical-tributary-signal-dev.prod.yang:28.5: warning(1035): bad revision-stmt order |
|
| fujitsu-optical-tributary-signal-group-dev@2016-11-04.yang | FAILED | fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-optical-tributary-signal-group-dev.prod.yang --lint 2>&1": fujitsu-optical-tributary-signal-group-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:26: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:31: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:37: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:42: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:96: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-if-type.yang:5.3: warning(1015): import not used Warning: compare value 'fjift:fujitsuOtsig' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'fjift:fujitsuOtsig' fujitsu-optical-tributary-signal-group.yang: line 279: warning(1052): XPath compare value invalid for YANG type |
||
| fujitsu-optical-tributary-signal-group@2015-04-10.yang | FAILED | fujitsu-if-type@2019-05-16.yang:5: warning: imported module "ietf-interfaces" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-optical-tributary-signal-group@2015-04-10.yang --lint 2>&1": fujitsu-optical-tributary-signal-group@2015-04-10.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:78: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group@2015-04-10.yang:81: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:83: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:86: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:214: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:217: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:227: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:230: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:258: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:286: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:287: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group@2015-04-10.yang:292: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-optical-tributary-signal-group@2015-04-10.yang 2>&1": Error: 'fujitsu-optical-tributary-signal-group@2015-04-10.yang' import of module 'fujitsu-state-timer' failed fujitsu-optical-tributary-signal-group@2015-04-10.yang:9.3: error(236): module not found Error: 'fujitsu-optical-tributary-signal-group@2015-04-10.yang' import of module 'fujitsu-entity-states' failed fujitsu-optical-tributary-signal-group@2015-04-10.yang:12.3: error(236): module not found Error: 'fujitsu-optical-tributary-signal-group@2015-04-10.yang' import of module 'fujitsu-if-type' failed fujitsu-optical-tributary-signal-group@2015-04-10.yang:15.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-optical-tributary-signal-group@2015-04-10.yang:74.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-optical-tributary-signal-group@2015-04-10.yang:75.5: error(250): definition not found Error: grouping definition for 'st:state-timer' not found in module fujitsu-state-timer fujitsu-optical-tributary-signal-group@2015-04-10.yang:265.7: error(250): definition not found Error: grouping definition for 'st:state-timer' not found in module fujitsu-state-timer fujitsu-optical-tributary-signal-group@2015-04-10.yang:293.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-optical-tributary-signal-group@2015-04-10.yang:74.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-optical-tributary-signal-group@2015-04-10.yang:75.5: error(250): definition not found Error: grouping 'state-timer' not found fujitsu-optical-tributary-signal-group@2015-04-10.yang:265.7: error(250): definition not found Error: object 'oper-status' not found in module fujitsu-optical-tributary-signal-group in Xpath target oper-status fujitsu-optical-tributary-signal-group@2015-04-10.yang:270.7: error(250): definition not found Error: refinement node 'oper-status' not found in grouping 'otsig-attributes' fujitsu-optical-tributary-signal-group@2015-04-10.yang:274.9: error(366): missing refine target Error: grouping 'state-timer' not found fujitsu-optical-tributary-signal-group@2015-04-10.yang:293.7: error(250): definition not found Warning: compare value 'fjift:fujitsuOtsig' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'fjift:fujitsuOtsig' fujitsu-optical-tributary-signal-group@2015-04-10.yang: line 260: warning(1052): XPath compare value invalid for YANG type |
||
| fujitsu-optical-tributary-signal@2018-06-13.yang | FAILED | fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-optical-tributary-signal.yang --lint 2>&1": fujitsu-optical-tributary-signal.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:64: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:69: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:88: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal.yang:96: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:99: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:102: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:278: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:281: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:431: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:434: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:462: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-tributary-signal.yang:504: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-tributary-signal.yang:512: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-if-type.yang:5.3: warning(1015): import not used Warning: compare value 'fjift:fujitsuOtsi' invalid for object 'ietf-interfaces:type type:identityref' XPath:(../if:type = 'fjift:fujitsuOtsi') or (../if:type = 'fjift:fujitsuOtsiV2') fujitsu-optical-tributary-signal.yang: line 464: warning(1052): XPath compare value invalid for YANG type Warning: compare value 'fjift:fujitsuOtsiV2' invalid for object 'ietf-interfaces:type type:identityref' XPath:(../if:type = 'fjift:fujitsuOtsi') or (../if:type = 'fjift:fujitsuOtsiV2') fujitsu-optical-tributary-signal.yang: line 464: warning(1052): XPath compare value invalid for YANG type |
||
| fujitsu-ospf@2015-11-04.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-ospf@2015-11-04.yang 2>&1": ./ietf-ospf@2015-03-09.yang:704: error: grouping 'crypto-algorithm-types' in module 'ietf-key-chain' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-instance' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocols' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocol' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-instance' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocols' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocol' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'ribs' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'rib' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'routes' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'route' not found ./ietf-ospf@2015-03-09.yang:2435: error: typedef 'routing-instance-ref' in module 'ietf-routing' not found fujitsu-ospf@2015-11-04.yang:158: error: node 'interface' in module 'ietf-ospf' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ospf@2015-11-04.yang 2>&1": fujitsu-ospf@2015-11-04.yang:8: warning: imported module "ietf-yang-types" not used fujitsu-ospf@2015-11-04.yang:11: warning: imported module "ietf-inet-types" not used fujitsu-ospf@2015-11-04.yang:14: warning: imported module "ietf-ospf" not used fujitsu-ospf@2015-11-04.yang:95: error: node ietf-routing::routing-instance is not found fujitsu-ospf@2015-11-04.yang:158: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1970 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2121 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:601: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2151 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1458): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2151 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1467): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2169 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1486): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2169 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1495): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2187 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1514): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2187 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1523): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1946 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1614): warning: node "ietf-routing::routing-instance" is not found in "ietf-routing::routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1868: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:1907: error: type "routing-instance-ref" not found in module "ietf-routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2003: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2020: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2018 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2038: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2052: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2050 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2064: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2087: error: type "routing-instance-ref" not found in module "ietf-routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2134: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2193: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2207: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2205 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2224: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2238: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2236 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2292: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-ospf.yang:2331: error: type "routing-instance-ref" not found in module "ietf-routing" |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ospf@2015-11-04.yang --lint 2>&1": fujitsu-ospf@2015-11-04.yang:8: warning: imported module "ietf-yang-types" not used fujitsu-ospf@2015-11-04.yang:11: warning: imported module "ietf-inet-types" not used fujitsu-ospf@2015-11-04.yang:14: warning: imported module "ietf-ospf" not used fujitsu-ospf@2015-11-04.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ospf@2015-11-04.yang:50: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-ospf@2015-11-04.yang:55: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ospf@2015-11-04.yang:70: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf@2015-11-04.yang:78: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf@2015-11-04.yang:87: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-ospf@2015-11-04.yang:88: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf@2015-11-04.yang:95: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ospf@2015-11-04.yang:95: error: node ietf-routing::routing-instance is not found fujitsu-ospf@2015-11-04.yang:100: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ospf@2015-11-04.yang:158: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ospf@2015-11-04.yang:158: error: node ietf-routing::routing-instance is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/fujitsu-ospf@2015-11-04.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "fujitsu-ospf" was not found. (Path "/fujitsu-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface" from module "fujitsu-ospf" was not found. (Path "/fujitsu-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-ospf@2015-11-04.yang 2>&1": Error: 'ietf-ospf@2015-03-09.yang' import of module 'ietf-key-chain' failed ietf-ospf@2015-03-09.yang:24.3: error(236): module not found Error: typedef definition for 'key-chain:key-chain-ref' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:692.18: error(250): definition not found Error: grouping definition for 'key-chain:crypto-algorithm-types' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:704.13: error(250): definition not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /var/yang/all_modules/ietf-routing@2018-03-13.yang ietf-ospf@2015-03-09.yang:2435.12: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:1952.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:2155.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2095.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2309.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route' ietf-ospf@2015-03-09.yang:2397.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface' ietf-ospf@2015-03-09.yang:2129.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces' ietf-ospf@2015-03-09.yang:2340.3: error(251): definition segment not found Warning: path failed (no nodes available): '/rt:routing/rt:routing-instance/rt:ribs/rt:rib/rt:name' Error: 'fujitsu-ospf@2015-11-04.yang' import of module 'ietf-ospf' revision '2015-03-09' failed fujitsu-ospf@2015-11-04.yang:14.3: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' fujitsu-ospf@2015-11-04.yang:95.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface' fujitsu-ospf@2015-11-04.yang:158.3: error(251): definition segment not found Warning: Module 'ietf-yang-types' not used fujitsu-ospf@2015-11-04.yang:8.3: warning(1015): import not used Warning: Module 'ietf-inet-types' not used fujitsu-ospf@2015-11-04.yang:11.3: warning(1015): import not used Warning: Module 'ietf-ospf' not used fujitsu-ospf@2015-11-04.yang:14.3: warning(1015): import not used |
| fujitsu-otn-odu-interfaces-dev@2017-10-05.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order |
fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-otn-odu-interfaces.yang:875: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:935: warning: explicit config statement is ignored |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-odu-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-odu-interfaces-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:60: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:64: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:68: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:73: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:82: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:86: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:90: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:94: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:98: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:102: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-odu-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-odu-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/odu:odu/odu:direction'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-odu-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:28.5: warning(1035): bad revision-stmt order Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:32.5: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:10.5: warning(1015): import not used Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-otn-odu-interfaces.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-otn-odu-interfaces.yang:29.5: error(332): imported module has errors Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces.yang:881.13: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces.yang:933.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces.yang:881.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces.yang:933.13: error(250): definition not found Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces.yang: line 875: warning(1052): XPath compare value invalid for YANG type Error: 'fujitsu-otn-odu-interfaces-dev.prod.yang' import of module 'fujitsu-otn-odu-interfaces' failed fujitsu-otn-odu-interfaces-dev.prod.yang:12.5: error(250): definition not found Load module 'fujitsu-otn-odu-interfaces' failed (imported module has errors) Error: failure importing module 'fujitsu-otn-odu-interfaces' fujitsu-otn-odu-interfaces-dev.prod.yang:107.6: error(332): imported module has errors Load module 'fujitsu-otn-odu-interfaces' failed (imported module has errors) Error: failure importing module 'fujitsu-otn-odu-interfaces' fujitsu-otn-odu-interfaces-dev.prod.yang:112.6: error(332): imported module has errors Load module 'fujitsu-otn-odu-interfaces' failed (imported module has errors) Error: failure importing module 'fujitsu-otn-odu-interfaces' fujitsu-otn-odu-interfaces-dev.prod.yang:117.6: error(332): imported module has errors Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tx-clock-source' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:direction' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:circuit-id' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:monitoring-mode' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:actual-vstimer' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tx-ftfl' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:rx-ftfl' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:auto-rx' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:auto-tx' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:extension' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:auto-rx' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:auto-tx' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:degthr' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:monitoring-mode' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:proactive-DM' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:ltc-act-enabled' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:opu/odu:payload-type' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:opu/odu:exp-payload-type' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:list-gcc' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:ais-pt' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:proactive-DM' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:gcc0-pass-through' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:degthr' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:testPattern' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:pm/odu:pm-threshold/odu:pm-type' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:pm/odu:pm-threshold/odu:pm-th-metered' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:pm/odu:pm-threshold/odu:pm-th-binned/odu:pm-time-periods/odu:pm-time-period' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:pm/odu:pm-threshold/odu:pm-type' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:pm/odu:pm-threshold/odu:pm-th-metered' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:pm/odu:pm-threshold/odu:pm-th-binned/odu:pm-time-periods/odu:pm-time-period' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:standard/odu:itu/odu:tti-itu/odu:tim-det-mode' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:standard/odu:itu/odu:tti-itu/odu:tim-det-mode' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:pm/odu:pm-threshold/odu:pm-th-binned/odu:pm-time-periods/odu:pm-value' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:pm/odu:pm-threshold/odu:pm-th-binned/odu:pm-time-periods/odu:pm-value' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:standard/odu:itu/odu:tti-itu/odu:exp-tti/odu:op-spec' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:standard/odu:itu/odu:tti-itu/odu:tx-tti/odu:op-spec' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:standard/odu:itu/odu:tti-itu/odu:rx-tti/odu:op-spec' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:standard/odu:ansi/odu:tti-ansi' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:standard/odu:itu/odu:tti-itu/odu:exp-tti/odu:op-spec' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:standard/odu:itu/odu:tti-itu/odu:tx-tti/odu:op-spec' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:standard/odu:itu/odu:tti-itu/odu:rx-tti/odu:op-spec' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:tcm/odu:standard/odu:ansi/odu:tti-ansi' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found Error: object 'odu' not found in path '/if:interfaces/if:interface/odu:odu/odu:parent-odu-allocation' fujitsu-otn-odu-interfaces-dev.prod.yang:437.2: error(251): definition segment not found |
| fujitsu-otn-odu-interfaces@2018-02-02.yang | FAILED | fujitsu-otn-odu-interfaces@2018-02-02.yang:869: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces@2018-02-02.yang:921: warning: explicit config statement is ignored /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-odu-interfaces@2018-02-02.yang --lint 2>&1": fujitsu-otn-odu-interfaces@2018-02-02.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:79: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:83: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:87: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:91: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:95: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:101: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:105: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:109: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:113: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:117: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:370: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:390: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:425: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:444: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:450: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:501: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:502: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:512: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:646: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:652: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:654: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:657: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:660: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:666: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:694: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:725: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:728: error: keyword "min-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:730: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:748: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:749: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:750: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:821: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:839: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:843: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:848: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:849: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:854: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:855: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:867: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:869: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces@2018-02-02.yang:875: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:876: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:912: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:913: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:918: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:921: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:921: warning: explicit config statement is ignored fujitsu-otn-odu-interfaces@2018-02-02.yang:922: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces@2018-02-02.yang:933: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:936: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:939: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces@2018-02-02.yang:942: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-otn-odu-interfaces@2018-02-02.yang 2>&1": Error: 'fujitsu-otn-odu-interfaces@2018-02-02.yang' import of module 'fujitsu-entity-states' failed fujitsu-otn-odu-interfaces@2018-02-02.yang:9.3: error(236): module not found Error: 'fujitsu-otn-odu-interfaces@2018-02-02.yang' import of module 'fujitsu-entity-maintenance-testsignal' failed fujitsu-otn-odu-interfaces@2018-02-02.yang:12.3: error(236): module not found Error: 'fujitsu-otn-odu-interfaces@2018-02-02.yang' import of module 'fujitsu-gcc' failed fujitsu-otn-odu-interfaces@2018-02-02.yang:15.3: error(236): module not found Error: 'fujitsu-otn-odu-interfaces@2018-02-02.yang' import of module 'fujitsu-otn' failed fujitsu-otn-odu-interfaces@2018-02-02.yang:18.3: error(236): module not found Error: 'fujitsu-otn-odu-interfaces@2018-02-02.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-otn-odu-interfaces@2018-02-02.yang:21.3: error(236): module not found Error: 'fujitsu-otn-odu-interfaces@2018-02-02.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-otn-odu-interfaces@2018-02-02.yang:24.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-otn-odu-interfaces@2018-02-02.yang:508.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-otn-odu-interfaces@2018-02-02.yang:509.5: error(250): definition not found Error: grouping definition for 'otn:tti-choice' not found in module fujitsu-otn fujitsu-otn-odu-interfaces@2018-02-02.yang:623.5: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-otn-odu-interfaces@2018-02-02.yang:643.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-otn-odu-interfaces@2018-02-02.yang:650.5: error(250): definition not found Error: grouping definition for 'otn:tti-choice' not found in module fujitsu-otn fujitsu-otn-odu-interfaces@2018-02-02.yang:795.5: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces@2018-02-02.yang:873.7: error(250): definition not found Error: grouping definition for 'fujitsu-testsignal:maint-testsignal' not found in module fujitsu-entity-maintenance-testsignal fujitsu-otn-odu-interfaces@2018-02-02.yang:883.7: error(250): definition not found Error: grouping definition for 'fujitsuGcc:gcc-group' not found in module fujitsu-gcc fujitsu-otn-odu-interfaces@2018-02-02.yang:908.9: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces@2018-02-02.yang:919.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:508.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:509.5: error(250): definition not found Error: grouping 'tti-choice' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:623.5: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:643.7: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:650.5: error(250): definition not found Error: grouping 'tti-choice' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:795.5: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:873.7: error(250): definition not found Error: grouping 'maint-testsignal' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:883.7: error(250): definition not found Error: object 'oper-status' not found in module fujitsu-otn-odu-interfaces in Xpath target oper-status fujitsu-otn-odu-interfaces@2018-02-02.yang:884.7: error(250): definition not found Error: refinement node 'oper-status' not found in grouping 'odu-attributes' fujitsu-otn-odu-interfaces@2018-02-02.yang:885.9: error(366): missing refine target Error: grouping 'gcc-group' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:908.9: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces@2018-02-02.yang:919.7: error(250): definition not found Error: object 'gccType' not found in module fujitsu-otn-odu-interfaces in Xpath target gccType fujitsu-otn-odu-interfaces@2018-02-02.yang:905.9: error(250): definition not found Error: invalid identifier in key for list 'list-gcc' (gccType) fujitsu-otn-odu-interfaces@2018-02-02.yang:905.9: error(250): definition not found Error: object 'gccType' not found in module fujitsu-otn-odu-interfaces in Xpath target gccType fujitsu-otn-odu-interfaces@2018-02-02.yang:904.7: error(250): definition not found Error: invalid identifier in key for list 'list-gcc' (gccType) fujitsu-otn-odu-interfaces@2018-02-02.yang:904.7: error(250): definition not found Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces@2018-02-02.yang: line 869: warning(1052): XPath compare value invalid for YANG type |
||
| fujitsu-otn-oducn-interfaces-dev@2016-09-13.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-otn-oducn-interfaces-dev.prod.yang:22: warning: the revision statements are not given in reverse chronological order |
fujitsu-otn-oducn-interfaces-dev.prod.yang:22: warning: the revision statements are not given in reverse chronological order fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used fujitsu-otn-odu-interfaces.yang:875: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:935: warning: explicit config statement is ignored fujitsu-otn-oducn-interfaces.yang:48: warning: imported module "fujitsu-equipment" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-oducn-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-oducn-interfaces-dev.prod.yang:5: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:5: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:5: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:17: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:22: warning: the revision statements are not given in reverse chronological order fujitsu-otn-oducn-interfaces-dev.prod.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:92: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-oducn-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-oducn-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/oducn:oducn/oducn:rate'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-oducn-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:28.5: warning(1035): bad revision-stmt order Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:32.5: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:10.5: warning(1015): import not used Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-otn-odu-interfaces.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-otn-odu-interfaces.yang:29.5: error(332): imported module has errors Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces.yang:881.13: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces.yang:933.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces.yang:881.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces.yang:933.13: error(250): definition not found Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces.yang: line 875: warning(1052): XPath compare value invalid for YANG type Error: 'fujitsu-otn-oducn-interfaces.yang' import of module 'fujitsu-otn-odu-interfaces' failed fujitsu-otn-oducn-interfaces.yang:44.5: error(250): definition not found Warning: revision with same date on line 34 fujitsu-port.yang:40.5: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:13.3: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-if-type.yang:5.3: warning(1015): import not used Error: grouping definition for 'odu:tcm-attributes' not found in module fujitsu-otn-odu-interfaces fujitsu-otn-oducn-interfaces.yang:321.9: error(250): definition not found Error: grouping 'tcm-attributes' not found fujitsu-otn-oducn-interfaces.yang:321.9: error(250): definition not found Error: object 'layer' not found in module fujitsu-otn-oducn-interfaces in Xpath target layer fujitsu-otn-oducn-interfaces.yang:320.9: error(250): definition not found Error: invalid identifier in key for list 'tcm' (layer) fujitsu-otn-oducn-interfaces.yang:320.9: error(250): definition not found Error: object 'layer' not found in module fujitsu-otn-oducn-interfaces in Xpath target layer fujitsu-otn-oducn-interfaces.yang:319.9: error(250): definition not found Error: invalid identifier in key for list 'tcm' (layer) fujitsu-otn-oducn-interfaces.yang:319.9: error(250): definition not found Warning: compare value 'fjift:fujitsuOduc' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'fjift:fujitsuOduc' fujitsu-otn-oducn-interfaces.yang: line 355: warning(1052): XPath compare value invalid for YANG type Warning: Module 'fujitsu-equipment' not used fujitsu-otn-oducn-interfaces.yang:48.5: warning(1015): import not used Error: 'fujitsu-otn-oducn-interfaces-dev.prod.yang' import of module 'fujitsu-otn-oducn-interfaces' failed fujitsu-otn-oducn-interfaces-dev.prod.yang:13.5: error(250): definition not found Warning: revision dates not in descending order fujitsu-otn-oducn-interfaces-dev.prod.yang:22.5: warning(1035): bad revision-stmt order Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:rate' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:direction' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:testPattern' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:testsignal-type' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:opu/oducn:payload-type' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:opu/oducn:exp-payload-type' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:ais-pt' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:list-gcc' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:standard/oducn:ansi' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:vstimer' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:actual-vstimer' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:proactive-DM' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:tcm' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:degthr' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:standard/oducn:itu/oducn:tti-itu/oducn:tim-det-mode' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:standard/oducn:itu/oducn:tti-itu/oducn:exp-tti/oducn:op-spec' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:monitoring-mode' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found Error: object 'oducn' not found in path '/if:interfaces/if:interface/oducn:oducn/oducn:circuit-id' fujitsu-otn-oducn-interfaces-dev.prod.yang:195.3: error(251): definition segment not found |
| fujitsu-otn-oducn-interfaces@2016-07-22.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order |
fujitsu-otn-oducn-interfaces.yang:48: warning: imported module "fujitsu-equipment" not used fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-entity-maintenance-testsignal.yang:28: warning: the revision statements are not given in reverse chronological order fujitsu-entity-maintenance-testsignal.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used fujitsu-otn-odu-interfaces.yang:875: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:935: warning: explicit config statement is ignored |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-oducn-interfaces.yang --lint 2>&1": fujitsu-otn-oducn-interfaces.yang:48: warning: imported module "fujitsu-equipment" not used fujitsu-otn-oducn-interfaces.yang:88: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces.yang:93: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces.yang:177: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:220: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:271: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-oducn-interfaces.yang:275: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:277: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-oducn-interfaces.yang:280: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-oducn-interfaces.yang:293: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:319: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:353: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:388: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:389: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:395: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-oducn-interfaces.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:28.5: warning(1035): bad revision-stmt order Warning: revision dates not in descending order fujitsu-entity-maintenance-testsignal.yang:32.5: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:10.5: warning(1015): import not used Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-otn-odu-interfaces.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-otn-odu-interfaces.yang:29.5: error(332): imported module has errors Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces.yang:881.13: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-odu-interfaces.yang:933.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces.yang:881.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-odu-interfaces.yang:933.13: error(250): definition not found Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces.yang: line 875: warning(1052): XPath compare value invalid for YANG type Error: 'fujitsu-otn-oducn-interfaces.yang' import of module 'fujitsu-otn-odu-interfaces' failed fujitsu-otn-oducn-interfaces.yang:44.5: error(250): definition not found Warning: revision with same date on line 34 fujitsu-port.yang:40.5: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:13.3: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-if-type.yang:5.3: warning(1015): import not used Error: grouping definition for 'odu:tcm-attributes' not found in module fujitsu-otn-odu-interfaces fujitsu-otn-oducn-interfaces.yang:321.9: error(250): definition not found Error: grouping 'tcm-attributes' not found fujitsu-otn-oducn-interfaces.yang:321.9: error(250): definition not found Error: object 'layer' not found in module fujitsu-otn-oducn-interfaces in Xpath target layer fujitsu-otn-oducn-interfaces.yang:320.9: error(250): definition not found Error: invalid identifier in key for list 'tcm' (layer) fujitsu-otn-oducn-interfaces.yang:320.9: error(250): definition not found Error: object 'layer' not found in module fujitsu-otn-oducn-interfaces in Xpath target layer fujitsu-otn-oducn-interfaces.yang:319.9: error(250): definition not found Error: invalid identifier in key for list 'tcm' (layer) fujitsu-otn-oducn-interfaces.yang:319.9: error(250): definition not found Warning: compare value 'fjift:fujitsuOduc' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'fjift:fujitsuOduc' fujitsu-otn-oducn-interfaces.yang: line 355: warning(1052): XPath compare value invalid for YANG type Warning: Module 'fujitsu-equipment' not used fujitsu-otn-oducn-interfaces.yang:48.5: warning(1015): import not used |
|
| fujitsu-otn-otu-interfaces-dev@2017-05-29.yang | FAILED | fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-otn-otu-interfaces.yang:272: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-otu-interfaces.yang:318: warning: explicit config statement is ignored |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-otu-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-otu-interfaces-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-otu-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-otu-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/otu:otu/otu:direction'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-otu-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:10.5: warning(1015): import not used Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-otn-otu-interfaces.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-otn-otu-interfaces.yang:32.5: error(332): imported module has errors Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-otu-interfaces.yang:280.13: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-otu-interfaces.yang:316.14: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-otu-interfaces.yang:280.13: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-otu-interfaces.yang:316.14: error(250): definition not found Warning: compare value 'ianaift:otnOtu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOtu' fujitsu-otn-otu-interfaces.yang: line 272: warning(1052): XPath compare value invalid for YANG type Error: 'fujitsu-otn-otu-interfaces-dev.prod.yang' import of module 'fujitsu-otn-otu-interfaces' failed fujitsu-otn-otu-interfaces-dev.prod.yang:12.5: error(250): definition not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:fec' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:direction' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:location' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:degthr' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:circuit-id' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:list-gcc/otu:gccType' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:list-gcc/otu:gccEnabled' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:list-gcc/otu:protocol' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:actual-vstimer' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:auto-rx' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:auto-tx' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:pm/otu:pm-threshold/otu:pm-type' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:pm/otu:pm-threshold/otu:pm-th-metered' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:pm/otu:pm-threshold/otu:pm-th-binned/otu:pm-time-periods/otu:pm-time-period' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:standard/otu:itu/otu:tti-itu/otu:tim-det-mode' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:pm/otu:pm-threshold/otu:pm-th-binned/otu:pm-time-periods/otu:pm-value' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:standard/otu:itu/otu:tti-itu/otu:exp-tti/otu:op-spec' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:standard/otu:itu/otu:tti-itu/otu:tx-tti/otu:op-spec' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:standard/otu:itu/otu:tti-itu/otu:rx-tti/otu:op-spec' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found Error: object 'otu' not found in path '/if:interfaces/if:interface/otu:otu/otu:standard/otu:ansi/otu:tti-ansi' fujitsu-otn-otu-interfaces-dev.prod.yang:237.2: error(251): definition segment not found |
|
| fujitsu-otn-otu-interfaces@2018-01-09.yang | FAILED | fujitsu-otn-otu-interfaces@2018-01-09.yang:270: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-otu-interfaces@2018-01-09.yang:307: warning: explicit config statement is ignored /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-otu-interfaces@2018-01-09.yang --lint 2>&1": fujitsu-otn-otu-interfaces@2018-01-09.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:114: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:149: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces@2018-01-09.yang:268: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:270: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-otu-interfaces@2018-01-09.yang:277: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces@2018-01-09.yang:278: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces@2018-01-09.yang:298: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:299: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:304: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-otu-interfaces@2018-01-09.yang:307: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces@2018-01-09.yang:307: warning: explicit config statement is ignored fujitsu-otn-otu-interfaces@2018-01-09.yang:308: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-otn-otu-interfaces@2018-01-09.yang 2>&1": Error: 'fujitsu-otn-otu-interfaces@2018-01-09.yang' import of module 'fujitsu-entity-states' failed fujitsu-otn-otu-interfaces@2018-01-09.yang:9.3: error(236): module not found Error: 'fujitsu-otn-otu-interfaces@2018-01-09.yang' import of module 'fujitsu-entity-maintenance-loopback' failed fujitsu-otn-otu-interfaces@2018-01-09.yang:12.3: error(236): module not found Error: 'fujitsu-otn-otu-interfaces@2018-01-09.yang' import of module 'fujitsu-gcc' failed fujitsu-otn-otu-interfaces@2018-01-09.yang:15.3: error(236): module not found Error: 'fujitsu-otn-otu-interfaces@2018-01-09.yang' import of module 'fujitsu-otn' failed fujitsu-otn-otu-interfaces@2018-01-09.yang:18.3: error(236): module not found Error: 'fujitsu-otn-otu-interfaces@2018-01-09.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-otn-otu-interfaces@2018-01-09.yang:21.3: error(236): module not found Error: 'fujitsu-otn-otu-interfaces@2018-01-09.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-otn-otu-interfaces@2018-01-09.yang:24.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-otn-otu-interfaces@2018-01-09.yang:145.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-otn-otu-interfaces@2018-01-09.yang:146.5: error(250): definition not found Error: grouping definition for 'otn:tti-choice' not found in module fujitsu-otn fujitsu-otn-otu-interfaces@2018-01-09.yang:152.5: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-otn-otu-interfaces@2018-01-09.yang:265.5: error(250): definition not found Error: grouping definition for 'fujitsu-loopback:maint-loopback' not found in module fujitsu-entity-maintenance-loopback fujitsu-otn-otu-interfaces@2018-01-09.yang:274.7: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-otu-interfaces@2018-01-09.yang:275.7: error(250): definition not found Error: grouping definition for 'fujitsuGcc:gcc-group' not found in module fujitsu-gcc fujitsu-otn-otu-interfaces@2018-01-09.yang:294.9: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-otn-otu-interfaces@2018-01-09.yang:305.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:145.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:146.5: error(250): definition not found Error: grouping 'tti-choice' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:152.5: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:265.5: error(250): definition not found Error: grouping 'maint-loopback' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:274.7: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:275.7: error(250): definition not found Error: object 'oper-status' not found in module fujitsu-otn-otu-interfaces in Xpath target oper-status fujitsu-otn-otu-interfaces@2018-01-09.yang:285.7: error(250): definition not found Error: refinement node 'oper-status' not found in grouping 'otu-attributes' fujitsu-otn-otu-interfaces@2018-01-09.yang:286.9: error(366): missing refine target Error: grouping 'gcc-group' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:294.9: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-otn-otu-interfaces@2018-01-09.yang:305.7: error(250): definition not found Error: object 'gccType' not found in module fujitsu-otn-otu-interfaces in Xpath target gccType fujitsu-otn-otu-interfaces@2018-01-09.yang:291.9: error(250): definition not found Error: invalid identifier in key for list 'list-gcc' (gccType) fujitsu-otn-otu-interfaces@2018-01-09.yang:291.9: error(250): definition not found Error: object 'gccType' not found in module fujitsu-otn-otu-interfaces in Xpath target gccType fujitsu-otn-otu-interfaces@2018-01-09.yang:290.7: error(250): definition not found Error: invalid identifier in key for list 'list-gcc' (gccType) fujitsu-otn-otu-interfaces@2018-01-09.yang:290.7: error(250): definition not found Warning: compare value 'ianaift:otnOtu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOtu' fujitsu-otn-otu-interfaces@2018-01-09.yang: line 270: warning(1052): XPath compare value invalid for YANG type |
||
| fujitsu-otn-otucn-interfaces-dev@2017-05-19.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-loopback.yang:47: warning: The XPath expression references an undefined node: the node 'loopback' from module 'fujitsu-otn-otucn-interfaces' (in node 'otucn' in module 'fujitsu-otn-otucn-interfaces' from 'fujitsu-otn-otucn-interfaces') is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-entity-maintenance-loopback.yang:63: warning: The XPath expression references an undefined node: the node 'loopback' from module 'fujitsu-otn-otucn-interfaces' (in node 'otucn' in module 'fujitsu-otn-otucn-interfaces' from 'fujitsu-otn-otucn-interfaces') is not found |
fujitsu-otn-otucn-interfaces.yang:227 (at fujitsu-entity-maintenance-loopback.yang:47): warning: node "fujitsu-otn-otucn-interfaces::loopback" is not found in "fujitsu-otn-otucn-interfaces::otucn" fujitsu-otn-otucn-interfaces.yang:227 (at fujitsu-entity-maintenance-loopback.yang:63): warning: node "fujitsu-otn-otucn-interfaces::loopback" is not found in "fujitsu-otn-otucn-interfaces::otucn" fujitsu-if-type.yang:5: warning: imported module "ietf-interfaces" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-otucn-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-otucn-interfaces-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:6: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-otucn-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-otucn-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/otucn:otucn/otucn:rate'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-otn-otucn-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-if-type.yang:5.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:10.5: warning(1015): import not used fujitsu-otn-otucn-interfaces.yang:183.13: error(223): entry exists Error: 'description' token not allowed here Error: Got 'description', Expected: anyxml, container, leaf, leaf-list, list, choice, uses,or augment keyword fujitsu-otn-otucn-interfaces.yang:192.13: error(246): wrong token value Error: Extra input after end of module starting on line 195 fujitsu-otn-otucn-interfaces.yang:195.5: error(281): extra node Warning: Module 'ietf-interfaces' not used fujitsu-otn-otucn-interfaces.yang:24.5: warning(1015): import not used Warning: Module 'fujitsu-state-timer' not used fujitsu-otn-otucn-interfaces.yang:28.5: warning(1015): import not used Warning: Module 'fujitsu-entity-maintenance-loopback' not used fujitsu-otn-otucn-interfaces.yang:36.5: warning(1015): import not used Warning: Module 'fujitsu-if-type' not used fujitsu-otn-otucn-interfaces.yang:40.5: warning(1015): import not used Warning: Module 'fujitsu-gcc' not used fujitsu-otn-otucn-interfaces.yang:44.4: warning(1015): import not used Error: 'fujitsu-otn-otucn-interfaces-dev.prod.yang' import of module 'fujitsu-otn-otucn-interfaces' failed fujitsu-otn-otucn-interfaces-dev.prod.yang:14.5: error(281): extra node Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:rate' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:direction' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:list-gcc/otucn:gccType' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:list-gcc/otucn:protocol' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:list-gcc/otucn:gccEnabled' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:auto-rx' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:auto-tx' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:standard/otucn:ansi' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:vstimer' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:actual-vstimer' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:loopback' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:admin-status' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:degthr' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:type' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:location' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:standard/otucn:itu/otucn:tti-itu/otucn:tim-det-mode' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:standard/otucn:itu/otucn:tti-itu/otucn:exp-tti/otucn:op-spec' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found Error: object 'otucn' not found in path '/if:interfaces/if:interface/otucn:otucn/otucn:circuit-id' fujitsu-otn-otucn-interfaces-dev.prod.yang:196.3: error(251): definition segment not found |
| fujitsu-otn-otucn-interfaces@2015-05-12.yang | FAILED | fujitsu-if-type@2019-05-16.yang:5: warning: imported module "ietf-interfaces" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn-otucn-interfaces@2015-05-12.yang --lint 2>&1": fujitsu-otn-otucn-interfaces@2015-05-12.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otucn-interfaces@2015-05-12.yang:80: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-otucn-interfaces@2015-05-12.yang:115: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-otucn-interfaces@2015-05-12.yang:127: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-otucn-interfaces@2015-05-12.yang:159: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-otucn-interfaces@2015-05-12.yang:185: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-otucn-interfaces@2015-05-12.yang:186: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-otucn-interfaces@2015-05-12.yang:191: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-otn-otucn-interfaces@2015-05-12.yang 2>&1": Error: 'fujitsu-otn-otucn-interfaces@2015-05-12.yang' import of module 'fujitsu-state-timer' failed fujitsu-otn-otucn-interfaces@2015-05-12.yang:9.3: error(236): module not found Error: 'fujitsu-otn-otucn-interfaces@2015-05-12.yang' import of module 'fujitsu-entity-states' failed fujitsu-otn-otucn-interfaces@2015-05-12.yang:12.3: error(236): module not found Error: 'fujitsu-otn-otucn-interfaces@2015-05-12.yang' import of module 'fujitsu-entity-maintenance-loopback' failed fujitsu-otn-otucn-interfaces@2015-05-12.yang:15.3: error(236): module not found Error: 'fujitsu-otn-otucn-interfaces@2015-05-12.yang' import of module 'fujitsu-if-type' failed fujitsu-otn-otucn-interfaces@2015-05-12.yang:18.3: error(236): module not found Error: 'fujitsu-otn-otucn-interfaces@2015-05-12.yang' import of module 'fujitsu-gcc' failed fujitsu-otn-otucn-interfaces@2015-05-12.yang:21.3: error(236): module not found Error: 'fujitsu-otn-otucn-interfaces@2015-05-12.yang' import of module 'fujitsu-otn' failed fujitsu-otn-otucn-interfaces@2015-05-12.yang:24.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-otn-otucn-interfaces@2015-05-12.yang:111.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-otn-otucn-interfaces@2015-05-12.yang:112.5: error(250): definition not found Error: grouping definition for 'otn:tti-choice' not found in module fujitsu-otn fujitsu-otn-otucn-interfaces@2015-05-12.yang:118.5: error(250): definition not found Error: grouping definition for 'st:state-timer' not found in module fujitsu-state-timer fujitsu-otn-otucn-interfaces@2015-05-12.yang:166.7: error(250): definition not found Error: grouping definition for 'fujitsuGcc:gcc-group' not found in module fujitsu-gcc fujitsu-otn-otucn-interfaces@2015-05-12.yang:180.9: error(250): definition not found Error: grouping definition for 'fujitsu-loopback:maint-loopback' not found in module fujitsu-entity-maintenance-loopback fujitsu-otn-otucn-interfaces@2015-05-12.yang:182.7: error(250): definition not found Error: grouping definition for 'st:state-timer' not found in module fujitsu-state-timer fujitsu-otn-otucn-interfaces@2015-05-12.yang:192.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-otn-otucn-interfaces@2015-05-12.yang:111.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-otn-otucn-interfaces@2015-05-12.yang:112.5: error(250): definition not found Error: grouping 'tti-choice' not found fujitsu-otn-otucn-interfaces@2015-05-12.yang:118.5: error(250): definition not found Error: grouping 'state-timer' not found fujitsu-otn-otucn-interfaces@2015-05-12.yang:166.7: error(250): definition not found Error: object 'oper-status' not found in module fujitsu-otn-otucn-interfaces in Xpath target oper-status fujitsu-otn-otucn-interfaces@2015-05-12.yang:171.7: error(250): definition not found Error: refinement node 'oper-status' not found in grouping 'otucn-attributes' fujitsu-otn-otucn-interfaces@2015-05-12.yang:172.9: error(366): missing refine target Error: grouping 'gcc-group' not found fujitsu-otn-otucn-interfaces@2015-05-12.yang:180.9: error(250): definition not found Error: grouping 'maint-loopback' not found fujitsu-otn-otucn-interfaces@2015-05-12.yang:182.7: error(250): definition not found Error: grouping 'state-timer' not found fujitsu-otn-otucn-interfaces@2015-05-12.yang:192.7: error(250): definition not found Error: object 'gccType' not found in module fujitsu-otn-otucn-interfaces in Xpath target gccType fujitsu-otn-otucn-interfaces@2015-05-12.yang:177.9: error(250): definition not found Error: invalid identifier in key for list 'list-gcc' (gccType) fujitsu-otn-otucn-interfaces@2015-05-12.yang:177.9: error(250): definition not found Error: object 'gccType' not found in module fujitsu-otn-otucn-interfaces in Xpath target gccType fujitsu-otn-otucn-interfaces@2015-05-12.yang:176.7: error(250): definition not found Error: invalid identifier in key for list 'list-gcc' (gccType) fujitsu-otn-otucn-interfaces@2015-05-12.yang:176.7: error(250): definition not found Warning: compare value 'fjift:fujitsuOtuc' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'fjift:fujitsuOtuc' fujitsu-otn-otucn-interfaces@2015-05-12.yang: line 161: warning(1052): XPath compare value invalid for YANG type |
||
| fujitsu-otn@2015-08-13.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-otn@2015-08-13.yang --lint 2>&1": fujitsu-otn@2015-08-13.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn@2015-08-13.yang:41: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn@2015-08-13.yang:50: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn@2015-08-13.yang:59: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn@2015-08-13.yang:68: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn@2015-08-13.yang:119: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn@2015-08-13.yang:137: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn@2015-08-13.yang:145: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn@2015-08-13.yang:166: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn@2015-08-13.yang:201: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn@2015-08-13.yang:209: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-otn@2015-08-13.yang:221: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-otn@2015-08-13.yang 2>&1": Error: 'fujitsu-otn@2015-08-13.yang' import of module 'fujitsu-notifications' failed fujitsu-otn@2015-08-13.yang:5.3: error(236): module not found Error: 'fujitsu-otn@2015-08-13.yang' import of module 'fujitsu-notification-types' failed fujitsu-otn@2015-08-13.yang:8.3: error(236): module not found Error: Module for prefix 'notifications' not found fujitsu-otn@2015-08-13.yang:204.10: error(236): module not found Error: object 'event-notification' not found in module fujitsu-otn in Xpath target /notifications:event-notification fujitsu-otn@2015-08-13.yang:201.3: error(250): definition not found Warning: Module 'fujitsu-notification-types' not used fujitsu-otn@2015-08-13.yang:8.3: warning(1015): import not used |
|||
| fujitsu-performance-monitoring-dev@2018-01-29.yang | FAILED | fujitsu-performance-monitoring-dev.prod.yang:49:21: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:50:50: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:50:54: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:50:58: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:50:62: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:51:23: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:51:27: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:51:31: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:51:35: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:51:39: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:52:19: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:52:23: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:52:27: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:52:31: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:52:35: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:53:19: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:53:23: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:53:27: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:53:31: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:53:35: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:53:39: warning: illegal character after \ |
fujitsu-performance-monitoring-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-performance-monitoring-dev.prod.yang:49: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:50: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:51: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:52: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:53: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring.yang:5: warning: imported module "ietf-yang-types" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-performance-monitoring-dev.prod.yang --lint 2>&1": fujitsu-performance-monitoring-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-performance-monitoring-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-performance-monitoring-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-performance-monitoring-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-performance-monitoring-dev.prod.yang:13: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-dev.prod.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-dev.prod.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-dev.prod.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-dev.prod.yang:49: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:50: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:51: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:52: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-performance-monitoring-dev.prod.yang:53: warning: the escape sequence "\S" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-performance-monitoring-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\S'. (Line number 49.) libyang err : Parsing module "fujitsu-performance-monitoring-dev.prod" failed. |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-performance-monitoring-dev.prod.yang 2>&1": Error: 'fujitsu-performance-monitoring-dev.prod.yang' import of module 'tailf-common' failed fujitsu-performance-monitoring-dev.prod.yang:5.5: error(236): module not found Warning: Module 'ietf-yang-types' not used fujitsu-performance-monitoring.yang:5.5: warning(1015): import not used Warning: Module 'tailf-common' not used fujitsu-performance-monitoring-dev.prod.yang:5.5: warning(1015): import not used |
| fujitsu-performance-monitoring-typedefs@2018-01-11.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-performance-monitoring-typedefs@2018-01-11.yang --lint 2>&1": fujitsu-performance-monitoring-typedefs@2018-01-11.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:115: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:128: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:158: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:179: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:206: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:207: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:210: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:213: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:218: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:219: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:220: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:225: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:234: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:235: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:250: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:252: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:253: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:255: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:257: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:258: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:263: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:264: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:266: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:268: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:271: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:272: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:273: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:279: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:283: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:285: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:293: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:295: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:298: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:301: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:304: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:312: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:315: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:321: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:322: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:326: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:330: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:364: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:365: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs@2018-01-11.yang:369: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs@2018-01-11.yang:373: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement |
||||
| fujitsu-performance-monitoring@2018-01-11.yang | FAILED | fujitsu-performance-monitoring@2018-01-11.yang:5: warning: imported module "ietf-yang-types" not used | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-performance-monitoring@2018-01-11.yang --lint 2>&1": fujitsu-performance-monitoring@2018-01-11.yang:5: warning: imported module "ietf-yang-types" not used fujitsu-performance-monitoring@2018-01-11.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring@2018-01-11.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring@2018-01-11.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring@2018-01-11.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring@2018-01-11.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring@2018-01-11.yang:57: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:61: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:64: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:65: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:73: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:76: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:77: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:85: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:88: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:89: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:95: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:98: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:99: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:105: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:108: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:109: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:121: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:125: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:128: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:129: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:137: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:141: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:144: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:145: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:149: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:150: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:165: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring@2018-01-11.yang:169: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring@2018-01-11.yang:175: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring@2018-01-11.yang:188: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring@2018-01-11.yang:194: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-performance-monitoring@2018-01-11.yang 2>&1": Error: 'fujitsu-performance-monitoring@2018-01-11.yang' import of module 'fujitsu-notifications' failed fujitsu-performance-monitoring@2018-01-11.yang:8.3: error(236): module not found Error: 'fujitsu-performance-monitoring@2018-01-11.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-performance-monitoring@2018-01-11.yang:11.3: error(236): module not found Error: grouping definition for 'pmtypedefs:pm-oper-data' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:69.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-oper-data' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:81.9: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-oper-data' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:91.11: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-oper-data' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:101.13: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-oper-data' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:111.15: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-oper-data' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:131.7: error(250): definition not found Error: typedef definition for 'pmtypedefs:pm-pg-type' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:145.14: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-oper-data' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:152.7: error(250): definition not found Error: typedef definition for 'pmtypedefs:pm-time-period' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:166.14: error(250): definition not found Error: typedef definition for 'pmtypedefs:pm-history' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:170.14: error(250): definition not found Error: grouping definition for 'notifications:common-event-parameters' not found in module fujitsu-notifications fujitsu-performance-monitoring@2018-01-11.yang:183.5: error(250): definition not found Error: typedef definition for 'pmtypedefs:pm-data-type' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:185.12: error(250): definition not found Error: typedef definition for 'pmtypedefs:pm-data-type' not found in module fujitsu-performance-monitoring-typedefs fujitsu-performance-monitoring@2018-01-11.yang:191.12: error(250): definition not found Error: grouping 'pm-oper-data' not found fujitsu-performance-monitoring@2018-01-11.yang:69.7: error(250): definition not found Error: grouping 'pm-oper-data' not found fujitsu-performance-monitoring@2018-01-11.yang:81.9: error(250): definition not found Error: grouping 'pm-oper-data' not found fujitsu-performance-monitoring@2018-01-11.yang:91.11: error(250): definition not found Error: grouping 'pm-oper-data' not found fujitsu-performance-monitoring@2018-01-11.yang:101.13: error(250): definition not found Error: grouping 'pm-oper-data' not found fujitsu-performance-monitoring@2018-01-11.yang:111.15: error(250): definition not found Error: grouping 'pm-oper-data' not found fujitsu-performance-monitoring@2018-01-11.yang:131.7: error(250): definition not found Error: grouping 'pm-oper-data' not found fujitsu-performance-monitoring@2018-01-11.yang:152.7: error(250): definition not found Error: grouping 'common-event-parameters' not found fujitsu-performance-monitoring@2018-01-11.yang:183.5: error(250): definition not found Error: object 'pg-type' not found in module fujitsu-performance-monitoring in Xpath target pg-type fujitsu-performance-monitoring@2018-01-11.yang:141.7: error(250): definition not found Error: invalid identifier in key for list 'protection' (pg-type) fujitsu-performance-monitoring@2018-01-11.yang:141.7: error(250): definition not found Warning: Module 'ietf-yang-types' not used fujitsu-performance-monitoring@2018-01-11.yang:5.3: warning(1015): import not used |
||
| fujitsu-physical-inventory@2015-04-10.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-physical-inventory@2015-04-10.yang --lint 2>&1": fujitsu-physical-inventory@2015-04-10.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-physical-inventory@2015-04-10.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement |
||||
| fujitsu-pm-types@2018-03-27.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-pm-types@2018-03-27.yang --lint 2>&1": fujitsu-pm-types@2018-03-27.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:79: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types@2018-03-27.yang:84: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:88: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:92: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:96: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:100: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:104: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:108: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:112: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:116: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:120: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:124: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:128: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:132: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:136: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:140: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:144: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:148: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:152: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:156: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:160: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:164: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:168: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:172: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:176: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:180: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:184: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:188: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:192: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:196: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:200: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:204: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:208: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:212: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:216: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:220: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:224: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:228: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:232: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:236: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:240: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:244: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:248: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:252: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:256: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:260: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:264: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:268: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:272: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:276: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:280: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:284: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:288: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:292: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:296: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:300: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:304: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:308: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:312: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:316: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:320: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:324: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:328: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:332: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:336: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:340: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:344: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:348: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:352: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:356: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:360: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:364: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:368: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:372: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:376: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:380: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:384: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:388: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:392: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:396: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:400: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:404: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:408: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:412: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:416: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:420: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:424: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:428: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:432: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:436: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:440: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:444: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:448: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:452: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:456: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:460: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:464: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:468: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:472: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:476: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:480: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:484: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:488: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:492: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:496: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:500: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:504: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:508: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:512: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:516: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:520: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:524: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:528: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:532: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:536: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:540: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:544: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:548: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:552: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:556: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:560: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:564: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:568: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:572: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:576: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:580: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:584: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:588: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:592: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:596: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:600: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:604: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:608: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:612: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:616: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:620: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:624: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:628: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:632: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:636: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:640: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:644: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:648: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:652: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:656: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:660: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:664: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:668: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:672: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:676: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:680: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:684: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:688: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:692: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:696: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:700: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:704: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:708: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:712: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:716: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:720: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:724: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:728: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:732: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:736: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:740: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:744: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:748: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:752: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:756: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:760: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:764: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:768: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:772: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:776: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:780: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:784: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:788: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:792: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:796: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:800: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:804: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:808: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:812: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:816: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:820: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:824: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:828: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:832: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:836: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:840: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:844: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:848: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:852: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:856: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:860: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:864: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:868: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:872: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:876: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:880: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:884: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:888: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:892: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:896: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:900: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:904: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:908: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:912: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:916: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:920: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:924: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:928: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:932: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:936: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:940: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:944: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:948: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:952: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:956: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:960: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:964: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:968: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:972: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:976: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:980: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:984: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:988: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:992: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:996: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1000: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1004: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1008: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1012: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1016: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1020: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1024: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1028: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1032: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1036: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1040: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1044: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1048: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1052: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1056: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1060: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1064: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1068: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1072: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1076: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1080: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1084: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1088: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1092: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1096: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1100: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1104: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1108: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1112: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1116: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1120: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1124: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1128: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1132: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1136: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1140: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1144: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1148: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1152: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1156: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1160: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1164: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1168: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1172: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1176: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1180: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1184: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1188: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1192: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1196: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1200: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1204: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1208: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1212: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1216: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1220: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1224: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types@2018-03-27.yang:1228: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-pm-types@2018-03-27.yang 2>&1": Error: 'fujitsu-pm-types@2018-03-27.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-pm-types@2018-03-27.yang:5.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:84.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:100.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:104.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:120.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:132.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:148.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:152.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:164.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:176.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:180.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:192.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:204.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:208.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:220.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:232.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:236.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:248.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:260.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:264.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:276.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:288.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:300.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:312.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:316.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:320.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:324.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:328.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:332.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:336.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:340.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:344.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:348.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:352.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:356.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:360.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:364.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:368.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:372.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:376.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:380.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:384.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:388.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:392.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:396.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:400.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:404.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:408.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:412.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:416.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:420.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:424.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:428.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:432.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:436.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:440.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:444.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:448.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:452.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:456.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:460.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:464.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:468.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:472.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:484.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:488.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:492.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:496.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:500.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:504.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:508.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:512.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:516.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:520.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:524.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:528.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:544.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:560.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:576.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:592.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:608.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:624.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:640.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:656.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:672.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:688.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:692.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:696.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:700.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:704.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:708.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:712.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:716.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:720.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:724.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:728.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:732.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:736.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:740.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:744.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:748.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:752.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:756.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:760.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:764.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:768.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:772.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:776.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:780.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:784.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:788.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:792.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:796.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:800.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:804.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:808.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:812.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:816.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:820.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:824.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:828.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:832.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:836.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:840.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:844.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:848.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:852.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:856.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:860.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:864.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:868.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:872.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:876.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:880.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:884.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:888.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:892.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:896.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:900.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:904.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:908.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:912.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:916.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:920.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:924.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:928.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:932.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:936.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:940.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:944.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:948.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:952.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:956.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:960.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:964.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:968.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:972.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:976.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:980.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:984.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:988.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:992.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:996.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1000.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1004.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1008.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1012.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1016.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1020.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1024.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1028.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1032.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1036.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1040.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1044.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1048.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1052.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1056.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1060.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1064.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1068.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1072.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1076.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1080.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1084.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1088.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1092.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1096.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1100.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1104.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1108.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1112.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1116.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1120.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1124.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1128.3: error(236): module not found Load module 'fujitsu-performance-monitoring-typedefs' failed (module not found) Error: failure importing module 'fujitsu-performance-monitoring-typedefs' fujitsu-pm-types@2018-03-27.yang:1132.3: error(236): module not found |
|||
| fujitsu-port@2018-04-03.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-port@2018-04-03.yang --lint 2>&1": fujitsu-port@2018-04-03.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-04-03.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-04-03.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-04-03.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-04-03.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-04-03.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-04-03.yang:75: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-port@2018-04-03.yang:122: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-port@2018-04-03.yang:125: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-port@2018-04-03.yang 2>&1": Error: 'fujitsu-port@2018-04-03.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-port@2018-04-03.yang:5.3: error(236): module not found Error: 'fujitsu-port@2018-04-03.yang' import of module 'fujitsu-entity-states' failed fujitsu-port@2018-04-03.yang:8.3: error(236): module not found Error: 'fujitsu-port@2018-04-03.yang' import of module 'fujitsu-subport' failed fujitsu-port@2018-04-03.yang:11.3: error(236): module not found Error: 'fujitsu-port@2018-04-03.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-port@2018-04-03.yang:14.3: error(236): module not found Warning: revision with same date on line 28 fujitsu-port@2018-04-03.yang:33.3: warning(1054): Revision date has already been used Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-port@2018-04-03.yang:114.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-port@2018-04-03.yang:119.5: error(250): definition not found Error: grouping definition for 'physical-inventory:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-port@2018-04-03.yang:126.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-port@2018-04-03.yang:129.5: error(250): definition not found Error: grouping definition for 'subport:subPort' not found in module fujitsu-subport fujitsu-port@2018-04-03.yang:148.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-port@2018-04-03.yang:114.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-port@2018-04-03.yang:119.5: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-port@2018-04-03.yang:126.7: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-port@2018-04-03.yang:129.5: error(250): definition not found Error: grouping 'subPort' not found fujitsu-port@2018-04-03.yang:148.7: error(250): definition not found Error: object 'subPortID' not found in module fujitsu-port in Xpath target subPortID fujitsu-port@2018-04-03.yang:147.7: error(250): definition not found Error: invalid identifier in key for list 'subport' (subPortID) fujitsu-port@2018-04-03.yang:147.7: error(250): definition not found |
|||
| fujitsu-ppp-interface@2017-05-08.yang | FAILED | fujitsu-ppp-interface.yang:116: warning: "ianaift" looks like a prefix but is not defined | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ppp-interface.yang --lint 2>&1": fujitsu-ppp-interface.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ppp-interface.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ppp-interface.yang:106: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ppp-interface.yang:114: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ppp-interface.yang:116: warning: "ianaift" looks like a prefix but is not defined fujitsu-ppp-interface.yang:125: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ppp-interface.yang:150: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ppp-interface.yang:154: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: compare value 'ianaift:ppp' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:ppp' fujitsu-ppp-interface.yang: line 116: warning(1052): XPath compare value invalid for YANG type Warning: compare value 'ianaift:ppp' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:ppp' fujitsu-ppp-interface.yang: line 152: warning(1052): XPath compare value invalid for YANG type |
||
| fujitsu-protocols@2016-04-01.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-protocols@2016-04-01.yang --lint 2>&1": fujitsu-protocols@2016-04-01.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
||||
| fujitsu-radius-client@2016-10-27.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-radius-client@2016-10-27.yang 2>&1": ./tailf-aaa@2023-03-06.yang:103: error: unexpected keyword 'tailf:internal-dp' |
/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security@2018-07-18.yang:9: warning: imported module "tailf-aaa" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-radius-client@2016-10-27.yang --lint 2>&1": fujitsu-radius-client@2016-10-27.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-radius-client@2016-10-27.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-radius-client@2016-10-27.yang:81: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-radius-client@2016-10-27.yang:86: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-radius-client@2016-10-27.yang:89: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-radius-client@2016-10-27.yang:177: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-radius-client@2016-10-27.yang:180: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-radius-client@2016-10-27.yang:185: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-radius-client@2016-10-27.yang:188: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-radius-client@2016-10-27.yang:267: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-radius-client@2016-10-27.yang:270: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-radius-client@2016-10-27.yang 2>&1": Error: 'fujitsu-radius-client@2016-10-27.yang' import of module 'fujitsu-user-security' failed fujitsu-radius-client@2016-10-27.yang:8.3: error(236): module not found Error: object 'security' not found in module fujitsu-radius-client in Xpath target /secu:security fujitsu-radius-client@2016-10-27.yang:81.3: error(250): definition not found |
|
| fujitsu-routing@2018-01-22.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-routing@2018-01-22.yang 2>&1": fujitsu-routing@2018-01-22.yang:36: error: node 'routing-instance' not found fujitsu-routing@2018-01-22.yang:36: error: node 'ribs' not found fujitsu-routing@2018-01-22.yang:36: error: node 'rib' not found fujitsu-routing@2018-01-22.yang:36: error: node 'routes' not found fujitsu-routing@2018-01-22.yang:36: error: node 'route' not found fujitsu-routing@2018-01-22.yang:36: error: node 'next-hop' not found fujitsu-routing@2018-01-22.yang:36: error: node 'next-hop-options' not found fujitsu-routing@2018-01-22.yang:36: error: node 'simple-next-hop' not found fujitsu-routing@2018-01-22.yang:39: error: the node 'routing-instance' from module 'ietf-routing' (in node 'routing-state' from 'ietf-routing') is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-routing@2018-01-22.yang 2>&1": fujitsu-routing@2018-01-22.yang:36: error: node ietf-routing::routing-instance is not found fujitsu-routing@2018-01-22.yang:39: error: "ietf-routing:routing-instance" in the path for outgoing-interface at fujitsu-routing@2018-01-22.yang:37 is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-routing@2018-01-22.yang --lint 2>&1": fujitsu-routing@2018-01-22.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-routing@2018-01-22.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-routing@2018-01-22.yang:36: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-routing@2018-01-22.yang:36: error: node ietf-routing::routing-instance is not found fujitsu-routing@2018-01-22.yang:39: error: "ietf-routing:routing-instance" in the path for outgoing-interface at fujitsu-routing@2018-01-22.yang:37 is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/fujitsu-routing@2018-01-22.yang 2>&1": libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop" from module "fujitsu-routing" was not found. (Path "/fujitsu-routing:{augment='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-routing@2018-01-22.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop' fujitsu-routing@2018-01-22.yang:36.3: error(251): definition segment not found |
| fujitsu-shelf@2018-04-03.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-shelf@2018-04-03.yang --lint 2>&1": fujitsu-shelf@2018-04-03.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-shelf@2018-04-03.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-shelf@2018-04-03.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-shelf@2018-04-03.yang:72: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-shelf@2018-04-03.yang:116: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf@2018-04-03.yang:121: error: keyword "units" not in canonical order (see RFC 6020, Section 12) fujitsu-shelf@2018-04-03.yang:123: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf@2018-04-03.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf@2018-04-03.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf@2018-04-03.yang:151: error: keyword "key" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-shelf@2018-04-03.yang 2>&1": Error: 'fujitsu-shelf@2018-04-03.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-shelf@2018-04-03.yang:5.3: error(236): module not found Error: 'fujitsu-shelf@2018-04-03.yang' import of module 'fujitsu-slot' failed fujitsu-shelf@2018-04-03.yang:8.3: error(236): module not found Error: 'fujitsu-shelf@2018-04-03.yang' import of module 'fujitsu-entity-states' failed fujitsu-shelf@2018-04-03.yang:11.3: error(236): module not found Error: 'fujitsu-shelf@2018-04-03.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-shelf@2018-04-03.yang:14.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-shelf@2018-04-03.yang:64.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-shelf@2018-04-03.yang:69.5: error(250): definition not found Error: grouping definition for 'physical-inventory:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-shelf@2018-04-03.yang:111.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-shelf@2018-04-03.yang:147.5: error(250): definition not found Error: grouping definition for 'slot:Slot' not found in module fujitsu-slot fujitsu-shelf@2018-04-03.yang:152.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-shelf@2018-04-03.yang:64.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-shelf@2018-04-03.yang:69.5: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-shelf@2018-04-03.yang:111.7: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-shelf@2018-04-03.yang:147.5: error(250): definition not found Error: grouping 'Slot' not found fujitsu-shelf@2018-04-03.yang:152.7: error(250): definition not found Error: object 'slotID' not found in module fujitsu-shelf in Xpath target slotID fujitsu-shelf@2018-04-03.yang:151.7: error(250): definition not found Error: invalid identifier in key for list 'slot' (slotID) fujitsu-shelf@2018-04-03.yang:151.7: error(250): definition not found |
|||
| fujitsu-slot@2018-04-03.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-slot@2018-04-03.yang --lint 2>&1": fujitsu-slot@2018-04-03.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-04-03.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-04-03.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-04-03.yang:79: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-slot@2018-04-03.yang:103: error: keyword "key" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-slot@2018-04-03.yang 2>&1": Error: 'fujitsu-slot@2018-04-03.yang' import of module 'fujitsu-subslot' failed fujitsu-slot@2018-04-03.yang:5.3: error(236): module not found Error: 'fujitsu-slot@2018-04-03.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-slot@2018-04-03.yang:8.3: error(236): module not found Error: 'fujitsu-slot@2018-04-03.yang' import of module 'fujitsu-entity-states' failed fujitsu-slot@2018-04-03.yang:11.3: error(236): module not found Error: 'fujitsu-slot@2018-04-03.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-slot@2018-04-03.yang:14.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-slot@2018-04-03.yang:71.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-slot@2018-04-03.yang:76.5: error(250): definition not found Error: grouping definition for 'physical-inventory:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-slot@2018-04-03.yang:94.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-slot@2018-04-03.yang:99.5: error(250): definition not found Error: grouping definition for 'subslot:subslot' not found in module fujitsu-subslot fujitsu-slot@2018-04-03.yang:104.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-slot@2018-04-03.yang:71.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-slot@2018-04-03.yang:76.5: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-slot@2018-04-03.yang:94.7: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-slot@2018-04-03.yang:99.5: error(250): definition not found Error: grouping 'subslot' not found fujitsu-slot@2018-04-03.yang:104.7: error(250): definition not found Error: object 'subslotID' not found in module fujitsu-slot in Xpath target subslotID fujitsu-slot@2018-04-03.yang:103.7: error(250): definition not found Error: invalid identifier in key for list 'subslot' (subslotID) fujitsu-slot@2018-04-03.yang:103.7: error(250): definition not found |
|||
| fujitsu-ssh-host-key@2015-10-14.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-ssh-host-key@2015-10-14.yang --lint 2>&1": fujitsu-ssh-host-key@2015-10-14.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ssh-host-key@2015-10-14.yang:26: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-ssh-host-key@2015-10-14.yang:36: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-ssh-host-key@2015-10-14.yang:54: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ssh-host-key@2015-10-14.yang:57: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
||||
| fujitsu-state-timer@2015-04-01.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-state-timer@2015-04-01.yang --lint 2>&1": fujitsu-state-timer@2015-04-01.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-state-timer@2015-04-01.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement |
||||
| fujitsu-subport@2018-04-03.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-subport@2018-04-03.yang --lint 2>&1": fujitsu-subport@2018-04-03.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subport@2018-04-03.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subport@2018-04-03.yang:55: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-subport@2018-04-03.yang:83: error: keyword "default" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-subport@2018-04-03.yang 2>&1": Error: 'fujitsu-subport@2018-04-03.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-subport@2018-04-03.yang:5.3: error(236): module not found Error: 'fujitsu-subport@2018-04-03.yang' import of module 'fujitsu-entity-states' failed fujitsu-subport@2018-04-03.yang:8.3: error(236): module not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-subport@2018-04-03.yang:74.5: error(250): definition not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-subport@2018-04-03.yang:75.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-subport@2018-04-03.yang:80.5: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-subport@2018-04-03.yang:74.5: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-subport@2018-04-03.yang:75.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-subport@2018-04-03.yang:80.5: error(250): definition not found |
|||
| fujitsu-subslot@2018-04-03.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-subslot@2018-04-03.yang --lint 2>&1": fujitsu-subslot@2018-04-03.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subslot@2018-04-03.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subslot@2018-04-03.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subslot@2018-04-03.yang:73: error: keyword "default" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-subslot@2018-04-03.yang 2>&1": Error: 'fujitsu-subslot@2018-04-03.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-subslot@2018-04-03.yang:5.3: error(236): module not found Error: 'fujitsu-subslot@2018-04-03.yang' import of module 'fujitsu-port' failed fujitsu-subslot@2018-04-03.yang:8.3: error(236): module not found Error: 'fujitsu-subslot@2018-04-03.yang' import of module 'fujitsu-entity-states' failed fujitsu-subslot@2018-04-03.yang:11.3: error(236): module not found Error: 'fujitsu-subslot@2018-04-03.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-subslot@2018-04-03.yang:14.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-subslot@2018-04-03.yang:65.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-subslot@2018-04-03.yang:70.5: error(250): definition not found Error: grouping definition for 'physical-inventory:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-subslot@2018-04-03.yang:77.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-subslot@2018-04-03.yang:82.5: error(250): definition not found Error: grouping definition for 'port:Port' not found in module fujitsu-port fujitsu-subslot@2018-04-03.yang:85.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-subslot@2018-04-03.yang:65.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-subslot@2018-04-03.yang:70.5: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-subslot@2018-04-03.yang:77.7: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-subslot@2018-04-03.yang:82.5: error(250): definition not found Error: grouping 'Port' not found fujitsu-subslot@2018-04-03.yang:85.7: error(250): definition not found Error: object 'portID' not found in module fujitsu-subslot in Xpath target portID fujitsu-subslot@2018-04-03.yang:84.7: error(250): definition not found Error: invalid identifier in key for list 'port' (portID) fujitsu-subslot@2018-04-03.yang:84.7: error(250): definition not found |
|||
| fujitsu-swdl@2018-06-22.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-swdl@2018-06-22.yang --lint 2>&1": fujitsu-swdl@2018-06-22.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:64: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:68: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl@2018-06-22.yang:100: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-swdl@2018-06-22.yang:258: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-swdl@2018-06-22.yang:315: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-swdl@2018-06-22.yang:347: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-swdl@2018-06-22.yang:391: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-swdl@2018-06-22.yang:392: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-swdl@2018-06-22.yang:400: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-swdl@2018-06-22.yang:401: error: keyword "config" not in canonical order (see RFC 6020, Section 12) |
||||
| fujitsu-system-dev@2017-03-20.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-system-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:30: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:36: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:38: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:41: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security.yang:12: error: module 'tailf-aaa' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security.yang:308: error: the node 'user' from module 'tailf-aaa' is not found |
fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:9: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:21: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:25: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:41: warning: imported module "fujitsu-license" not used fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security.yang:12: warning: imported module "tailf-aaa" not used fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-system-dev.prod.yang --lint 2>&1": fujitsu-system-dev.prod.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-dev.prod.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-system-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\^'. (Line number 157.) libyang err : Parsing module "fujitsu-user-security-typedefs" failed. libyang err : Loading "fujitsu-user-security-typedefs" module failed. libyang err : Parsing module "fujitsu-user-security" failed. libyang err : Loading "fujitsu-user-security" module failed. libyang err : Parsing module "fujitsu-security-certificates" failed. libyang err : Loading "fujitsu-security-certificates" module failed. libyang err : Parsing module "fujitsu-system" failed. libyang err : Loading "fujitsu-system" module failed. libyang err : Parsing module "fujitsu-system-dev.prod" failed. |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-system-dev.prod.yang 2>&1": Error: 'fujitsu-system.yang' import of module 'tailf-common' failed fujitsu-system.yang:5.3: error(236): module not found Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:40.5: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:13.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-common' failed fujitsu-user-security.yang:9.3: error(236): module not found Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:12.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:259.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:260.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:261.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:267.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:269.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:273.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:275.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:285.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:287.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:291.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:293.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:308.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:320.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:321.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:322.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:323.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:337.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:338.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:344.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:345.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:357.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:358.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:359.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:362.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:373.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:374.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:380.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:386.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:387.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:389.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:393.11: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:96.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:12.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:4.3: error(236): module not found Warning: no revision statements for module 'fujitsu-security-certificates' Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:7.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:53.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:28.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:31.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:35.3: error(236): module not found Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-system.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-system.yang:38.3: error(332): imported module has errors Warning: revision dates not in descending order fujitsu-license.yang:38.6: warning(1035): bad revision-stmt order Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-system.yang:862.4: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1628.17: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1768.16: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:663.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:684.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:741.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:804.10: error(236): module not found Error: grouping 'ains-prov-keywords' not found fujitsu-system.yang:862.4: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:866.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:867.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:868.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:915.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1481.14: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1482.14: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1732.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1733.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1734.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1735.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1736.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1737.12: error(236): module not found Warning: top-level NP container 'system' is mandatory fujitsu-system.yang:874.3: warning(1048): top-level object is mandatory Error: Module for prefix 'secu' not found fujitsu-system.yang:1661.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:9.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:21.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:25.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:41.3: warning(1015): import not used Error: 'fujitsu-system-dev.prod.yang' import of module 'fujitsu-system' failed fujitsu-system-dev.prod.yang:5.5: error(236): module not found Error: object 'init-filter-timer' not found in module fujitsu-system-dev.prod in Xpath target /system:init-filter-timer fujitsu-system-dev.prod.yang:47.2: error(250): definition not found Error: object 'system' not found in module fujitsu-system-dev.prod in Xpath target /system:system/system:internal-rstp-enabled fujitsu-system-dev.prod.yang:47.2: error(250): definition not found |
| fujitsu-system-zeroization@2017-05-08.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-system-zeroization@2017-05-08.yang --lint 2>&1": fujitsu-system-zeroization@2017-05-08.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-zeroization@2017-05-08.yang:33: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-system-zeroization@2017-05-08.yang:36: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
||||
| fujitsu-system@2018-09-19.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-system.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:30: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:36: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:38: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:41: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security.yang:12: error: module 'tailf-aaa' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security.yang:308: error: the node 'user' from module 'tailf-aaa' is not found |
fujitsu-system.yang:9: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:21: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:25: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:41: warning: imported module "fujitsu-license" not used fujitsu-ains-keywords.yang:5: warning: imported module "tailf-common" not used fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:38: warning: the revision statements are not given in reverse chronological order fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security.yang:12: warning: imported module "tailf-aaa" not used fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-system.yang --lint 2>&1": fujitsu-system.yang:9: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:21: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:25: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:41: warning: imported module "fujitsu-license" not used fujitsu-system.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:68: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:74: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:79: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:84: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:89: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:94: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:99: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:105: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:110: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:115: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:120: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:125: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:130: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:138: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:143: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:148: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:154: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:160: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:166: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:171: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:176: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:182: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:187: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:193: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:198: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:203: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:208: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:213: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:218: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:223: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:228: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:234: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:239: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:244: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:248: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:252: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:256: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:261: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:266: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:270: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:274: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:278: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:430: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:447: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:600: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:629: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:658: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:676: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:733: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:798: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:861: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-system.yang:874: error: RFC 8407: 4.10: top-level node system must not be mandatory fujitsu-system.yang:981: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1013: error: keyword "default" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1014: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1479: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1559: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:1599: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1600: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1601: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1602: error: keyword "ordered-by" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1609: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1610: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1611: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1612: error: keyword "ordered-by" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1644: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1656: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1657: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-system.yang:1678: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1679: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1685: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1686: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1730: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1767: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1768: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1797: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1798: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1800: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1809: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1810: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1812: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1818: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1819: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1821: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1831: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:1832: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1834: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1850: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:1853: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:1877: error: keyword "units" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1907: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:1969: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:1970: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:1973: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2005: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2014: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2015: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2035: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2036: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2047: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2048: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2069: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:2070: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:2078: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:2079: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:2090: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2091: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2124: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2130: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-system.yang:2140: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2151: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2178: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-system.yang 2>&1": libyang err : Double-quoted string unknown special character '\^'. (Line number 157.) libyang err : Parsing module "fujitsu-user-security-typedefs" failed. libyang err : Loading "fujitsu-user-security-typedefs" module failed. libyang err : Parsing module "fujitsu-user-security" failed. libyang err : Loading "fujitsu-user-security" module failed. libyang err : Parsing module "fujitsu-security-certificates" failed. libyang err : Loading "fujitsu-security-certificates" module failed. libyang err : Parsing module "fujitsu-system" failed. |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-system.yang 2>&1": Error: 'fujitsu-system.yang' import of module 'tailf-common' failed fujitsu-system.yang:5.3: error(236): module not found Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:10.5: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:40.5: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:13.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-common' failed fujitsu-user-security.yang:9.3: error(236): module not found Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:12.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:259.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:260.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:261.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:267.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:269.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:273.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:275.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:285.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:287.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:291.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:293.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:308.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:320.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:321.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:322.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:323.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:337.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:338.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:344.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:345.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:357.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:358.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:359.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:362.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:373.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:374.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:380.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:386.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:387.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:389.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:393.11: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:96.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:12.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:4.3: error(236): module not found Warning: no revision statements for module 'fujitsu-security-certificates' Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:7.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:53.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:28.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:31.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:35.3: error(236): module not found Error: 'fujitsu-ains-keywords.yang' import of module 'tailf-common' failed fujitsu-ains-keywords.yang:5.3: error(236): module not found Warning: Module 'tailf-common' not used fujitsu-ains-keywords.yang:5.3: warning(1015): import not used Error: 'fujitsu-system.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-system.yang:38.3: error(332): imported module has errors Warning: revision dates not in descending order fujitsu-license.yang:38.6: warning(1035): bad revision-stmt order Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-system.yang:862.4: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1628.17: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1768.16: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:663.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:684.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:741.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:804.10: error(236): module not found Error: grouping 'ains-prov-keywords' not found fujitsu-system.yang:862.4: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:866.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:867.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:868.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:915.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1481.14: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1482.14: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1732.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1733.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1734.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1735.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1736.12: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:1737.12: error(236): module not found Warning: top-level NP container 'system' is mandatory fujitsu-system.yang:874.3: warning(1048): top-level object is mandatory Error: Module for prefix 'secu' not found fujitsu-system.yang:1661.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:9.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:21.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:25.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:41.3: warning(1015): import not used |
| fujitsu-tacacs-plus-client@2017-06-08.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-tacacs-plus-client@2017-06-08.yang 2>&1": ./tailf-aaa@2023-03-06.yang:103: error: unexpected keyword 'tailf:internal-dp' |
/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security@2018-07-18.yang:9: warning: imported module "tailf-aaa" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-tacacs-plus-client@2017-06-08.yang --lint 2>&1": fujitsu-tacacs-plus-client@2017-06-08.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client@2017-06-08.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client@2017-06-08.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client@2017-06-08.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client@2017-06-08.yang:69: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-tacacs-plus-client@2017-06-08.yang:74: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-tacacs-plus-client@2017-06-08.yang:77: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-tacacs-plus-client@2017-06-08.yang:142: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-tacacs-plus-client@2017-06-08.yang:145: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-tacacs-plus-client@2017-06-08.yang:150: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-tacacs-plus-client@2017-06-08.yang:153: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-tacacs-plus-client@2017-06-08.yang:210: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-tacacs-plus-client@2017-06-08.yang:213: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-tacacs-plus-client@2017-06-08.yang 2>&1": Error: 'fujitsu-tacacs-plus-client@2017-06-08.yang' import of module 'fujitsu-user-security' failed fujitsu-tacacs-plus-client@2017-06-08.yang:8.3: error(236): module not found Error: object 'security' not found in module fujitsu-tacacs-plus-client in Xpath target /secu:security fujitsu-tacacs-plus-client@2017-06-08.yang:69.3: error(250): definition not found |
|
| fujitsu-telemetry@2017-01-13.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-telemetry@2017-01-13.yang --lint 2>&1": fujitsu-telemetry@2017-01-13.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-telemetry@2017-01-13.yang:25: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-telemetry@2017-01-13.yang:36: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-telemetry@2017-01-13.yang:39: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
||||
| fujitsu-threshold-crossover-types@2018-02-06.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-threshold-crossover-types@2018-02-06.yang --lint 2>&1": fujitsu-threshold-crossover-types@2018-02-06.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types@2018-02-06.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types@2018-02-06.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types@2018-02-06.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types@2018-02-06.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types@2018-02-06.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-threshold-crossover-types@2018-02-06.yang 2>&1": Error: 'fujitsu-threshold-crossover-types@2018-02-06.yang' import of module 'fujitsu-notifications' failed fujitsu-threshold-crossover-types@2018-02-06.yang:5.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:52.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:58.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:64.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:70.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:76.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:82.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:88.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:94.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:100.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:106.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:112.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:118.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:124.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:130.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:136.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:142.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:148.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:154.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:160.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:166.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:172.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:178.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:184.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:190.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:196.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:202.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:208.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:214.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:220.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:226.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:232.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:238.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:244.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:250.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:256.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:262.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:268.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:274.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:280.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:286.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:292.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:298.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:304.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:310.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:316.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:322.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:328.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:334.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:340.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:346.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:352.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:358.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:364.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:370.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:376.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:382.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:388.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:394.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:400.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:406.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:412.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:418.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:424.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:430.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:436.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:442.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:448.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:454.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:460.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:466.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:472.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:478.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:484.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:490.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:496.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:502.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:508.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:514.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:520.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:526.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:532.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:538.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:544.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:550.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:556.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:562.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:568.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:574.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:580.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:586.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:592.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:598.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:604.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:610.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:616.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:622.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:628.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:634.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:640.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:646.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:652.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:658.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:664.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:670.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:676.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:682.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:688.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:694.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:700.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:706.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:712.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:718.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:724.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:730.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:736.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:742.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:748.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:754.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:760.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:766.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:772.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:778.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:784.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:790.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:796.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:802.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:808.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:814.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:820.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:826.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:832.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:838.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:844.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:850.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:856.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:862.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:868.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:874.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:880.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:886.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:892.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:898.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:904.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:910.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:916.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:922.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:928.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:934.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:940.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:946.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:952.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:958.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:964.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:970.3: error(236): module not found Load module 'fujitsu-notifications' failed (module not found) Error: failure importing module 'fujitsu-notifications' fujitsu-threshold-crossover-types@2018-02-06.yang:976.3: error(236): module not found |
|||
| fujitsu-user-security-dev@2017-08-28.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:30: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:36: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:38: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157:41: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security.yang:12: error: module 'tailf-aaa' not found |
fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security.yang:12: warning: imported module "tailf-aaa" not used fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-user-security-dev.prod.yang --lint 2>&1": fujitsu-user-security-dev.prod.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-dev.prod.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-dev.prod.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\^'. (Line number 157.) libyang err : Parsing module "fujitsu-user-security-typedefs" failed. libyang err : Loading "fujitsu-user-security-typedefs" module failed. libyang err : Parsing module "fujitsu-user-security" failed. libyang err : Loading "fujitsu-user-security" module failed. libyang err : Parsing module "fujitsu-user-security-dev.prod" failed. |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-dev.prod.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-common' failed fujitsu-user-security.yang:9.3: error(236): module not found Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:12.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:259.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:260.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:261.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:267.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:269.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:273.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:275.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:285.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:287.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:291.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:293.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:308.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:320.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:321.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:322.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:323.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:337.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:338.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:344.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:345.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:357.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:358.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:359.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:362.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:373.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:374.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:380.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:386.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:387.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:389.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-user-security.yang:393.11: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:96.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:12.3: warning(1015): import not used Error: 'fujitsu-user-security-dev.prod.yang' import of module 'fujitsu-user-security' failed fujitsu-user-security-dev.prod.yang:6.3: error(236): module not found Warning: revision with same date on line 35 fujitsu-user-security-dev.prod.yang:40.3: warning(1054): Revision date has already been used Error: object 'usersec' not found in module fujitsu-user-security-dev.prod in Xpath target /fuser:usersec/fuser:idle-timeout fujitsu-user-security-dev.prod.yang:52.1: error(250): definition not found |
| fujitsu-user-security-typedefs@2018-12-07.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-user-security-typedefs@2018-12-07.yang --lint 2>&1": fujitsu-user-security-typedefs@2018-12-07.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs@2018-12-07.yang:73: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:75: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:78: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:84: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:86: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:89: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:126: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security-typedefs@2018-12-07.yang:135: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:216: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security-typedefs@2018-12-07.yang:225: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:243: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:262: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:302: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:314: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:317: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:320: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:348: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:354: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:356: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:359: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:362: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:368: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:370: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:373: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:379: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:381: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:384: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs@2018-12-07.yang:387: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
||||
| fujitsu-user-security@2017-12-22.yang | FAILED | /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\^" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\[" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\]" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-user-security-typedefs.yang:157: warning: the escape sequence "\-" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" fujitsu-user-security@2017-12-22.yang --lint 2>&1": fujitsu-user-security@2017-12-22.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:74: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:78: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:82: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security@2017-12-22.yang:84: error: RFC 8407: 4.10: top-level node security must not be mandatory fujitsu-user-security@2017-12-22.yang:87: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:89: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:90: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:91: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:92: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:95: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:96: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:97: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:99: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:100: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:101: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:102: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:104: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:105: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:106: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:107: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:109: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:110: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:111: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:114: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:117: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:120: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:121: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:122: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:140: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:141: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:146: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:147: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:181: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:182: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:187: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:188: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:193: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:194: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:200: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:201: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:202: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:203: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:204: error: keyword "ordered-by" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:208: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:209: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:210: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:211: error: keyword "ordered-by" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:218: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:219: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:222: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:230: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:231: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:232: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:233: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:236: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:238: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:239: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:240: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:242: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:243: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:244: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:246: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:247: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:248: error: keyword "when" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:249: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:250: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:252: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:253: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:254: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:256: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:257: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:258: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:260: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:261: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:262: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:268: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:271: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:273: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:274: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:278: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:281: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:284: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:285: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:288: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:291: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:295: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:297: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:301: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security@2017-12-22.yang:303: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:304: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:317: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:323: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:329: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security@2017-12-22.yang:335: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security@2017-12-22.yang:338: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-user-security@2017-12-22.yang 2>&1": Error: 'fujitsu-user-security@2017-12-22.yang' import of module 'fujitsu-user-security-typedefs' failed fujitsu-user-security@2017-12-22.yang:6.3: error(236): module not found Error: typedef definition for 'usersecu-type:uage-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:91.14: error(250): definition not found Error: typedef definition for 'usersecu-type:page-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:96.14: error(250): definition not found Error: typedef definition for 'usersecu-type:minit-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:101.14: error(250): definition not found Error: typedef definition for 'usersecu-type:reauth-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:106.14: error(250): definition not found Error: typedef definition for 'usersecu-type:uage-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:121.14: error(250): definition not found Error: typedef definition for 'usersecu-type:umin-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:125.14: error(250): definition not found Error: typedef definition for 'usersecu-type:pmin-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:130.14: error(250): definition not found Error: typedef definition for 'usersecu-type:pcontent-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:135.14: error(250): definition not found Error: typedef definition for 'usersecu-type:prot-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:141.14: error(250): definition not found Error: typedef definition for 'usersecu-type:smt-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:147.14: error(250): definition not found Error: typedef definition for 'usersecu-type:dural-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:152.14: error(250): definition not found Error: typedef definition for 'usersecu-type:maxinv-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:157.14: error(250): definition not found Error: typedef definition for 'usersecu-type:lastlogin-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:182.14: error(250): definition not found Error: typedef definition for 'usersecu-type:warn-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:188.14: error(250): definition not found Error: typedef definition for 'usersecu-type:yORn-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:194.14: error(250): definition not found Error: typedef definition for 'usersecu-type:authentication-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:203.14: error(250): definition not found Error: typedef definition for 'usersecu-type:accounting-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:210.14: error(250): definition not found Error: typedef definition for 'usersecu-type:group-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:220.12: error(250): definition not found Error: typedef definition for 'usersecu-type:username-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:236.12: error(250): definition not found Error: typedef definition for 'usersecu-type:uage-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:240.12: error(250): definition not found Error: typedef definition for 'usersecu-type:page-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:244.12: error(250): definition not found Error: typedef definition for 'usersecu-type:minit-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:254.12: error(250): definition not found Error: typedef definition for 'usersecu-type:reauth-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:258.12: error(250): definition not found Error: typedef definition for 'usersecu-type:username-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:275.14: error(250): definition not found Error: typedef definition for 'usersecu-type:crypt-password-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:279.14: error(250): definition not found Error: typedef definition for 'usersecu-type:password-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:282.14: error(250): definition not found Error: typedef definition for 'usersecu-type:group-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:288.14: error(250): definition not found Error: typedef definition for 'usersecu-type:adminState-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:292.14: error(250): definition not found Error: typedef definition for 'usersecu-type:uage-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:299.16: error(250): definition not found Error: typedef definition for 'usersecu-type:password-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:314.14: error(250): definition not found Error: typedef definition for 'usersecu-type:password-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:320.14: error(250): definition not found Error: typedef definition for 'usersecu-type:password-type' not found in module fujitsu-user-security-typedefs fujitsu-user-security@2017-12-22.yang:326.14: error(250): definition not found Error: 'input' must define at least 1 data-def-stmt fujitsu-user-security@2017-12-22.yang:331.5: error(413): missing data definition statement Warning: top-level NP container 'security' is mandatory fujitsu-user-security@2017-12-22.yang:84.3: warning(1048): top-level object is mandatory Error: object 'group' not found in module fujitsu-user-security in Xpath target group fujitsu-user-security@2017-12-22.yang:218.5: error(250): definition not found Error: invalid identifier in key for list 'usergrp' (group) fujitsu-user-security@2017-12-22.yang:218.5: error(250): definition not found Error: object 'username' not found in module fujitsu-user-security in Xpath target username fujitsu-user-security@2017-12-22.yang:230.5: error(250): definition not found Error: invalid identifier in key for list 'usersec' (username) fujitsu-user-security@2017-12-22.yang:230.5: error(250): definition not found Error: object 'username' not found in module fujitsu-user-security in Xpath target username fujitsu-user-security@2017-12-22.yang:273.7: error(250): definition not found Error: invalid identifier in key for list 'user' (username) fujitsu-user-security@2017-12-22.yang:273.7: error(250): definition not found Warning: no child node '*:page' found for parent 'fujitsu-user-security:usersec' XPath: ../page != 'OFF' fujitsu-user-security@2017-12-22.yang:248.15: warning(1032): no child node available Warning: no child node 'fujitsu-user-security:group' found for parent 'fujitsu-user-security:user' XPath: boolean(/secu:users/secu:user[(secu:group='level-4') and (secu:adminState='allow')] ) or (/secu:users/secu:user[(secu:group='level-6') and (secu:adminState='allow')]) fujitsu-user-security@2017-12-22.yang:268.41: warning(1032): no child node available Warning: no child node 'fujitsu-user-security:adminState' found for parent 'fujitsu-user-security:user' XPath: boolean(/secu:users/secu:user[(secu:group='level-4') and (secu:adminState='allow')] ) or (/secu:users/secu:user[(secu:group='level-6') and (secu:adminState='allow')]) fujitsu-user-security@2017-12-22.yang:268.68: warning(1032): no child node available Warning: no child node 'fujitsu-user-security:group' found for parent 'fujitsu-user-security:user' XPath: boolean(/secu:users/secu:user[(secu:group='level-4') and (secu:adminState='allow')] ) or (/secu:users/secu:user[(secu:group='level-6') and (secu:adminState='allow')]) fujitsu-user-security@2017-12-22.yang:268.123: warning(1032): no child node available Warning: no child node 'fujitsu-user-security:adminState' found for parent 'fujitsu-user-security:user' XPath: boolean(/secu:users/secu:user[(secu:group='level-4') and (secu:adminState='allow')] ) or (/secu:users/secu:user[(secu:group='level-6') and (secu:adminState='allow')]) fujitsu-user-security@2017-12-22.yang:268.150: warning(1032): no child node available Warning: no child node 'fujitsu-user-security:uage' found for parent 'fujitsu-user-security:systemwide' XPath: /secu:security/secu:systemwide/secu:uage != 'OFF' fujitsu-user-security@2017-12-22.yang:296.45: warning(1032): no child node available Warning: no child node '*:uage' found for parent 'fujitsu-user-security:session' XPath: ../uage != 'OFF' fujitsu-user-security@2017-12-22.yang:302.19: warning(1032): no child node available |
||
| iana-afn-safi@2013-07-04.yang | PASSED | |||||
| iana-crypt-hash@2014-08-06.yang | PASSED | |||||
| iana-if-type@2019-03-08.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" iana-if-type.yang --lint 2>&1": iana-if-type.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
||||
| ietf-access-control-list-dev@2017-03-02.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-access-control-list-dev.yang 2>&1": ietf-access-control-list-dev.yang:6: error: module 'ietf-access-control-list' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-access-control-list-dev.yang 2>&1": ietf-access-control-list-dev.yang:36: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:42: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:48: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:59: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:70: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:76: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:80: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:84: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:88: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:92: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:96: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:100: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:104: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:108: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:112: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:116: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:120: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:124: error: node ietf-access-control-list::access-lists is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-access-control-list-dev.yang --lint 2>&1": ietf-access-control-list-dev.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-access-control-list-dev.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-access-control-list-dev.yang:36: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:42: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:48: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:59: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:70: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:76: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:80: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:84: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:88: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:92: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:96: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:100: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:104: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:108: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:112: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:116: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:120: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:124: error: node ietf-access-control-list::access-lists is not found |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-access-control-list-dev.yang 2>&1": Error: 'ietf-access-control-list-dev.yang' import of module 'ietf-access-control-list' failed ietf-access-control-list-dev.yang:6.3: error(236): module not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:acl-name ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:rule-name ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:actions/acl:packet-handling ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:ace-ip-version/acl:ace-ipv4/acl:destination-ipv4-network ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:ace-ip-version/acl:ace-ipv6/acl:destination-ipv6-network ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:ace-ip-version/acl:ace-ipv6/acl:flow-label ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:dscp ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:protocol ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:source-port-range ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:destination-port-range ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-eth ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:input-interface ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:absolute-time ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:acl-type ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:ace-oper-data ietf-access-control-list-dev.yang:127.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:acl-oper-data ietf-access-control-list-dev.yang:127.2: error(250): definition not found |
|
| ietf-access-control-list@2015-03-17.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-access-control-list@2015-03-17.yang 2>&1": ./ietf-packet-fields@2019-03-04.yang:295: error: schema node 'destination-network' already defined at ./ietf-packet-fields@2019-03-04.yang:264 ./ietf-packet-fields@2019-03-04.yang:295: error: schema node 'destination-network' already defined at ./ietf-packet-fields@2019-03-04.yang:264 ./ietf-packet-fields@2019-03-04.yang:309: error: schema node 'source-network' already defined at ./ietf-packet-fields@2019-03-04.yang:277 ./ietf-packet-fields@2019-03-04.yang:309: error: schema node 'source-network' already defined at ./ietf-packet-fields@2019-03-04.yang:277 ietf-access-control-list@2015-03-17.yang:147: error: grouping 'metadata' in module 'ietf-packet-fields' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-access-control-list@2015-03-17.yang 2>&1": ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "matches" at ietf-access-control-list@2015-03-17.yang:119 with the name "destination-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:264) ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "matches" at ietf-access-control-list@2015-03-17.yang:119 with the name "source-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:277) ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list@2015-03-17.yang:126 with the name "destination-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:264) ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list@2015-03-17.yang:126 with the name "source-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:277) ietf-access-control-list@2015-03-17.yang:147: error: grouping "metadata" not found in module "ietf-packet-fields" |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-access-control-list@2015-03-17.yang --lint 2>&1": ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "matches" at ietf-access-control-list@2015-03-17.yang:119 with the name "destination-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:264) ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "matches" at ietf-access-control-list@2015-03-17.yang:119 with the name "source-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:277) ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list@2015-03-17.yang:126 with the name "destination-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:264) ietf-access-control-list@2015-03-17.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list@2015-03-17.yang:126 with the name "source-network" defined at ietf-access-control-list@2015-03-17.yang:133 (at ietf-packet-fields@2019-03-04.yang:277) ietf-access-control-list@2015-03-17.yang:147: error: grouping "metadata" not found in module "ietf-packet-fields" |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/ietf-access-control-list@2015-03-17.yang 2>&1": libyang err : Grouping "packet-fields:metadata" referenced by a uses statement not found. (Path "/ietf-access-control-list:access-lists/acl/access-list-entries/ace/matches/{uses='packet-fields:metadata'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-access-control-list@2015-03-17.yang 2>&1": Error: 'ietf-access-control-list@2015-03-17.yang' import of module 'ietf-packet-fields' failed ietf-access-control-list@2015-03-17.yang:9.3: error(236): module not found Error: grouping definition for 'packet-fields:acl-ipv4-header-fields' not found in module ietf-packet-fields ietf-access-control-list@2015-03-17.yang:133.21: error(250): definition not found Error: grouping definition for 'packet-fields:acl-ipv6-header-fields' not found in module ietf-packet-fields ietf-access-control-list@2015-03-17.yang:136.21: error(250): definition not found Error: grouping definition for 'packet-fields:acl-ip-header-fields' not found in module ietf-packet-fields ietf-access-control-list@2015-03-17.yang:139.17: error(250): definition not found Error: grouping definition for 'packet-fields:acl-eth-header-fields' not found in module ietf-packet-fields ietf-access-control-list@2015-03-17.yang:144.17: error(250): definition not found Error: grouping definition for 'packet-fields:metadata' not found in module ietf-packet-fields ietf-access-control-list@2015-03-17.yang:147.13: error(250): definition not found Error: grouping 'metadata' not found ietf-access-control-list@2015-03-17.yang:147.13: error(250): definition not found |
| ietf-alarms-dev@2016-12-08.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-alarms-dev.prod.yang --lint 2>&1": ietf-alarms-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement ietf-alarms-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement ietf-alarms-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement ietf-alarms-dev.prod.yang:9: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
||||
| ietf-alarms-dev@2017-02-01.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-alarms-dev.yang 2>&1": ietf-alarms-dev.yang:5: error: module 'ietf-alarms' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-alarms-dev.yang 2>&1": ietf-alarms-dev.yang:16: error: node ietf-alarms::shelved-alarms is not found ietf-alarms-dev.yang:20: error: node ietf-alarms::cleared is not found ietf-alarms-dev.yang:24: error: node ietf-alarms::cleared-not-closed is not found ietf-alarms-dev.yang:28: error: node ietf-alarms::cleared-closed is not found ietf-alarms-dev.yang:32: error: node ietf-alarms::not-cleared-closed is not found ietf-alarms-dev.yang:36: error: node ietf-alarms::not-cleared-not-closed is not found ietf-alarms-dev.yang:45: error: node ietf-alarms::related-alarms is not found ietf-alarms-dev.yang:49: error: node ietf-alarms::impacted-resources is not found ietf-alarms-dev.yang:53: error: node ietf-alarms::root-cause-resources is not found ietf-alarms-dev.yang:65: error: node ietf-alarms::last-operator-state is not found ietf-alarms-dev.yang:68: error: node ietf-alarms::last-operator is not found ietf-alarms-dev.yang:72: error: node ietf-alarms::last-operator-text is not found ietf-alarms-dev.yang:75: error: node ietf-alarms::last-operator-action is not found ietf-alarms-dev.yang:82: error: node ietf-alarms::operator-action is not found ietf-alarms-dev.yang:86: error: node ietf-alarms::compress is not found ietf-alarms-dev.yang:90: error: node ietf-alarms::compress-alarms is not found ietf-alarms-dev.yang:94: error: node ietf-alarms::set-operator-state is not found ietf-alarms-dev.yang:98: error: node ietf-alarms::purge-alarms is not found ietf-alarms-dev.yang:102: error: node ietf-alarms::max-alarm-history is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-alarms-dev.yang --lint 2>&1": ietf-alarms-dev.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement ietf-alarms-dev.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement ietf-alarms-dev.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement ietf-alarms-dev.yang:16: error: node ietf-alarms::shelved-alarms is not found ietf-alarms-dev.yang:20: error: node ietf-alarms::cleared is not found ietf-alarms-dev.yang:24: error: node ietf-alarms::cleared-not-closed is not found ietf-alarms-dev.yang:28: error: node ietf-alarms::cleared-closed is not found ietf-alarms-dev.yang:32: error: node ietf-alarms::not-cleared-closed is not found ietf-alarms-dev.yang:36: error: node ietf-alarms::not-cleared-not-closed is not found ietf-alarms-dev.yang:45: error: node ietf-alarms::related-alarms is not found ietf-alarms-dev.yang:49: error: node ietf-alarms::impacted-resources is not found ietf-alarms-dev.yang:53: error: node ietf-alarms::root-cause-resources is not found ietf-alarms-dev.yang:65: error: node ietf-alarms::last-operator-state is not found ietf-alarms-dev.yang:68: error: node ietf-alarms::last-operator is not found ietf-alarms-dev.yang:72: error: node ietf-alarms::last-operator-text is not found ietf-alarms-dev.yang:75: error: node ietf-alarms::last-operator-action is not found ietf-alarms-dev.yang:82: error: node ietf-alarms::operator-action is not found ietf-alarms-dev.yang:86: error: node ietf-alarms::compress is not found ietf-alarms-dev.yang:90: error: node ietf-alarms::compress-alarms is not found ietf-alarms-dev.yang:94: error: node ietf-alarms::set-operator-state is not found ietf-alarms-dev.yang:98: error: node ietf-alarms::purge-alarms is not found ietf-alarms-dev.yang:102: error: node ietf-alarms::max-alarm-history is not found |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-alarms-dev.yang 2>&1": Error: 'ietf-alarms-dev.yang' import of module 'ietf-alarms' failed ietf-alarms-dev.yang:5.5: error(236): module not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:control/alarms:shelved-alarms ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:cleared ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:cleared-not-closed ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:cleared-closed ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:not-cleared-closed ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:not-cleared-not-closed ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:alt-resource ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:related-alarms ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:impacted-resources ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:root-cause-resources ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:is-cleared ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:status-change ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-state ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-text ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-action ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:operator-action ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'operator-action' not found in module ietf-alarms-dev in Xpath target /alarms:operator-action ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'compress' not found in module ietf-alarms-dev in Xpath target /alarms:compress ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'compress-alarms' not found in module ietf-alarms-dev in Xpath target /alarms:compress-alarms ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'set-operator-state' not found in module ietf-alarms-dev in Xpath target /alarms:set-operator-state ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'purge-alarms' not found in module ietf-alarms-dev in Xpath target /alarms:purge-alarms ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:control/alarms:max-alarm-history ietf-alarms-dev.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:control/alarms:notify-status-changes ietf-alarms-dev.yang:110.2: error(250): definition not found |
|
| ietf-alarms@2015-05-04.yang | PASSED | |||||
| ietf-inet-types@2013-07-15.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-inet-types@2013-07-15.yang --lint 2>&1": ietf-inet-types@2013-07-15.yang:361: error: keyword "length" not in canonical order (see RFC 6020, Section 12) |
||||
| ietf-interfaces-dev@2018-04-23.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-interfaces-dev.prod.yang 2>&1": ietf-interfaces-dev.prod.yang:106: error: XPath function "re-match" is not defined in the XPath context /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/fujitsu-equipment.yang:13: warning: imported module "fujitsu-notification-types" not used |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-interfaces-dev.prod.yang --lint 2>&1": ietf-interfaces-dev.prod.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:72: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:106: error: XPath function "re-match" is not defined in the XPath context |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/ietf-interfaces-dev.prod.yang 2>&1": Error: 'ietf-interfaces-dev.prod.yang' import of module 'fujitsu-equipment' failed ietf-interfaces-dev.prod.yang:6.5: error(236): module not found Error: Module for prefix 'eqpt' not found ietf-interfaces-dev.prod.yang:1.48: error(236): module not found |
||
| ietf-interfaces@2014-05-08.yang | PASSED WITH WARNINGS | ietf-interfaces@2014-05-08.yang:243: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-interfaces@2014-05-08.yang:246: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
||||
| ietf-ip-dev@2017-04-19.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ip-dev.yang 2>&1": ietf-ip-dev.yang:128: error: XPath function "re-match" is not defined in the XPath context |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ip-dev.yang --lint 2>&1": ietf-ip-dev.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ip-dev.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ip-dev.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ip-dev.yang:82: error: keyword "description" not in canonical order (see RFC 6020, Section 12) ietf-ip-dev.yang:90: error: keyword "description" not in canonical order (see RFC 6020, Section 12) ietf-ip-dev.yang:128: error: keyword "must" not in canonical order (see RFC 6020, Section 12) ietf-ip-dev.yang:128: error: XPath function "re-match" is not defined in the XPath context |
|||
| ietf-ip@2014-06-16.yang | PASSED | |||||
| ietf-ipv4-unicast-routing-dev@2017-02-21.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-ipv4-unicast-routing-dev.yang 2>&1": ietf-ipv4-unicast-routing-dev.yang:7: error: module 'ietf-routing' not found ietf-ipv4-unicast-routing-dev.yang:11: error: module 'ietf-ipv4-unicast-routing' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv4-unicast-routing-dev.yang 2>&1": ietf-ipv4-unicast-routing-dev.yang:11: warning: imported module "ietf-ipv4-unicast-routing" not used ietf-ipv4-unicast-routing-dev.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing-dev.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev.yang:62: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv4-unicast-routing-dev.yang --lint 2>&1": ietf-ipv4-unicast-routing-dev.yang:11: warning: imported module "ietf-ipv4-unicast-routing" not used ietf-ipv4-unicast-routing-dev.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ipv4-unicast-routing-dev.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing-dev.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev.yang:62: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-ipv4-unicast-routing-dev.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route' ietf-ipv4-unicast-routing-dev.yang:66.2: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address/v4ur:address ietf-ipv4-unicast-routing-dev.yang:66.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/v4ur:destination-prefix ietf-ipv4-unicast-routing-dev.yang:66.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address ietf-ipv4-unicast-routing-dev.yang:66.2: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address' ietf-ipv4-unicast-routing-dev.yang:66.2: error(251): definition segment not found Warning: Module 'ietf-ipv4-unicast-routing' not used ietf-ipv4-unicast-routing-dev.yang:11.3: warning(1015): import not used |
|
| ietf-ipv4-unicast-routing@2015-05-25.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'routing-instance' not found ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'routing-protocols' not found ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'routing-protocol' not found ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'static-routes' not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node 'fib-route' not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node 'input' not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node 'destination-address' not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node 'output' not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node 'route' not found ietf-ipv4-unicast-routing@2015-05-25.yang:179: error: node 'next-hop' not found ietf-ipv4-unicast-routing@2015-05-25.yang:179: error: node 'next-hop-options' not found ietf-ipv4-unicast-routing@2015-05-25.yang:179: error: node 'simple-next-hop' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv4-unicast-routing@2015-05-25.yang:104: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:180: error: node ietf-routing::fib-route is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv4-unicast-routing@2015-05-25.yang --lint 2>&1": ietf-ipv4-unicast-routing@2015-05-25.yang:104: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:180: error: node ietf-routing::fib-route is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes'}".) libyang err : Augment target node "/rt:fib-route/rt:input/rt:destination-address" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:fib-route/rt:input/rt:destination-address'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address ietf-ipv4-unicast-routing@2015-05-25.yang:149.6: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route ietf-ipv4-unicast-routing@2015-05-25.yang:164.6: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes' ietf-ipv4-unicast-routing@2015-05-25.yang:103.6: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop ietf-ipv4-unicast-routing@2015-05-25.yang:179.6: error(250): definition not found |
| ietf-ipv6-unicast-routing-dev@2017-02-21.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-ipv6-unicast-routing-dev.yang 2>&1": ietf-ipv6-unicast-routing-dev.yang:7: error: module 'ietf-routing' not found ietf-ipv6-unicast-routing-dev.yang:11: error: module 'ietf-ipv6-unicast-routing' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv6-unicast-routing-dev.yang 2>&1": ietf-ipv6-unicast-routing-dev.yang:11: warning: imported module "ietf-ipv6-unicast-routing" not used ietf-ipv6-unicast-routing-dev.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing-dev.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev.yang:62: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv6-unicast-routing-dev.yang --lint 2>&1": ietf-ipv6-unicast-routing-dev.yang:11: warning: imported module "ietf-ipv6-unicast-routing" not used ietf-ipv6-unicast-routing-dev.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ipv6-unicast-routing-dev.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing-dev.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev.yang:62: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-ipv6-unicast-routing-dev.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v6ur:ipv6/v6ur:route' ietf-ipv6-unicast-routing-dev.yang:65.2: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address/v6ur:address ietf-ipv6-unicast-routing-dev.yang:65.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/v6ur:destination-prefix ietf-ipv6-unicast-routing-dev.yang:65.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address ietf-ipv6-unicast-routing-dev.yang:65.2: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address' ietf-ipv6-unicast-routing-dev.yang:65.2: error(251): definition segment not found Warning: Module 'ietf-ipv6-unicast-routing' not used ietf-ipv6-unicast-routing-dev.yang:11.3: warning(1015): import not used |
|
| ietf-ipv6-unicast-routing@2015-05-25.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'routing-instance' not found ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'routing-protocols' not found ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'routing-protocol' not found ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'static-routes' not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node 'fib-route' not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node 'input' not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node 'destination-address' not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node 'output' not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node 'route' not found ietf-ipv6-unicast-routing@2015-05-25.yang:581: error: node 'next-hop' not found ietf-ipv6-unicast-routing@2015-05-25.yang:581: error: node 'next-hop-options' not found ietf-ipv6-unicast-routing@2015-05-25.yang:581: error: node 'simple-next-hop' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv6-unicast-routing@2015-05-25.yang:506: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:582: error: node ietf-routing::fib-route is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ipv6-unicast-routing@2015-05-25.yang --lint 2>&1": ietf-ipv6-unicast-routing@2015-05-25.yang:506: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:582: error: node ietf-routing::fib-route is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes'}".) libyang err : Augment target node "/rt:fib-route/rt:input/rt:destination-address" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:fib-route/rt:input/rt:destination-address'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address ietf-ipv6-unicast-routing@2015-05-25.yang:551.6: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route ietf-ipv6-unicast-routing@2015-05-25.yang:566.6: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes' ietf-ipv6-unicast-routing@2015-05-25.yang:505.6: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop ietf-ipv6-unicast-routing@2015-05-25.yang:581.6: error(250): definition not found |
| ietf-key-chain@2015-02-24.yang | PASSED | |||||
| ietf-netconf-acm@2012-02-22.yang | FAILED | ietf-netconf-acm@2012-02-22.yang:103:16: warning: illegal character after \ ietf-netconf-acm@2012-02-22.yang:144:18: warning: illegal character after \ |
ietf-netconf-acm@2012-02-22.yang:103: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning ietf-netconf-acm@2012-02-22.yang:144: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
ietf-netconf-acm@2012-02-22.yang:103: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning ietf-netconf-acm@2012-02-22.yang:144: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/ietf-netconf-acm@2012-02-22.yang 2>&1": libyang err : Double-quoted string unknown special character '\*'. (Line number 103.) libyang err : Parsing module "ietf-netconf-acm" failed. |
|
| ietf-netconf-monitoring@2010-10-04.yang | PASSED WITH WARNINGS | ietf-netconf-monitoring@2010-10-04.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-netconf-monitoring@2010-10-04.yang:55: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-netconf-monitoring@2010-10-04.yang:56: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-netconf-monitoring@2010-10-04.yang:384: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement |
||||
| ietf-netconf-notifications@2012-02-06.yang | FAILED | ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found |
ietf-netconf-notifications@2012-02-06.yang:286: warning: node "ietf-netconf-notifications::confirm-event" is not found in module "ietf-netconf-notifications" | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-netconf-notifications@2012-02-06.yang --lint 2>&1": ietf-netconf-notifications@2012-02-06.yang:95: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement ietf-netconf-notifications@2012-02-06.yang:286: warning: node "ietf-netconf-notifications::confirm-event" is not found in module "ietf-netconf-notifications" |
libyang warn: Schema node "confirm-event" for parent " |
Warning: no parent found in XPath expr '../confirm-event != 'timeout'' ietf-netconf-notifications@2012-02-06.yang:286.12: warning(1031): no parent node available |
| ietf-netconf-with-defaults@2011-06-01.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-netconf-with-defaults@2011-06-01.yang --lint 2>&1": ietf-netconf-with-defaults@2011-06-01.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-netconf-with-defaults@2011-06-01.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12) ietf-netconf-with-defaults@2011-06-01.yang:97: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-netconf-with-defaults@2011-06-01.yang:101: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
||||
| ietf-netconf@2011-06-01.yang | PASSED | |||||
| ietf-ospf-dev@2017-07-19.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-ospf-dev.yang 2>&1": ietf-ospf-dev.yang:17: error: module 'ietf-ospf' not found ietf-ospf-dev.yang:21: error: module 'ietf-routing' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ospf-dev.yang 2>&1": ietf-ospf-dev.yang:5: warning: imported module "tailf-common" not used ietf-ospf-dev.yang:9: warning: imported module "ietf-inet-types" not used ietf-ospf-dev.yang:17: warning: imported module "ietf-ospf" not used ietf-ospf-dev.yang:54: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:65: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:75: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:85: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:95: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:105: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:115: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:125: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:135: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:145: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:151: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:157: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:161: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:165: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:169: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:173: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:177: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:181: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:185: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:189: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:193: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:197: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:201: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:205: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:209: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:213: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:217: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:221: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:225: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:230: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:234: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:238: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:242: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:246: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:251: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:255: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:259: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:263: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:267: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:271: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:275: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:279: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:284: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:290: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:294: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:298: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:302: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:306: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:310: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:314: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:320: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:1970 (at standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2121 (at standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:601: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" standards/ietf-ospf.yang:2151 (at standards/ietf-ospf.yang:1458): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2151 (at standards/ietf-ospf.yang:1467): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2169 (at standards/ietf-ospf.yang:1486): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2169 (at standards/ietf-ospf.yang:1495): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2187 (at standards/ietf-ospf.yang:1514): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2187 (at standards/ietf-ospf.yang:1523): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:1946 (at standards/ietf-ospf.yang:1614): warning: node "ietf-routing::routing-instance" is not found in "ietf-routing::routing" standards/ietf-ospf.yang:1868: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:1907: error: type "routing-instance-ref" not found in module "ietf-routing" standards/ietf-ospf.yang:2003: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2020: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2018 is not found standards/ietf-ospf.yang:2038: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2052: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2050 is not found standards/ietf-ospf.yang:2064: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2087: error: type "routing-instance-ref" not found in module "ietf-routing" standards/ietf-ospf.yang:2134: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2193: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2207: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2205 is not found standards/ietf-ospf.yang:2224: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2238: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2236 is not found standards/ietf-ospf.yang:2292: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2331: error: type "routing-instance-ref" not found in module "ietf-routing" |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ospf-dev.yang --lint 2>&1": ietf-ospf-dev.yang:5: warning: imported module "tailf-common" not used ietf-ospf-dev.yang:9: warning: imported module "ietf-inet-types" not used ietf-ospf-dev.yang:17: warning: imported module "ietf-ospf" not used ietf-ospf-dev.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ospf-dev.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ospf-dev.yang:54: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:65: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:75: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:85: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:95: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:105: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:115: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:125: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:135: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:145: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:151: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:157: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:161: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:165: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:169: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:173: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:177: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:181: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:185: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:189: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:193: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:197: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:201: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:205: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:209: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:213: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:217: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:221: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:225: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:230: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:234: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:238: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:242: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:246: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:251: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:255: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:259: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:263: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:267: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:271: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:275: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:279: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:284: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:290: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:294: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:298: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:302: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:306: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:310: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:314: error: node ietf-routing::routing-instance is not found ietf-ospf-dev.yang:320: error: node ietf-routing::routing-instance is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-ospf-dev.yang 2>&1": libyang err : Not found node "key-chain-list" in path. (Schema location "/ietf-routing:routing/routing-instance/routing-protocols/routing-protocol/ietf-ospf:ospf/instance/area/sham-link/authentication/auth-type-selection/auth-trailer-key-chain/key-chain".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-ospf-dev.yang 2>&1": Error: 'ietf-ospf-dev.yang' import of module 'tailf-common' failed ietf-ospf-dev.yang:5.3: error(236): module not found Error: 'ietf-ospf-dev.yang' import of module 'ietf-ospf' failed ietf-ospf-dev.yang:17.3: error(236): module not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:inter-area' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:intra-area' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:external' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:key' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:hello-interval' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:cost' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:dead-interval' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:retransmit-interval' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:transmit-delay' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-id' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:graceful-restart/ospf:helper-enable' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:coarse/ospf:internal' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:nsr' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:protocol-shutdown' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:maximum' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:mpls' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:sham-link' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:demand-circuit' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:lls' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:prefix-suppression' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:bfd' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1-12' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:sha-1' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-256' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-384' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-512' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:static-neighbors' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:link-scope-lsas' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:raw-data' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:raw-data' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:router-id' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv3' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv3' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:operation-mode' ietf-ospf-dev.yang:325.10: error(251): definition segment not found Warning: Module 'tailf-common' not used ietf-ospf-dev.yang:5.3: warning(1015): import not used Warning: Module 'ietf-inet-types' not used ietf-ospf-dev.yang:9.3: warning(1015): import not used Warning: Module 'ietf-ospf' not used ietf-ospf-dev.yang:17.3: warning(1015): import not used |
| ietf-ospf@2015-03-09.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ospf@2015-03-09.yang 2>&1": ietf-ospf@2015-03-09.yang:704: error: grouping 'crypto-algorithm-types' in module 'ietf-key-chain' not found ietf-ospf@2015-03-09.yang:1952: error: node 'routing-instance' not found ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocols' not found ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocol' not found ietf-ospf@2015-03-09.yang:2155: error: node 'routing-instance' not found ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocols' not found ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocol' not found ietf-ospf@2015-03-09.yang:2397: error: node 'ribs' not found ietf-ospf@2015-03-09.yang:2397: error: node 'rib' not found ietf-ospf@2015-03-09.yang:2397: error: node 'routes' not found ietf-ospf@2015-03-09.yang:2397: error: node 'route' not found ietf-ospf@2015-03-09.yang:2435: error: typedef 'routing-instance-ref' in module 'ietf-routing' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ospf@2015-03-09.yang 2>&1": ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2111 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2141 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2324 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2352 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for rib-ref at ietf-ospf@2015-03-09.yang:137 is not found ietf-ospf@2015-03-09.yang:2058 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2208 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:704: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" ietf-ospf@2015-03-09.yang:1953: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2096: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2131: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2156: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2224: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2240: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2245: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2266: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2271: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2293: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2298: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2311: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2342: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2398: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2435: error: type "routing-instance-ref" not found in module "ietf-routing" |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-ospf@2015-03-09.yang --lint 2>&1": ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2111 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2141 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2324 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2352 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for rib-ref at ietf-ospf@2015-03-09.yang:137 is not found ietf-ospf@2015-03-09.yang:2058 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2208 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:704: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" ietf-ospf@2015-03-09.yang:1115: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1468: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1470: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1472: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1474: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1953: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2096: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2131: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2156: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2224: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2240: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2245: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2266: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2271: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2293: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2298: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2311: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2342: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2398: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2435: error: type "routing-instance-ref" not found in module "ietf-routing" |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/ietf-ospf@2015-03-09.yang 2>&1": libyang err : Referenced type "rt:routing-instance-ref" not found. (Path "/ietf-ospf:if-state-change/{uses='notification-instance-hdr'}/routing-instance".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ospf@2015-03-09.yang 2>&1": Error: 'ietf-ospf@2015-03-09.yang' import of module 'ietf-key-chain' failed ietf-ospf@2015-03-09.yang:24.3: error(236): module not found Error: typedef definition for 'key-chain:key-chain-ref' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:692.18: error(250): definition not found Error: grouping definition for 'key-chain:crypto-algorithm-types' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:704.13: error(250): definition not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /var/yang/all_modules/ietf-routing@2018-03-13.yang ietf-ospf@2015-03-09.yang:2435.12: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:1952.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:2155.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2095.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2309.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route' ietf-ospf@2015-03-09.yang:2397.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface' ietf-ospf@2015-03-09.yang:2129.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces' ietf-ospf@2015-03-09.yang:2340.3: error(251): definition segment not found Warning: path failed (no nodes available): '/rt:routing/rt:routing-instance/rt:ribs/rt:rib/rt:name' |
| ietf-packet-fields@2015-06-11.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-packet-fields@2015-06-11.yang --lint 2>&1": ietf-packet-fields@2015-06-11.yang:71: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-packet-fields@2015-06-11.yang:74: error: keyword "type" not in canonical order (see RFC 6020, Section 12) ietf-packet-fields@2015-06-11.yang:91: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-packet-fields@2015-06-11.yang:94: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
||||
| ietf-restconf-monitoring@2016-08-15.yang | PASSED | |||||
| ietf-restconf@2017-01-26.yang | FAILED | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-restconf@2017-01-26.yang 2>&1": Error: 'ietf-restconf@2017-01-26.yang' import of module 'tailf-common' failed ietf-restconf@2017-01-26.yang:8.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-restconf@2017-01-26.yang:6.3: error(236): module not found |
||||
| ietf-routing-dev@2017-02-21.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-routing-dev.yang 2>&1": ietf-routing-dev.yang:5: error: module 'ietf-routing' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-routing-dev.yang 2>&1": ietf-routing-dev.yang:35: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:42: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:48: error: node ietf-routing::fib-route is not found ietf-routing-dev.yang:54: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-routing-dev.yang --lint 2>&1": ietf-routing-dev.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-routing-dev.yang:35: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:42: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:48: error: node ietf-routing::fib-route is not found ietf-routing-dev.yang:54: error: node ietf-routing::routing-instance is not found |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-routing-dev.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance' ietf-routing-dev.yang:57.2: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-routing-dev.yang:57.2: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route ietf-routing-dev.yang:57.2: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/rt:outgoing-interface' ietf-routing-dev.yang:57.2: error(251): definition segment not found |
|
| ietf-routing@2015-05-25.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-routing@2015-05-25.yang --lint 2>&1": ietf-routing@2015-05-25.yang:297: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-routing@2015-05-25.yang:298: error: keyword "type" not in canonical order (see RFC 6020, Section 12) ietf-routing@2015-05-25.yang:493: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-routing@2015-05-25.yang:494: error: keyword "type" not in canonical order (see RFC 6020, Section 12) |
||||
| ietf-syslog-dev@2017-10-16.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-syslog-dev.yang 2>&1": ietf-syslog-dev.yang:86: error: unexpected keyword 'mandatory' ietf-syslog-dev.yang:140: error: unexpected keyword 'mandatory' |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-syslog-dev.yang 2>&1": ietf-syslog-dev.yang:86: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" ietf-syslog-dev.yang:140: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-syslog-dev.yang --lint 2>&1": ietf-syslog-dev.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:86: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" ietf-syslog-dev.yang:140: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-syslog-dev.yang 2>&1": libyang err : Deviate "delete" does not support keyword "mandatory". (Line number 86.) libyang err : Parsing module "ietf-syslog-dev" failed. |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/ietf-syslog-dev.yang 2>&1": Error: 'ietf-syslog-dev.yang' import of module 'ietf-syslog' failed ietf-syslog-dev.yang:6.3: error(236): module not found Error: mandatory-stmt cannot be deleted ietf-syslog-dev.yang:86.5: error(347): invalid deviate sub-clause Error: mandatory-stmt cannot be deleted ietf-syslog-dev.yang:140.5: error(347): invalid deviate sub-clause Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:console ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:buffer ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:name ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:log-selector/slg:selector-facility/slg:no-log-facility ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:log-selector/slg:selector-facility/slg:log-facility/slg:log-facility/slg:compare-op ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:log-selector/slg:pattern-match ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:structured-data ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:file-archive ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:name ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:transport/slg:udp/slg:udp/slg:port ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:transport/slg:tcp/slg:tcp/slg:port ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:transport/slg:tls ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:log-selector/slg:selector-facility/slg:no-log-facility ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:log-selector/slg:selector-facility/slg:log-facility/slg:log-facility/slg:compare-op ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:log-selector/slg:pattern-match ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:destination-facility ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:source-interface ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:structured-data ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:syslog-sign ietf-syslog-dev.yang:167.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:session ietf-syslog-dev.yang:167.2: error(250): definition not found |
| ietf-syslog-types@2016-07-08.yang | PASSED | |||||
| ietf-syslog@2016-07-08.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" ietf-syslog@2016-07-08.yang --lint 2>&1": ietf-syslog@2016-07-08.yang:274: error: RFC 8407: 4.10: top-level node syslog must not be mandatory |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-syslog@2016-07-08.yang 2>&1": Error: 'ietf-syslog@2016-07-08.yang' import of module 'ietf-syslog-types' failed ietf-syslog@2016-07-08.yang:11.3: error(236): module not found Error: typedef definition for 'syslogtypes:severity' not found in module ietf-syslog-types ietf-syslog@2016-07-08.yang:124.14: error(250): definition not found Load module 'ietf-syslog-types' failed (module not found) Error: failure importing module 'ietf-syslog-types' ietf-syslog@2016-07-08.yang:226.17: error(236): module not found Error: identityref has unknown base value (syslog-facility) ietf-syslog@2016-07-08.yang:226.17: error(236): module not found Load module 'ietf-syslog-types' failed (module not found) Error: failure importing module 'ietf-syslog-types' ietf-syslog@2016-07-08.yang:456.13: error(236): module not found Error: identityref has unknown base value (syslog-facility) ietf-syslog@2016-07-08.yang:456.13: error(236): module not found Warning: top-level NP container 'syslog' is mandatory ietf-syslog@2016-07-08.yang:274.3: warning(1048): top-level object is mandatory Warning: no child node '*:severity' found for parent 'ietf-syslog:log-facility' XPath: ../severity != "all" and ../severity != "none" ietf-syslog@2016-07-08.yang:151.12: warning(1032): no child node available Warning: no child node '*:severity' found for parent 'ietf-syslog:log-facility' XPath: ../severity != "all" and ../severity != "none" ietf-syslog@2016-07-08.yang:151.45: warning(1032): no child node available |
|||
| ietf-yang-library@2016-06-21.yang | PASSED | |||||
| ietf-yang-smiv2@2011-11-25.yang | PASSED | |||||
| ietf-yang-types@2013-07-15.yang | PASSED | |||||
| iputil@2018-12-14.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" iputil.yang --lint 2>&1": iputil.yang:1: warning: RFC 8407: 4.1: no module name prefix string used iputil.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iputil.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iputil.yang:38: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:45: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:51: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:54: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:57: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:58: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:62: error: RFC 8407: 4.14: statement "container" must have a "description" substatement iputil.yang:63: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:66: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:73: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:82: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:85: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:88: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:89: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:93: error: RFC 8407: 4.14: statement "container" must have a "description" substatement iputil.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:97: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:104: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:113: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:116: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:119: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:120: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:127: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:136: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:142: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:143: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/standards/iputil.yang 2>&1": Error: 'iputil.yang' import of module 'tailf-common' failed iputil.yang:5.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' iputil.yang:39.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' iputil.yang:74.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' iputil.yang:105.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' iputil.yang:128.5: error(236): module not found |
|||
| openconfig-extensions@2017-01-29.yang | PASSED WITH WARNINGS | openconfig-extensions@2017-01-29.yang:33: warning: RFC 8407: 4.4: statement "yin-element" is given with its default value "false" | ||||
| openconfig-inet-types@2017-08-24.yang | FAILED | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/openconfig-inet-types@2017-08-24.yang 2>&1": Error: 'openconfig-inet-types@2017-08-24.yang' import of module 'openconfig-extensions' failed openconfig-inet-types@2017-08-24.yang:7.3: error(236): module not found Load module 'openconfig-extensions' failed (module not found) Error: failure importing module 'openconfig-extensions' openconfig-inet-types@2017-08-24.yang:34.3: error(236): module not found Warning: revision with same date on line 48 openconfig-inet-types@2017-08-24.yang:54.3: warning(1054): Revision date has already been used |
||||
| openconfig-telemetry-dev@2018-12-14.yang | FAILED | Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/openconfig-telemetry-dev@2018-12-14.yang 2>&1": openconfig-telemetry-dev@2018-12-14.yang:55: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:58: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:61: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:64: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:74: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:81: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:86: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:129: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:137: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:157: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:160: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:163: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:166: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:169: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:172: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:175: error: node 'persistent' not found openconfig-telemetry-dev@2018-12-14.yang:178: error: node 'dynamic' not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" openconfig-telemetry-dev@2018-12-14.yang 2>&1": openconfig-telemetry-dev@2018-12-14.yang:55: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:58: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:61: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:64: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:74: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:81: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:86: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:129: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:137: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:157: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:160: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:163: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:166: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:169: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:172: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:175: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:178: error: node openconfig-telemetry::dynamic is not found |
Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" openconfig-telemetry-dev@2018-12-14.yang --lint 2>&1": openconfig-telemetry-dev@2018-12-14.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev@2018-12-14.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev@2018-12-14.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev@2018-12-14.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev@2018-12-14.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev@2018-12-14.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev@2018-12-14.yang:55: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:58: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:61: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:64: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:74: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:77: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement openconfig-telemetry-dev@2018-12-14.yang:81: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:86: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:129: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:132: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement openconfig-telemetry-dev@2018-12-14.yang:133: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement openconfig-telemetry-dev@2018-12-14.yang:137: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:157: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:160: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:163: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:166: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:169: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:172: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:175: error: node openconfig-telemetry::persistent is not found openconfig-telemetry-dev@2018-12-14.yang:178: error: node openconfig-telemetry::dynamic is not found |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/openconfig-telemetry-dev@2018-12-14.yang 2>&1": libyang err : Multiple deviations of "/oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:originated-qos-marking" with one of them being "not-supported". (Path "/openconfig-telemetry-dev:{deviation='/oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:originated-qos-marking'}".) |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/openconfig-telemetry-dev@2018-12-14.yang 2>&1": Error: 'openconfig-telemetry-dev@2018-12-14.yang' import of module 'openconfig-telemetry' failed openconfig-telemetry-dev@2018-12-14.yang:5.3: error(236): module not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:originated-qos-marking openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:local-source-address openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:config/oc-telemetry:heartbeat-interval openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:config/oc-telemetry:sample-interval openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:protocol openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:subscription-name openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:destinations/oc-telemetry:destination/oc-telemetry:config/oc-telemetry:destination-address openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:destinations/oc-telemetry:destination/oc-telemetry:config/oc-telemetry:destination-port openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:config/oc-telemetry:group-id openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:config/oc-telemetry:sensor-group-id openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:encoding openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:state openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:sensor-paths/oc-telemetry:sensor-path/oc-telemetry:config/oc-telemetry:exclude-filter openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:sensor-paths/oc-telemetry:sensor-path/oc-telemetry:state openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:state openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:destinations/oc-telemetry:destination/oc-telemetry:state openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:state openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:config/oc-telemetry:suppress-redundant openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:state openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:state openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:dynamic openconfig-telemetry-dev@2018-12-14.yang:181.2: error(250): definition not found |
| openconfig-telemetry-types@2017-02-20.yang | FAILED | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/openconfig-telemetry-types@2017-02-20.yang 2>&1": Error: 'openconfig-telemetry-types@2017-02-20.yang' import of module 'openconfig-extensions' failed openconfig-telemetry-types@2017-02-20.yang:6.3: error(236): module not found Load module 'openconfig-extensions' failed (module not found) Error: failure importing module 'openconfig-extensions' openconfig-telemetry-types@2017-02-20.yang:18.3: error(236): module not found |
||||
| openconfig-telemetry@2017-02-20.yang | FAILED | Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/openconfig-telemetry@2017-02-20.yang 2>&1": Error: 'openconfig-telemetry@2017-02-20.yang' import of module 'openconfig-inet-types' failed openconfig-telemetry@2017-02-20.yang:6.3: error(236): module not found Error: 'openconfig-telemetry@2017-02-20.yang' import of module 'openconfig-extensions' failed openconfig-telemetry@2017-02-20.yang:9.3: error(236): module not found Error: 'openconfig-telemetry@2017-02-20.yang' import of module 'openconfig-telemetry-types' failed openconfig-telemetry@2017-02-20.yang:12.3: error(236): module not found Load module 'openconfig-extensions' failed (module not found) Error: failure importing module 'openconfig-extensions' openconfig-telemetry@2017-02-20.yang:23.3: error(236): module not found Error: typedef definition for 'oc-inet:dscp' not found in module openconfig-inet-types openconfig-telemetry@2017-02-20.yang:484.12: error(250): definition not found Error: typedef definition for 'oc-inet:ip-address' not found in module openconfig-inet-types openconfig-telemetry@2017-02-20.yang:574.12: error(250): definition not found Error: typedef definition for 'oc-inet:ip-address' not found in module openconfig-inet-types openconfig-telemetry@2017-02-20.yang:659.12: error(250): definition not found Load module 'openconfig-telemetry-types' failed (module not found) Error: failure importing module 'openconfig-telemetry-types' openconfig-telemetry@2017-02-20.yang:543.7: error(236): module not found Error: identityref has unknown base value (STREAM_PROTOCOL) openconfig-telemetry@2017-02-20.yang:543.7: error(236): module not found Load module 'openconfig-telemetry-types' failed (module not found) Error: failure importing module 'openconfig-telemetry-types' openconfig-telemetry@2017-02-20.yang:561.7: error(236): module not found Error: identityref has unknown base value (DATA_ENCODING_METHOD) openconfig-telemetry@2017-02-20.yang:561.7: error(236): module not found Error: XPath node '--:destination-address' not found in parent 'oc-telemetry:config' xpath: ../config/destination-address openconfig-telemetry@2017-02-20.yang:159.34: error(250): definition not found |
||||
| tailf-aaa@2015-06-16.yang | FAILED | tailf-aaa@2015-06-16.yang:246:20: warning: illegal character after \ | tailf-aaa@2015-06-16.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-aaa@2015-06-16.yang --lint 2>&1": tailf-aaa@2015-06-16.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-aaa@2015-06-16.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:72: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:82: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:87: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:92: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:97: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:100: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:105: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:111: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:113: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-aaa@2015-06-16.yang:114: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-aaa@2015-06-16.yang:118: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-aaa@2015-06-16.yang:119: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:123: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:127: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:135: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:143: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:147: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:151: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:155: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:161: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:164: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:166: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:168: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:170: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:174: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:179: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:184: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:188: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:194: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:205: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:211: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:217: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:228: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:232: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:235: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:238: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:241: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:244: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-aaa@2015-06-16.yang:250: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:252: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:255: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:259: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:262: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:264: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:272: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:276: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:281: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:289: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:295: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:300: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:303: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:307: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:310: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:315: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:323: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang /var/yang/all_modules/tailf-aaa@2015-06-16.yang 2>&1": libyang err : Double-quoted string unknown special character '\h'. (Line number 246.) libyang err : Parsing module "tailf-aaa" failed. |
Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/tailf-aaa@2015-06-16.yang 2>&1": Error: 'tailf-aaa@2015-06-16.yang' import of module 'tailf-common' failed tailf-aaa@2015-06-16.yang:14.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:4.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:121.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:125.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:129.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:133.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:137.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:141.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:145.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:149.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:153.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:157.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:162.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:165.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:167.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:199.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:200.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:201.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:202.15: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:208.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:209.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:214.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:215.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:220.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:221.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:172.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:177.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:182.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:191.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:197.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:229.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:275.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:278.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:284.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:293.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:296.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:305.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:309.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:312.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:318.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:325.7: error(236): module not found |
| tailf-acm@2013-03-07.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-acm.yang --lint 2>&1": tailf-acm.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-acm.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-acm.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-acm.yang:29: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-acm.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-acm.yang:71: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-acm.yang:154: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement |
||||
| tailf-common-monitoring@2013-06-14.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-common-monitoring@2013-06-14.yang --lint 2>&1": tailf-common-monitoring@2013-06-14.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-common-monitoring@2013-06-14.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:59: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:64: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:73: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:75: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:101: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:103: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:114: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:133: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:166: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:168: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:169: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:172: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:181: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:194: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:218: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:230: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:234: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:235: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:236: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:237: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:270: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:299: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:309: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:310: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:311: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:312: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:313: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:324: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:333: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:336: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:341: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:353: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:358: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:363: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:366: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:371: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:376: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:379: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:384: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:389: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:401: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:404: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:407: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:420: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:421: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:422: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:426: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:430: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:434: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:438: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:442: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:446: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:450: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:457: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:459: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:460: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:461: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:466: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:470: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:475: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:479: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:485: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:489: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:490: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:491: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:510: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:512: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:586: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:604: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:621: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:644: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:659: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:660: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:661: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:662: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:675: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:687: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:688: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:689: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:690: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:701: error: RFC 8407: 4.14: statement "list" must have a "description" substatement |
||||
| tailf-common-query@2017-04-27.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-common-query.yang --lint 2>&1": tailf-common-query.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-common-query.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-query.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-query.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-query.yang:142: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12) tailf-common-query.yang:179: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query.yang:193: error: keyword "default" not in canonical order (see RFC 6020, Section 12) tailf-common-query.yang:202: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query.yang:217: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-query.yang:224: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-common-query.yang:226: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query.yang:229: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query.yang:250: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query.yang:264: error: keyword "default" not in canonical order (see RFC 6020, Section 12) |
||||
| tailf-common@2017-08-23.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-common@2017-08-23.yang --lint 2>&1": tailf-common@2017-08-23.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-common@2017-08-23.yang:18: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:69: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:85: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:91: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:98: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:111: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:117: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:123: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:130: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:136: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:144: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:160: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:166: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:178: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:184: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:190: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:204: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:211: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:217: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:221: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:228: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:243: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:249: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:264: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:270: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:278: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:284: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:290: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:299: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:308: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:314: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:321: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:327: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:343: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:351: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:373: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:383: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:401: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:412: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:419: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common@2017-08-23.yang:432: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:433: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:434: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:435: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:436: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:437: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:785: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:786: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:787: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:822: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:823: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:824: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:859: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:860: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:2576: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:2577: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:2578: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3069: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3070: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3071: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3088: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3089: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3090: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3091: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3092: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3105: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3106: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common@2017-08-23.yang:3107: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:1: error: RFC 8407: 4.8: statement "submodule" must have a "contact" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:78: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:87: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:97: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:106: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:114: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:124: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:134: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:142: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:149: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:159: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:168: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:176: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:183: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:203: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:210: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:226: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:235: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:245: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:269: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:2176: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:2177: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-cli-extensions.yang:2178: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:1: error: RFC 8407: 4.8: statement "submodule" must have a "contact" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:49: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:55: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:61: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang/third_party/tailf-meta-extensions.yang:67: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement |
||||
| tailf-confd-monitoring@2013-06-14.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-confd-monitoring@2013-06-14.yang --lint 2>&1": tailf-confd-monitoring@2013-06-14.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-confd-monitoring@2013-06-14.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:50: error: RFC 8407: 4.14: statement "container" must have a "description" substatement |
||||
| tailf-kicker@2017-03-16.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-kicker.yang --lint 2>&1": tailf-kicker.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-kicker.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:87: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-kicker.yang:132: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-kicker.yang:133: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-kicker.yang:157: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-kicker.yang:198: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-kicker.yang:199: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-kicker.yang:236: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
||||
| tailf-netconf-monitoring@2016-11-24.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-netconf-monitoring.yang --lint 2>&1": tailf-netconf-monitoring.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-netconf-monitoring.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:134: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:144: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-netconf-monitoring.yang:168: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:169: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:170: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:187: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:201: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:223: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:230: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-netconf-monitoring.yang:232: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:235: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:239: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:243: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:247: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:258: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:263: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
||||
| tailf-netconf-query@2014-11-13.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-netconf-query.yang --lint 2>&1": tailf-netconf-query.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-netconf-query.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-query.yang:38: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement tailf-netconf-query.yang:48: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement tailf-netconf-query.yang:53: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-netconf-query.yang:59: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement tailf-netconf-query.yang:65: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement |
Error: include of submodule 'tailf-meta-extensions' revision '2017-03-08' failed tailf-common.yang:5.3: error(236): module not found Error: include of submodule 'tailf-cli-extensions' revision '2017-08-23' failed tailf-common.yang:9.3: error(236): module not found |
|||
| tailf-rest-query@2014-11-13.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-rest-query.yang --lint 2>&1": tailf-rest-query.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-rest-query.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-rest-query.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement |
Error: include of submodule 'tailf-meta-extensions' revision '2017-03-08' failed tailf-common.yang:5.3: error(236): module not found Error: include of submodule 'tailf-cli-extensions' revision '2017-08-23' failed tailf-common.yang:9.3: error(236): module not found Warning: Module 'tailf-common-query' not used tailf-rest-query.yang:10.3: warning(1015): import not used |
|||
| tailf-webui@2013-03-07.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-webui.yang --lint 2>&1": tailf-webui.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-webui.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-webui.yang:25: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:28: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:30: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:32: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:35: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:39: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:41: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:45: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:49: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:53: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:58: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:61: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:64: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:69: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:70: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:74: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:78: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:82: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:86: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:90: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-webui.yang:93: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:95: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:97: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:104: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:105: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:109: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:110: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:112: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:122: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:124: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:130: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-webui.yang:132: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:133: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:135: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:137: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:138: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:140: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:151: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:154: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:159: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:164: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:169: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:176: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:182: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:190: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-webui.yang:191: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:195: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:201: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-webui.yang:202: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:206: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:210: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement |
||||
| tailf-xsd-types@2009-03-17.yang | FAILED | Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.2/yang" tailf-xsd-types.yang --lint 2>&1": tailf-xsd-types.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-xsd-types.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement tailf-xsd-types.yang:9: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-xsd-types.yang:14: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:20: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:26: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:32: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:38: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:44: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:50: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:56: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types.yang:62: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement |