• Generated on 29/04/2025 by the YANG Catalog. Fujitsu https://github.com/FujitsuNetworkCommunications/FSS2-Yang/tree/master/FSS2-API-Yang/T400/1.1.2/yang

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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.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.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.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-ext@2016-04-05.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/standards/dhcp-client-ext.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: 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.1.2/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' 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.1.2/yang" dhcp-client-ext.yang 2>&1": dhcp-client-ext.yang:94: 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.1.2/yang/fujitsu-performance-monitoring.yang:34: 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.1.2/yang/fujitsu-system.yang:8: warning: imported module "fujitsu-entity-states" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-system.yang:20: warning: imported module "ietf-netconf-acm" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/third_party/tailf-aaa.yang:246: warning: the escape sequence "\h" 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.1.2/yang/third_party/tailf-common.yang:430: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:49: 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.1.2/yang/third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" dhcp-client-ext.yang --lint 2>&1": dhcp-client-ext.yang:6: warning: imported module "ietf-inet-types" not used dhcp-client-ext.yang:12: warning: imported module "ietf-interfaces" not used dhcp-client-ext.yang:15: warning: imported module "ietf-ip" not used dhcp-client-ext.yang:22: warning: imported module "fujitsu-system" not used dhcp-client-ext.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement dhcp-client-ext.yang:49: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement dhcp-client-ext.yang:50: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client-ext.yang:51: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client-ext.yang:57: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client-ext.yang:58: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client-ext.yang:61: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client-ext.yang:62: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client-ext.yang:66: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client-ext.yang:67: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client-ext.yang:80: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement dhcp-client-ext.yang:92: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client-ext.yang:93: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client-ext.yang:94: error: keyword "must" not in canonical order (see RFC 6020, Section 12) dhcp-client-ext.yang:99: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client-ext.yang:100: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client-ext.yang:101: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client-ext.yang:105: error: keyword "must" 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/standards/dhcp-client-ext.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "dhcp-client-ext" 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.1.2/yang/standards/dhcp-client-ext.yang 2>&1": Error: 'dhcp-client-ext.yang' import of module 'tailf-common' failed dhcp-client-ext.yang:18.3: error(236): module not found Error: 'dhcp-client-ext.yang' import of module 'fujitsu-system' failed dhcp-client-ext.yang:22.3: error(236): module not found Error: Module for prefix 'sys' not found dhcp-client-ext.yang:94.62: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' dhcp-client-ext.yang:54.9: error(236): module 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.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.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.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.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-ext@2016-04-05.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/standards/dhcpv6-client-ext.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: 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.1.2/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' 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.1.2/yang" dhcpv6-client-ext.yang 2>&1": dhcpv6-client-ext.yang:139: 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.1.2/yang/fujitsu-performance-monitoring.yang:34: 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.1.2/yang/fujitsu-system.yang:8: warning: imported module "fujitsu-entity-states" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-system.yang:20: warning: imported module "ietf-netconf-acm" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/third_party/tailf-aaa.yang:246: warning: the escape sequence "\h" 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.1.2/yang/third_party/tailf-common.yang:430: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:49: 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.1.2/yang/third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" dhcpv6-client-ext.yang --lint 2>&1": dhcpv6-client-ext.yang:12: warning: imported module "ietf-interfaces" not used dhcpv6-client-ext.yang:15: warning: imported module "ietf-ip" not used dhcpv6-client-ext.yang:22: warning: imported module "fujitsu-system" not used dhcpv6-client-ext.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement dhcpv6-client-ext.yang:61: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement dhcpv6-client-ext.yang:62: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcpv6-client-ext.yang:63: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcpv6-client-ext.yang:124: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement dhcpv6-client-ext.yang:139: error: keyword "must" not in canonical order (see RFC 6020, Section 12) dhcpv6-client-ext.yang:156: error: keyword "must" 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/standards/dhcpv6-client-ext.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "dhcpv6-client-ext" 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.1.2/yang/standards/dhcpv6-client-ext.yang 2>&1": Warning: top-level NP container 'serverv6' is mandatory dhcpv6-client.yang:135.5: warning(1048): top-level object is mandatory Warning: top-level NP container 'relayv6' is mandatory dhcpv6-client.yang:1430.5: warning(1048): top-level object is mandatory Error: 'dhcpv6-client-ext.yang' import of module 'tailf-common' failed dhcpv6-client-ext.yang:19.3: error(236): module not found Error: 'dhcpv6-client-ext.yang' import of module 'fujitsu-system' failed dhcpv6-client-ext.yang:22.3: error(236): module not found Error: Module for prefix 'sys' not found dhcpv6-client-ext.yang:139.60: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' dhcpv6-client-ext.yang:66.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' dhcpv6-client-ext.yang:82.13: error(236): module 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.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-access-control-list.yang 2>&1": fujitsu-access-control-list.yang:9: error: module 'ietf-access-control-list' not found fujitsu-access-control-list.yang:15: error: module 'iana-if-type' not found fujitsu-access-control-list.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.1.2/yang" fujitsu-access-control-list.yang 2>&1": fujitsu-access-control-list.yang:12: warning: imported module "ietf-yang-types" not used fujitsu-access-control-list.yang:51: error: "ietf-access-control-list:access-lists" in the path for acl-name at fujitsu-access-control-list.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.1.2/yang" fujitsu-access-control-list.yang --lint 2>&1": fujitsu-access-control-list.yang:9: warning: imported module "ietf-access-control-list" not used fujitsu-access-control-list.yang:12: warning: imported module "ietf-yang-types" not used fujitsu-access-control-list.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-access-control-list.yang:42: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-access-control-list.yang:49: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-access-control-list.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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-access-control-list.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "ietf-packet-fields" failed. libyang err : Loading "ietf-packet-fields" module failed. libyang err : Parsing module "ietf-access-control-list" failed. libyang err : Loading "ietf-access-control-list" module failed. libyang err : Parsing module "fujitsu-access-control-list" 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.1.2/yang/fujitsu-access-control-list.yang 2>&1": Error: 'fujitsu-access-control-list.yang' import of module 'ietf-access-control-list' failed fujitsu-access-control-list.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.yang:51.17: error(236): module not found Warning: Module 'ietf-yang-types' not used fujitsu-access-control-list.yang:12.3: warning(1015): import not used
fujitsu-ains-keywords@2016-07-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.1.2/yang" fujitsu-ains-keywords.yang --lint 2>&1": fujitsu-ains-keywords.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ains-keywords.yang:54: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ains-keywords.yang:55: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ains-keywords.yang:57: warning: RFC 8407: 4.4: statement "mandatory" is given with its default value "false" fujitsu-ains-keywords.yang:58: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ains-keywords.yang:60: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ains-keywords.yang:63: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
fujitsu-alarm-types@2017-02-06.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-alarm-types.yang 2>&1": fujitsu-alarm-types.yang:5: error: module 'ietf-alarms' not found fujitsu-alarm-types.yang:38: 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.1.2/yang" fujitsu-alarm-types.yang 2>&1": fujitsu-alarm-types.yang:38: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:44: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:48: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:52: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:56: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:60: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:64: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:68: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:72: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:76: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:80: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:84: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:88: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:92: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:96: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:100: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:104: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:108: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:112: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:116: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:120: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:124: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:128: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:132: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:136: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:140: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:144: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:148: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:152: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:156: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:160: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:164: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:168: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:172: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:176: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:180: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:184: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:188: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:192: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:196: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:200: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:204: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:208: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:212: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:216: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:220: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:224: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:228: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:232: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:236: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:240: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:244: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:248: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:252: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:256: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:260: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:264: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:268: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:272: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:276: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:280: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:284: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:288: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:292: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:296: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:300: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:304: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:308: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:312: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:316: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:320: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:324: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:328: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:332: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:336: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:340: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:344: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:348: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:352: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:356: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:360: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:364: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:368: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:372: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:376: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:380: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:384: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:388: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:392: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:396: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:400: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:404: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:408: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:412: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:416: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:420: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:424: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:428: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:432: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:436: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:440: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:444: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:448: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:452: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:456: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:460: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:464: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:468: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:472: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:476: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:480: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:484: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:488: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:492: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:496: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:500: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:504: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:508: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:512: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:516: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:520: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:524: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:528: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:532: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:536: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:540: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:544: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:548: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:552: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:556: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:560: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:564: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:568: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:572: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:576: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:580: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:584: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:588: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:592: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:596: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:600: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:604: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:608: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:612: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:616: 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.1.2/yang" fujitsu-alarm-types.yang --lint 2>&1": fujitsu-alarm-types.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:38: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:43: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:44: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:47: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:48: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:51: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:52: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:55: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:56: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:59: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:60: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:63: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:64: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:67: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:68: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:71: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:72: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:75: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:76: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:79: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:80: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:83: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:84: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:87: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:88: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:91: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:92: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:95: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:96: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:99: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:100: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:103: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:104: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:107: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:108: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:111: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:112: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:115: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:116: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:119: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:120: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:123: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:124: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:127: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:128: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:131: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:132: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:135: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:136: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:139: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:140: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:143: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:144: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:147: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:148: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:151: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:152: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:155: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:156: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:159: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:160: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:163: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:164: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:167: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:168: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:171: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:172: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:175: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:176: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:179: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:180: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:183: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:184: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:187: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:188: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:191: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:192: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:195: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:196: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:199: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:200: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:203: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:204: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:207: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:208: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:211: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:212: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:215: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:216: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:219: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:220: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:223: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:224: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:227: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:228: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:231: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:232: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:235: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:236: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:239: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:240: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:243: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:244: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:247: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:248: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:251: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:252: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:255: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:256: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:259: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:260: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:263: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:264: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:267: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:268: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:271: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:272: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:275: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:276: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:279: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:280: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:283: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:284: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:287: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:288: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:291: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:292: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:295: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:296: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:299: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:300: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:303: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:304: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:307: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:308: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:311: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:312: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:315: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:316: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:319: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:320: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:323: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:324: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:327: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:328: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:331: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:332: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:335: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:336: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:339: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:340: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:343: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:344: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:347: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:348: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:351: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:352: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:355: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:356: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:359: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:360: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:363: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:364: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:367: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:368: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:371: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:372: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:375: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:376: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:379: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:380: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:383: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:384: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:387: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:388: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:391: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:392: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:395: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:396: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:399: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:400: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:403: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:404: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:407: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:408: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:411: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:412: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:415: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:416: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:419: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:420: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:423: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:424: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:427: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:428: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:431: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:432: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:435: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:436: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:439: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:440: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:443: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:444: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:447: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:448: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:451: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:452: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:455: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:456: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:459: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:460: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:463: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:464: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:467: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:468: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:471: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:472: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:475: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:476: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:479: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:480: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:483: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:484: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:487: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:488: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:491: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:492: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:495: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:496: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:499: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:500: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:503: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:504: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:507: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:508: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:511: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:512: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:515: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:516: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:519: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:520: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:523: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:524: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:527: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:528: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:531: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:532: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:535: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:536: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:539: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:540: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:543: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:544: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:547: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:548: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:551: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:552: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:555: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:556: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:559: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:560: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:563: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:564: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:567: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:568: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:571: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:572: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:575: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:576: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:579: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:580: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:583: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:584: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:587: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:588: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:591: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:592: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:595: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:596: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:599: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:600: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:603: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:604: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:607: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:608: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:611: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:612: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:615: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:616: error: identity "alarm-identity" not found in module "ietf-alarms"		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.1.2/yang/fujitsu-alarm-types.yang 2>&1": Error: 'fujitsu-alarm-types.yang' import of module 'ietf-alarms' failed fujitsu-alarm-types.yang:5.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:43.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:47.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:51.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:55.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:59.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:63.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:67.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:71.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:75.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:79.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:83.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:87.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:91.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:95.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:99.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:103.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:107.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:111.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:115.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:119.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:123.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:127.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:131.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:135.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:139.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:143.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:147.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:151.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:155.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:159.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:163.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:167.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:171.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:175.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:179.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:183.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:187.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:191.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:195.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:199.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:203.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:207.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:211.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:215.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:219.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:223.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:227.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:231.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:235.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:239.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:243.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:247.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:251.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:255.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:259.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:263.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:267.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:271.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:275.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:279.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:283.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:287.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:291.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:295.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:299.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:303.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:307.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:311.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:315.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:319.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:323.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:327.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:331.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:335.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:339.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:343.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:347.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:351.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:355.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:359.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:363.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:367.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:371.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:375.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:379.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:383.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:387.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:391.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:395.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:399.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:403.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:407.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:411.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:415.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:419.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:423.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:427.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:431.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:435.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:439.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:443.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:447.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:451.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:455.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:459.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:463.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:467.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:471.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:475.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:479.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:483.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:487.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:491.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:495.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:499.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:503.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:507.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:511.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:515.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:519.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:523.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:527.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:531.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:535.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:539.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:543.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:547.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:551.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:555.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:559.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:563.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:567.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:571.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:575.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:579.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:583.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:587.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:591.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:595.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:599.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:603.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:607.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:611.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:615.3: error(236): module not found
fujitsu-alarms-ext@2015-05-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-alarms-ext.yang 2>&1": fujitsu-alarms-ext.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.1.2/yang" fujitsu-alarms-ext.yang --lint 2>&1": fujitsu-alarms-ext.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarms-ext.yang:35: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:38: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:41: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:44: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:53: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-alarms-ext.yang:90: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext.yang:103: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext.yang:107: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-alarms-ext.yang:129: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-alarms-ext.yang:193: 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/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-alarms-ext.yang 2>&1": Error: 'fujitsu-alarms-ext.yang' import of module 'ietf-alarms' failed fujitsu-alarms-ext.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.yang:60.12: error(250): definition not found Error: typedef definition for 'al:alarm-type-id' not found in module ietf-alarms fujitsu-alarms-ext.yang:148.14: error(250): definition not found Error: object 'alarms' not found in module fujitsu-alarms-ext in Xpath target /al:alarms fujitsu-alarms-ext.yang:129.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.yang:193.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.yang:107.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.yang:131.7: error(250): definition not found Error: invalid identifier in key for list 'alarm-severity-assignment' (alarm-type-id) fujitsu-alarms-ext.yang:131.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.yang:138.7: error(250): definition not found Error: invalid identifier in key for list 'severity-defaults' (alarm-type-id) fujitsu-alarms-ext.yang:138.7: error(250): definition not found
fujitsu-database@2015-09-28.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.1.2/yang" fujitsu-database.yang --lint 2>&1": fujitsu-database.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-database.yang:48: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-entity-states@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.1.2/yang" fujitsu-entity-states.yang --lint 2>&1": fujitsu-entity-states.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-states.yang:105: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-entity-states.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-entity-states.yang:111: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-entity-states.yang:112: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-entity-states.yang:117: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-entity-states.yang:124: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-entity-states.yang:127: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-eqpt-operations-dev@2017-02-22.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-eqpt-operations-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-eqpt-operations-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "fujitsu-eqpt-operations-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.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:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.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.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-eqpt-operations.yang --lint 2>&1": fujitsu-eqpt-operations.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations.yang:31: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-eqpt-operations.yang:42: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-eqpt-operations.yang:74: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-eqpt-operations.yang:102: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-eqpt-operations.yang:130: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations.yang:148: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations.yang:166: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations.yang:178: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement	libyang warn: Node "num-lanes" is not of a numeric type, but used where it was expected. libyang warn: Previous warning generated by XPath subexpression[3] "num-lanes > 1" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/subport".	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-equipment-dev@2017-01-25.yang	FAILED	fujitsu-equipment-dev.prod.yang:82: warning: the revision statements are not given in reverse chronological order fujitsu-equipment-dev.prod.yang:98: warning: Given dependencies are not equal to calculated: ./:cardType, ./:slotID, ../type. Consider removing tailf:dependency statements. /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-equipment-dev.prod.yang:14: warning: imported module "fujitsu-pm-types" not used fujitsu-equipment-dev.prod.yang:82: warning: the revision statements are not given in reverse chronological order fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" fujitsu-equipment-dev.prod.yang --lint 2>&1": 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: warning: the revision statements are not given in reverse chronological order fujitsu-equipment-dev.prod.yang:82: 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-equipment-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "fujitsu-equipment-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.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:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: 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@2015-05-07.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-equipment.yang --lint 2>&1": fujitsu-equipment.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment.yang:44: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-equipment.yang:49: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement	libyang warn: Node "num-lanes" is not of a numeric type, but used where it was expected. libyang warn: Previous warning generated by XPath subexpression[3] "num-lanes > 1" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/subport".	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
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.1.2/yang" fujitsu-factory.yang --lint 2>&1": fujitsu-factory.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
fujitsu-fwdl@2015-09-28.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-fwdl.yang --lint 2>&1": fujitsu-fwdl.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-fwdl.yang:31: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-fwdl.yang:86: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-fwdl.yang:204: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-fwdl.yang:216: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-fwdl.yang:234: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement	libyang warn: Node "num-lanes" is not of a numeric type, but used where it was expected. libyang warn: Previous warning generated by XPath subexpression[3] "num-lanes > 1" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/subport".	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
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.1.2/yang" fujitsu-gcc.yang --lint 2>&1": fujitsu-gcc.yang:72: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-if-type@2015-10-09.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.1.2/yang" fujitsu-if-type.yang --lint 2>&1": fujitsu-if-type.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-if-type.yang:38: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-if-type.yang:42: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-if-type.yang:46: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-if-type.yang:50: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
fujitsu-inventory@2014-12-02.yang	PASSED
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.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-lldp-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-lldp.yang:15: error: module 'iana-afn-safi' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-lldp.yang:47: 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.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:47: warning: the revision statements are not given in reverse chronological order fujitsu-lldp.yang:117: error: XPath function "re-match" is not defined in the XPath context third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-lldp-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "fujitsu-lldp" failed. libyang err : Loading "fujitsu-lldp" module failed. libyang err : Parsing module "fujitsu-lldp-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.1.2/yang/fujitsu-lldp-dev.prod.yang 2>&1": Error: 'fujitsu-lldp.yang' import of module 'iana-afn-safi' failed fujitsu-lldp.yang:15.3: error(236): module not found Error: 'fujitsu-lldp.yang' import of module 'tailf-common' failed fujitsu-lldp.yang:18.3: error(236): module not found Warning: revision dates not in descending order fujitsu-lldp.yang:47.3: warning(1035): bad revision-stmt order Error: typedef definition for 'ianaaf:address-family' not found in module iana-afn-safi fujitsu-lldp.yang:167.20: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:100.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:124.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:147.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:158.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:165.13: error(236): module 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(236): module not found Error: object 'lldp-instance' not found in path '/fjproto:protocols/fjproto:protocol/lldp:lldp-instance/lldp:port/lldp:adminStatus' fujitsu-lldp-dev.prod.yang:34.2: error(251): definition segment not found
fujitsu-lldp@2016-07-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-lldp.yang 2>&1": fujitsu-lldp.yang:15: error: module 'iana-afn-safi' not found fujitsu-lldp.yang:47: 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.1.2/yang" fujitsu-lldp.yang 2>&1": fujitsu-lldp.yang:6: warning: imported module "ietf-yang-types" not used fujitsu-lldp.yang:47: warning: the revision statements are not given in reverse chronological order fujitsu-lldp.yang:117: error: XPath function "re-match" is not defined in the XPath context third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" fujitsu-lldp.yang --lint 2>&1": fujitsu-lldp.yang:6: warning: imported module "ietf-yang-types" not used fujitsu-lldp.yang:47: warning: the revision statements are not given in reverse chronological order fujitsu-lldp.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:58: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-lldp.yang:81: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:89: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:97: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:106: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:112: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:117: error: XPath function "re-match" is not defined in the XPath context fujitsu-lldp.yang:144: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:151: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:156: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:157: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:164: error: RFC 8407: 4.14: statement "list" 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-lldp.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "fujitsu-lldp" 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.1.2/yang/fujitsu-lldp.yang 2>&1": Error: 'fujitsu-lldp.yang' import of module 'iana-afn-safi' failed fujitsu-lldp.yang:15.3: error(236): module not found Error: 'fujitsu-lldp.yang' import of module 'tailf-common' failed fujitsu-lldp.yang:18.3: error(236): module not found Warning: revision dates not in descending order fujitsu-lldp.yang:47.3: warning(1035): bad revision-stmt order Error: typedef definition for 'ianaaf:address-family' not found in module iana-afn-safi fujitsu-lldp.yang:167.20: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:100.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:124.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:147.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:158.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-lldp.yang:165.13: error(236): module not found Warning: Module 'ietf-yang-types' not used fujitsu-lldp.yang:6.3: warning(1015): import not used
fujitsu-log@2017-02-06.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-log.yang --lint 2>&1": fujitsu-log.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:54: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:65: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:69: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:107: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:111: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:151: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-log.yang:153: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-log.yang:190: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement fujitsu-log.yang:208: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:216: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-log.yang:234: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-log.yang:257: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement	libyang warn: Node "num-lanes" is not of a numeric type, but used where it was expected. libyang warn: Previous warning generated by XPath subexpression[3] "num-lanes > 1" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/subport".	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
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.1.2/yang" fujitsu-nat.yang --lint 2>&1": fujitsu-nat.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-nat.yang:42: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-nat.yang:70: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat.yang:86: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-nat.yang:116: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat.yang:131: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat.yang:149: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat.yang:165: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-nat.yang:195: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat.yang:210: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat.yang:228: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-nat.yang:256: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-nat.yang:293: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat.yang:312: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-nat.yang:331: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
fujitsu-notification-types@2016-09-28.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.1.2/yang" fujitsu-notification-types.yang --lint 2>&1": fujitsu-notification-types.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
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.1.2/yang" fujitsu-notifications.yang --lint 2>&1": fujitsu-notifications.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
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 /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-optical-tributary-signal.yang:41: 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-optical-tributary-signal.yang:41: 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.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:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-optical-tributary-signal.yang:41.3: warning(1035): bad revision-stmt order 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			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.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:8.3: warning(1015): import not used
fujitsu-optical-tributary-signal-group@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.1.2/yang" fujitsu-optical-tributary-signal-group.yang --lint 2>&1": fujitsu-optical-tributary-signal-group.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-group.yang:78: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group.yang:81: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:83: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:86: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:214: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:217: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:227: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:230: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:258: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:286: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:287: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:292: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-optical-tributary-signal@2015-04-10.yang	FAILED	fujitsu-optical-tributary-signal.yang:41: warning: the revision statements are not given in reverse chronological order	fujitsu-optical-tributary-signal.yang:41: 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.1.2/yang" fujitsu-optical-tributary-signal.yang --lint 2>&1": fujitsu-optical-tributary-signal.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:41: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:54: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal.yang:57: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal.yang:59: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:62: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:65: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:198: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-tributary-signal.yang:225: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-tributary-signal.yang:226: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal.yang:231: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-optical-tributary-signal.yang:41.3: warning(1035): bad revision-stmt order
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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-ospf.yang 2>&1": fujitsu-ospf.yang:5: error: module 'ietf-routing' not found fujitsu-ospf.yang:14: error: module 'ietf-ospf', revision '2015-03-09' 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.1.2/yang" fujitsu-ospf.yang 2>&1": fujitsu-ospf.yang:8: warning: imported module "ietf-yang-types" not used fujitsu-ospf.yang:11: warning: imported module "ietf-inet-types" not used fujitsu-ospf.yang:14: warning: imported module "ietf-ospf" not used fujitsu-ospf.yang:95: error: node ietf-routing::routing-instance is not found fujitsu-ospf.yang:158: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2045 (at standards/ietf-ospf.yang:606): 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:2227 (at standards/ietf-ospf.yang:606): 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:631: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" standards/ietf-ospf.yang:2259 (at standards/ietf-ospf.yang:1491): 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:2259 (at standards/ietf-ospf.yang:1500): 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:2276 (at standards/ietf-ospf.yang:1519): 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:2276 (at standards/ietf-ospf.yang:1528): 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:2292 (at standards/ietf-ospf.yang:1548): 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:2292 (at standards/ietf-ospf.yang:1556): 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:2014 (at standards/ietf-ospf.yang:1656): warning: node "ietf-routing::routing-instance" is not found in "ietf-routing::routing" standards/ietf-ospf.yang:1924: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:1969: error: type "routing-instance-ref" not found in module "ietf-routing" standards/ietf-ospf.yang:2083: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2102: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2100 is not found standards/ietf-ospf.yang:2122: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2143: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2141 is not found standards/ietf-ospf.yang:2164: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2190: error: type "routing-instance-ref" not found in module "ietf-routing" standards/ietf-ospf.yang:2243: 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:2301: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2326: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2324 is not found standards/ietf-ospf.yang:2346: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2368: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2366 is not found standards/ietf-ospf.yang:2416: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2456: error: type "routing-instance-ref" not found in module "ietf-routing" third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" fujitsu-ospf.yang --lint 2>&1": fujitsu-ospf.yang:8: warning: imported module "ietf-yang-types" not used fujitsu-ospf.yang:11: warning: imported module "ietf-inet-types" not used fujitsu-ospf.yang:14: warning: imported module "ietf-ospf" not used fujitsu-ospf.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ospf.yang:50: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-ospf.yang:55: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ospf.yang:70: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf.yang:78: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf.yang:87: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-ospf.yang:88: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf.yang:95: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ospf.yang:95: error: node ietf-routing::routing-instance is not found fujitsu-ospf.yang:100: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ospf.yang:158: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ospf.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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-ospf.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "ietf-ospf" failed. libyang err : Loading "ietf-ospf" module failed. libyang err : Parsing module "fujitsu-ospf" 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.1.2/yang/fujitsu-ospf.yang 2>&1": Error: 'fujitsu-ospf.yang' import of module 'ietf-ospf' revision '2015-03-09' failed fujitsu-ospf.yang:14.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' fujitsu-ospf.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.yang:158.3: error(251): definition segment not found Warning: Module 'ietf-yang-types' not used fujitsu-ospf.yang:8.3: warning(1015): import not used Warning: Module 'ietf-inet-types' not used fujitsu-ospf.yang:11.3: warning(1015): import not used Warning: Module 'ietf-ospf' not used fujitsu-ospf.yang:14.3: warning(1015): import not used
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.1.2/yang" fujitsu-otn.yang --lint 2>&1": fujitsu-otn.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn.yang:41: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:50: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:59: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:68: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:119: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn.yang:137: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn.yang:145: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn.yang:166: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn.yang:201: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn.yang:209: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-otn.yang:221: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used
fujitsu-performance-monitoring-dev@2016-12-14.yang	FAILED	fujitsu-performance-monitoring-dev.prod.yang:40:21: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:41:50: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:41:54: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:41:58: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:41:62: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:42:23: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:42:27: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:42:31: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:42:35: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:42:39: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:43:19: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:43:23: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:43:27: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:43:31: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:43:35: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:44:19: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:44:23: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:44:27: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:44:31: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:44:35: warning: illegal character after \ fujitsu-performance-monitoring-dev.prod.yang:44:39: warning: illegal character after \ /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring-dev.prod.yang:5: warning: imported module "tailf-common" not used fujitsu-performance-monitoring-dev.prod.yang:40: 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:41: 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:42: 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:43: 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:44: 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:34: warning: the revision statements are not given in reverse chronological order third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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:40: 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:41: 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:42: 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:43: 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:44: 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\S'. (Line number 40.) 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.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: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'tailf-common' not used fujitsu-performance-monitoring-dev.prod.yang:5.5: warning(1015): import not used
fujitsu-performance-monitoring@2015-05-07.yang	FAILED	fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-performance-monitoring.yang --lint 2>&1": fujitsu-performance-monitoring.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order fujitsu-performance-monitoring.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring.yang:118: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring.yang:131: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring.yang:161: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring.yang:182: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring.yang:197: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:198: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:201: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:204: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:209: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:210: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring.yang:211: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:216: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:225: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:226: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring.yang:228: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:241: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:243: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:244: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:246: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:248: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:249: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:254: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:255: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring.yang:257: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring.yang:259: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:262: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:263: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:264: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:270: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:274: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:276: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:284: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:286: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:289: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring.yang:292: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:295: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:303: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:306: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:312: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:313: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring.yang:317: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:321: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:355: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:356: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring.yang:360: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:364: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring.yang:376: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:380: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:383: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:384: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:390: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:393: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:394: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:400: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:403: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:404: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:410: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:413: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:414: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:420: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:423: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:424: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:436: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:440: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:443: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:444: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:459: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:463: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:469: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:482: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:488: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)		Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order
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.1.2/yang" fujitsu-physical-inventory.yang --lint 2>&1": fujitsu-physical-inventory.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-physical-inventory.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-pm-types@2016-10-09.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-pm-types.yang --lint 2>&1": fujitsu-pm-types.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:39: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:43: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:47: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:51: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:55: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:59: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:63: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:67: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:71: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:75: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:79: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:83: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:87: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:91: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:95: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:99: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:103: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:107: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:111: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:115: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:119: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:123: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:127: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:131: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:135: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:139: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:143: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:147: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:151: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:155: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:159: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:163: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:167: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:171: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:175: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:179: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:183: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:187: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:191: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:195: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:199: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:203: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:207: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:211: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:215: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:219: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:223: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:227: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:231: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:235: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:239: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:243: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:247: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:251: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:255: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:259: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:263: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:267: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:271: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:275: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:279: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:283: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:287: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:291: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:295: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:299: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:303: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:307: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:311: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:315: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:319: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:323: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:327: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:331: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:335: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:339: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:343: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:347: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:351: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:355: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:359: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:363: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:367: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:371: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:375: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:379: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:383: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:387: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:391: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:395: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:399: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:403: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:407: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:411: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:415: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:419: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:423: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:427: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:431: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:435: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:439: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:443: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:447: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:451: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:455: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:459: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:463: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:467: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:471: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:475: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:479: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:483: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:487: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:491: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:495: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:499: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:503: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:507: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:511: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:515: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:519: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:523: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:527: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:531: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:535: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:539: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:543: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:547: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:551: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:555: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:559: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:563: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:567: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:571: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:575: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:579: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:583: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:587: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:591: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:595: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:599: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:603: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:607: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:611: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:615: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:619: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:623: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:627: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:631: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:635: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:639: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:643: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:647: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:651: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:655: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement		Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order
fujitsu-port@2017-02-21.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-port.yang --lint 2>&1": fujitsu-port.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port.yang:45: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-port.yang:70: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-port.yang:73: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order
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.1.2/yang" fujitsu-protocols.yang --lint 2>&1": fujitsu-protocols.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.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.1.2/yang/third_party/tailf-aaa.yang:246: warning: the escape sequence "\h" 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.1.2/yang/third_party/tailf-common.yang:430: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:49: 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.1.2/yang/third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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-shelf@2015-04-10.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-shelf.yang --lint 2>&1": fujitsu-shelf.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-shelf.yang:59: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-shelf.yang:103: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:108: error: keyword "units" not in canonical order (see RFC 6020, Section 12) fujitsu-shelf.yang:110: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:118: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:138: error: keyword "key" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order
fujitsu-slot@2015-04-10.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-slot.yang --lint 2>&1": fujitsu-slot.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot.yang:65: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-slot.yang:91: error: keyword "key" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order
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.1.2/yang" fujitsu-ssh-host-key.yang --lint 2>&1": fujitsu-ssh-host-key.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ssh-host-key.yang:26: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-ssh-host-key.yang:36: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-ssh-host-key.yang:54: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ssh-host-key.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.1.2/yang" fujitsu-state-timer.yang --lint 2>&1": fujitsu-state-timer.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-state-timer.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-subport@2015-09-25.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-subport.yang --lint 2>&1": fujitsu-subport.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subport.yang:43: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-subport.yang:71: error: keyword "default" not in canonical order (see RFC 6020, Section 12)		Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-subslot@2015-04-10.yang	FAILED	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order	fujitsu-performance-monitoring.yang:34: 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.1.2/yang" fujitsu-subslot.yang --lint 2>&1": fujitsu-subslot.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subslot.yang:59: error: keyword "default" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order
fujitsu-swdl@2015-09-28.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.1.2/yang" fujitsu-swdl.yang --lint 2>&1": fujitsu-swdl.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:53: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-swdl.yang:173: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-swdl.yang:204: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement
fujitsu-system-dev@2017-02-03.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-system-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: 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.1.2/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:8: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:20: warning: imported module "ietf-netconf-acm" not used fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used third_party/tailf-aaa.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-system-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" 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.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:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:41.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors 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:9.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:58.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:23.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:26.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:29.3: error(236): module not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:486.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:594.16: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:247.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:292.7: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-system.yang:523.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:8.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:20.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:38.2: error(250): definition not found
fujitsu-system@2017-02-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-system.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-performance-monitoring.yang:34: 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.1.2/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-system.yang:8: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:20: warning: imported module "ietf-netconf-acm" not used fujitsu-performance-monitoring.yang:34: warning: the revision statements are not given in reverse chronological order fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used third_party/tailf-aaa.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" fujitsu-system.yang --lint 2>&1": fujitsu-system.yang:8: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:20: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:69: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:73: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:81: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:85: 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:239: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-system.yang:342: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:349: error: keyword "default" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:350: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:386: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:438: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:463: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:505: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:518: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:519: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-system.yang:593: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-system.yang:594: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:615: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:622: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:624: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:648: error: keyword "units" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:667: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:724: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-system.yang:725: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:727: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:757: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:766: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:767: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:785: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:786: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:796: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:797: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:815: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:816: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:845: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:850: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-system.yang:860: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:870: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:877: 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-system.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" 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.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:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-performance-monitoring.yang:34.3: warning(1035): bad revision-stmt order Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:41.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors 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:9.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:58.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:23.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:26.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:29.3: error(236): module not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:486.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:594.16: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:247.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' fujitsu-system.yang:292.7: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-system.yang:523.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:8.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:20.3: warning(1015): import not used
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.1.2/yang" fujitsu-telemetry.yang --lint 2>&1": fujitsu-telemetry.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-telemetry.yang:25: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-telemetry.yang:36: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-telemetry.yang:39: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
fujitsu-user-security-dev@2015-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.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.1.2/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used third_party/tailf-aaa.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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:34: 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-user-security-dev.prod.yang 2>&1": libyang err : Double-quoted string unknown special character '\h'. (Line number 246.) libyang err : Parsing module "tailf-aaa" failed. libyang err : Loading "tailf-aaa" 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.1.2/yang/fujitsu-user-security-dev.prod.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:41.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.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(332): imported module has errors Warning: revision with same date on line 29 fujitsu-user-security-dev.prod.yang:34.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:51.1: error(250): definition not found Error: object 'security' not found in module fujitsu-user-security-dev.prod in Xpath target /fuser:security/fuser:systemwide/fuser:authentication-order fujitsu-user-security-dev.prod.yang:51.1: error(250): definition not found
fujitsu-user-security-typedefs@2016-11-04.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.1.2/yang" fujitsu-user-security-typedefs.yang --lint 2>&1": fujitsu-user-security-typedefs.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:29: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:31: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:34: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:40: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:42: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:45: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:86: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:155: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:173: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:192: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:232: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:244: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:247: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:250: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:278: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:284: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:286: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:289: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:292: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
fujitsu-user-security@2016-11-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-user-security.yang 2>&1": fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used third_party/tailf-aaa.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" fujitsu-user-security.yang --lint 2>&1": fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used fujitsu-user-security.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:41: error: RFC 8407: 4.10: top-level node security must not be mandatory fujitsu-user-security.yang:44: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security.yang:45: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:49: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:53: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:57: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:61: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:68: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security.yang:69: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:72: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:80: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:83: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:86: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:89: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:111: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:114: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:117: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:120: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement fujitsu-user-security.yang:121: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:122: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:126: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security.yang:127: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:130: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:133: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:136: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:144: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:145: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:148: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:155: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:156: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:157: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:160: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:162: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:165: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:167: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:168: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:170: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:173: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:175: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:176: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:178: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:181: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:184: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:191: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:194: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-user-security.yang:196: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:197: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:201: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:204: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:207: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:208: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:211: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:214: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:228: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:234: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:240: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:246: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security.yang:249: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security.yang:264: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-user-security.yang:266: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:271: error: RFC 8407: 4.14: statement "leaf-list" 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/fujitsu-user-security.yang 2>&1": libyang err : Double-quoted string unknown special character '\h'. (Line number 246.) libyang err : Parsing module "tailf-aaa" failed. libyang err : Loading "tailf-aaa" module failed. libyang err : Parsing module "fujitsu-user-security" 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.1.2/yang/fujitsu-user-security.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:41.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used
iana-afn-safi@2013-07-04.yang	PASSED
iana-crypt-hash@2014-04-04.yang	PASSED
iana-if-type@2014-09-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.1.2/yang" iana-if-type.yang --lint 2>&1": iana-if-type.yang:49: 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:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:64: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:82: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:85: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:88: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:91: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:94: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:118: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:121: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:124: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:137: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:140: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:143: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:146: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:151: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:156: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:191: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:194: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:202: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:244: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:274: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:285: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:290: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:293: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:296: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:307: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:310: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:313: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:326: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:329: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
ietf-access-control-list-dev@2016-01-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.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.1.2/yang" ietf-access-control-list-dev.yang 2>&1": ietf-access-control-list-dev.yang:31: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:37: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:43: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:51: 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:65: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:69: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:73: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:77: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:81: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:85: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:89: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:93: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:97: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:101: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:105: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:109: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:113: 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.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:31: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:37: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:43: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:51: 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:65: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:69: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:73: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:77: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:81: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:85: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:89: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:93: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:97: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:101: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:105: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:109: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:113: error: node ietf-access-control-list::access-lists 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/ietf-access-control-list-dev.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "ietf-packet-fields" failed. libyang err : Loading "ietf-packet-fields" module failed. libyang err : Parsing module "ietf-access-control-list" failed. libyang err : Loading "ietf-access-control-list" module failed. libyang err : Parsing module "ietf-access-control-list-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.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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:116.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.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.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.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.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.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-03.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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.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.1.2/yang" ietf-alarms-dev.yang 2>&1": ietf-alarms-dev.yang:33: error: node ietf-alarms::shelved-alarms is not found ietf-alarms-dev.yang:37: error: node ietf-alarms::cleared is not found ietf-alarms-dev.yang:41: error: node ietf-alarms::cleared-not-closed is not found ietf-alarms-dev.yang:45: error: node ietf-alarms::cleared-closed is not found ietf-alarms-dev.yang:49: error: node ietf-alarms::not-cleared-closed is not found ietf-alarms-dev.yang:53: error: node ietf-alarms::not-cleared-not-closed is not found ietf-alarms-dev.yang:62: error: node ietf-alarms::related-alarms is not found ietf-alarms-dev.yang:66: error: node ietf-alarms::impacted-resources is not found ietf-alarms-dev.yang:70: error: node ietf-alarms::root-cause-resources is not found ietf-alarms-dev.yang:82: error: node ietf-alarms::last-operator-state is not found ietf-alarms-dev.yang:85: error: node ietf-alarms::last-operator is not found ietf-alarms-dev.yang:89: error: node ietf-alarms::last-operator-text is not found ietf-alarms-dev.yang:92: error: node ietf-alarms::last-operator-action is not found ietf-alarms-dev.yang:99: error: node ietf-alarms::operator-action is not found ietf-alarms-dev.yang:103: error: node ietf-alarms::compress is not found ietf-alarms-dev.yang:107: error: node ietf-alarms::compress-alarms is not found ietf-alarms-dev.yang:111: error: node ietf-alarms::set-operator-state is not found ietf-alarms-dev.yang:115: error: node ietf-alarms::purge-alarms is not found ietf-alarms-dev.yang:119: 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.1.2/yang" ietf-alarms-dev.yang --lint 2>&1": ietf-alarms-dev.yang:33: error: node ietf-alarms::shelved-alarms is not found ietf-alarms-dev.yang:37: error: node ietf-alarms::cleared is not found ietf-alarms-dev.yang:41: error: node ietf-alarms::cleared-not-closed is not found ietf-alarms-dev.yang:45: error: node ietf-alarms::cleared-closed is not found ietf-alarms-dev.yang:49: error: node ietf-alarms::not-cleared-closed is not found ietf-alarms-dev.yang:53: error: node ietf-alarms::not-cleared-not-closed is not found ietf-alarms-dev.yang:62: error: node ietf-alarms::related-alarms is not found ietf-alarms-dev.yang:66: error: node ietf-alarms::impacted-resources is not found ietf-alarms-dev.yang:70: error: node ietf-alarms::root-cause-resources is not found ietf-alarms-dev.yang:82: error: node ietf-alarms::last-operator-state is not found ietf-alarms-dev.yang:85: error: node ietf-alarms::last-operator is not found ietf-alarms-dev.yang:89: error: node ietf-alarms::last-operator-text is not found ietf-alarms-dev.yang:92: error: node ietf-alarms::last-operator-action is not found ietf-alarms-dev.yang:99: error: node ietf-alarms::operator-action is not found ietf-alarms-dev.yang:103: error: node ietf-alarms::compress is not found ietf-alarms-dev.yang:107: error: node ietf-alarms::compress-alarms is not found ietf-alarms-dev.yang:111: error: node ietf-alarms::set-operator-state is not found ietf-alarms-dev.yang:115: error: node ietf-alarms::purge-alarms is not found ietf-alarms-dev.yang:119: 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.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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:128.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.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@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@2014-06-16.yang	PASSED
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.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.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.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.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@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.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.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.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.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.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.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 "" not found; in expr "../confirm-event" with context node "/ietf-netconf-notifications:netconf-confirmed-commit".	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@2011-06-01.yang	PASSED
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.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.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.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.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.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-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.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@2016-11-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/ietf-syslog-dev.yang 2>&1": ietf-syslog-dev.yang:81: error: unexpected keyword 'mandatory' ietf-syslog-dev.yang:133: 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.1.2/yang" ietf-syslog-dev.yang 2>&1": ietf-syslog-dev.yang:81: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" ietf-syslog-dev.yang:133: 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.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:45: 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:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:81: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" ietf-syslog-dev.yang:133: 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/ietf-syslog-dev.yang 2>&1": libyang err : Deviate "delete" does not support keyword "mandatory". (Line number 81.) 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.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:81.5: error(347): invalid deviate sub-clause Error: mandatory-stmt cannot be deleted ietf-syslog-dev.yang:133.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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:158.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.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-smiv2@2011-11-25.yang	PASSED
ietf-yang-types@2013-07-15.yang	PASSED
iputil@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.1.2/yang" iputil@2015-04-10.yang --lint 2>&1": iputil@2015-04-10.yang:1: warning: RFC 8407: 4.1: no module name prefix string used iputil@2015-04-10.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iputil@2015-04-10.yang:27: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil@2015-04-10.yang:29: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:32: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:38: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:41: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:44: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil@2015-04-10.yang:45: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:49: error: RFC 8407: 4.14: statement "container" must have a "description" substatement iputil@2015-04-10.yang:50: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:53: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:59: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil@2015-04-10.yang:61: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:66: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:69: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:72: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil@2015-04-10.yang:73: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:77: error: RFC 8407: 4.14: statement "container" must have a "description" substatement iputil@2015-04-10.yang:78: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:81: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:87: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil@2015-04-10.yang:89: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:97: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:100: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil@2015-04-10.yang:101: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:107: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil@2015-04-10.yang:109: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:114: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:117: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil@2015-04-10.yang:120: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil@2015-04-10.yang:121: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
net-ospf@2015-11-04.yang	FAILED	./ietf-ospf.yang:501: warning: Given dependencies are not equal to calculated: ../dead-interval, ../hello-interval. Consider removing tailf:dependency statements. ./ietf-ospf.yang:501: warning: Given dependencies are not equal to calculated: ../dead-interval, ../hello-interval. Consider removing tailf:dependency statements. ./ietf-ospf.yang:501: warning: Given dependencies are not equal to calculated: ../dead-interval, ../hello-interval. Consider removing tailf:dependency statements. ./ietf-ospf.yang:501: warning: Given dependencies are not equal to calculated: ../dead-interval, ../hello-interval. Consider removing tailf:dependency statements. ./ietf-ospf.yang:606: warning: Given dependencies are not equal to calculated: ../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:606: warning: Given dependencies are not equal to calculated: ../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:606: warning: Given dependencies are not equal to calculated: ../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:606: warning: Given dependencies are not equal to calculated: ../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:756: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:756: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:756: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:825: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:825: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:825: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:845: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:845: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:845: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:874: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:874: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:874: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:924: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:924: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:924: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1133: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1133: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1133: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1195: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1195: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1195: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1211: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1211: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1211: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1225: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1225: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1225: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1244: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1244: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1244: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1255: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1255: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1255: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1265: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1265: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1265: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1298: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1298: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1298: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1411: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1411: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1411: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1424: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1424: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1424: warning: Given dependencies are not equal to calculated: ../../header/:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1491: warning: Given dependencies are not equal to calculated: ../../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1500: warning: Given dependencies are not equal to calculated: ../../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1519: warning: Given dependencies are not equal to calculated: ../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1528: warning: Given dependencies are not equal to calculated: ../../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1548: warning: Given dependencies are not equal to calculated: ../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1556: warning: Given dependencies are not equal to calculated: ../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1627: warning: Given dependencies are not equal to calculated: ../area-type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1627: warning: Given dependencies are not equal to calculated: ../area-type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1640: warning: Given dependencies are not equal to calculated: ../area-type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1640: warning: Given dependencies are not equal to calculated: ../area-type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:1925: warning: Given dependencies are not equal to calculated: ../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2028: warning: Given dependencies are not equal to calculated: ../area-id, ../area-type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2084: warning: Given dependencies are not equal to calculated: ../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2123: warning: Given dependencies are not equal to calculated: ../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2165: warning: Given dependencies are not equal to calculated: ../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2243: warning: Given dependencies are not equal to calculated: ../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2302: warning: Given dependencies are not equal to calculated: ../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2347: warning: Given dependencies are not equal to calculated: ../../../../../rt:type. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2417: warning: Given dependencies are not equal to calculated: ../rt:source-protocol. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2417: warning: Given dependencies are not equal to calculated: ../rt:source-protocol. Consider removing tailf:dependency statements. ./ietf-ospf.yang:2417: warning: Given dependencies are not equal to calculated: ../rt:source-protocol. Consider removing tailf:dependency statements.	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.1.2/yang" net-ospf.yang 2>&1": net-ospf.yang:70 (at net-ospf.yang:55): error: the statement "when" cannot be given for a key net-ospf.yang:68: error: node ietf-routing::routing-instance is not found net-ospf.yang:71: warning: node "ietf-ospf::af" is not found in "net-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" ietf-ospf.yang:2045 (at ietf-ospf.yang:606): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf.yang:2227 (at ietf-ospf.yang:606): 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.yang:631: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" ietf-ospf.yang:2259 (at ietf-ospf.yang:1491): 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.yang:2259 (at ietf-ospf.yang:1500): 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.yang:2276 (at ietf-ospf.yang:1519): 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.yang:2276 (at ietf-ospf.yang:1528): 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.yang:2292 (at ietf-ospf.yang:1548): 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.yang:2292 (at ietf-ospf.yang:1556): 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.yang:2014 (at ietf-ospf.yang:1656): warning: node "ietf-routing::routing-instance" is not found in "ietf-routing::routing" ietf-ospf.yang:1924: error: node ietf-routing::routing-instance is not found ietf-ospf.yang:1969: error: type "routing-instance-ref" not found in module "ietf-routing" ietf-ospf.yang:2083: error: node ietf-routing::routing-instance is not found ietf-ospf.yang:2102: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf.yang:2100 is not found ietf-ospf.yang:2122: error: node ietf-routing::routing-instance is not found ietf-ospf.yang:2143: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf.yang:2141 is not found ietf-ospf.yang:2164: error: node ietf-routing::routing-instance is not found ietf-ospf.yang:2190: error: type "routing-instance-ref" not found in module "ietf-routing" ietf-ospf.yang:2243: 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.yang:2301: error: node ietf-routing::routing-instance is not found ietf-ospf.yang:2326: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf.yang:2324 is not found ietf-ospf.yang:2346: error: node ietf-routing::routing-instance is not found ietf-ospf.yang:2368: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf.yang:2366 is not found ietf-ospf.yang:2416: error: node ietf-routing::routing-instance is not found ietf-ospf.yang:2456: 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.1.2/yang/third_party/tailf-common.yang:430: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:49: 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.1.2/yang/third_party/tailf-meta-extensions.yang:50: warning: the escape sequence "\d" 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: 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.1.2/yang/third_party/tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" net-ospf.yang --lint 2>&1": net-ospf.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement net-ospf.yang:38: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" net-ospf.yang:42: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" net-ospf.yang:47: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" net-ospf.yang:51: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" net-ospf.yang:70 (at net-ospf.yang:55): error: the statement "when" cannot be given for a key net-ospf.yang:57: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" net-ospf.yang:68: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement net-ospf.yang:68: error: node ietf-routing::routing-instance is not found net-ospf.yang:71: warning: node "ietf-ospf::af" is not found in "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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/standards/net-ospf.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "ietf-ospf" failed. libyang err : Loading "ietf-ospf" module failed. libyang err : Parsing module "net-ospf" 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.1.2/yang/standards/net-ospf.yang 2>&1": Error: 'ietf-ospf.yang' import of module 'tailf-common' failed ietf-ospf.yang:6.3: error(236): module not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /usr/share/yumapro/modules/ietf/RFC/ietf-routing.yang ietf-ospf.yang:1969.16: error(250): definition not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /usr/share/yumapro/modules/ietf/RFC/ietf-routing.yang ietf-ospf.yang:2190.16: error(250): definition not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /usr/share/yumapro/modules/ietf/RFC/ietf-routing.yang ietf-ospf.yang:2456.12: error(250): definition not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:502.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:607.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:757.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:826.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:847.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:876.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:928.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1134.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1196.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1212.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1226.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1245.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1256.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1266.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1299.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1414.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1427.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1492.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1501.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1520.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1529.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1549.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1557.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1628.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1641.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:1926.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2030.15: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2086.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2124.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2166.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2244.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2303.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2348.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-ospf.yang:2419.7: error(236): module not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf.yang:1923.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.yang:2163.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.yang:2082.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.yang:2299.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.yang:2416.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.yang:2120.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' ietf-ospf.yang:2344.3: error(251): definition segment not found Error: object 'routing-instance' not found in module ietf-ospf in Xpath target routing-instance ietf-ospf.yang:1965.9: error(250): definition not found Error: invalid identifier in key for list 'instance' (routing-instance) ietf-ospf.yang:1965.9: error(250): definition not found Error: object 'routing-instance' not found in module ietf-ospf in Xpath target routing-instance ietf-ospf.yang:2186.9: error(250): definition not found Error: invalid identifier in key for list 'instance' (routing-instance) ietf-ospf.yang:2186.9: error(250): definition not found Error: 'net-ospf.yang' import of module 'ietf-ospf' revision '2015-03-09' failed net-ospf.yang:13.3: error(250): definition not found Error: Module for prefix 'ospf' not found net-ospf.yang:71.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' net-ospf.yang:68.3: error(251): definition segment not found
tailf-aaa@2015-06-16.yang	FAILED	tailf-aaa.yang:246:20: warning: illegal character after \	tailf-aaa.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" tailf-aaa.yang --lint 2>&1": tailf-aaa.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-aaa.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:72: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa.yang:82: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa.yang:87: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa.yang:92: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa.yang:97: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa.yang:100: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa.yang:105: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa.yang:111: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa.yang:113: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-aaa.yang:114: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-aaa.yang:118: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-aaa.yang:119: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:123: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:127: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:135: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:143: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:147: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:151: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:155: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:161: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa.yang:164: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa.yang:166: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa.yang:168: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:170: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:174: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:179: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:184: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:188: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:194: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:205: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:211: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:217: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:228: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa.yang:232: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:235: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:238: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:241: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:244: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.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.yang:250: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:252: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:255: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:259: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:262: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:264: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:272: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:276: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:281: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:289: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa.yang:295: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:300: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:303: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:307: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa.yang:310: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.yang:315: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa.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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/third_party/tailf-aaa.yang 2>&1": libyang err : Double-quoted string unknown special character '\h'. (Line number 246.) libyang err : Parsing module "tailf-aaa" failed.
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.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.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@2016-05-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.1.2/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/third_party/tailf-common.yang 2>&1": /opt/confd/src/confd/yang/tailf-cli-extensions.yang:0: error: expected revision '2016-05-04', got '2021-12-17' /opt/confd/src/confd/yang/tailf-meta-extensions.yang:0: error: expected revision '2013-11-07', got '2017-03-08' tailf-common.yang:430:12: warning: illegal character after \ tailf-common.yang:430:19: warning: illegal character after \ tailf-common.yang:430:26: warning: illegal character after \ tailf-common.yang:430:33: warning: illegal character after \	tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang" tailf-common.yang --lint 2>&1": tailf-common.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-common.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:72: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:79: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:86: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:94: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:101: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:110: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:127: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:134: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:147: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:154: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:161: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:176: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:184: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:191: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:196: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:204: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:220: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:227: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:243: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:250: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:259: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:266: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:273: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:283: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:294: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:301: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:309: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:316: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:333: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:342: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:365: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:376: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:395: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:407: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:415: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:683: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:684: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:685: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:686: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:687: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:688: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1047: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1048: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1049: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1083: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1084: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1085: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1120: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1121: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:2868: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:2869: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:2870: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3391: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3392: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3393: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-cli-extensions.yang:1: error: RFC 8407: 4.8: statement "submodule" must have a "contact" substatement tailf-cli-extensions.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:60: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:69: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:87: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:97: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:105: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:112: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:122: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:131: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:139: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:146: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:166: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:173: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:189: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:198: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:208: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:232: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:1733: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-cli-extensions.yang:1734: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-cli-extensions.yang:1735: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:1: error: RFC 8407: 4.8: statement "submodule" must have a "contact" substatement tailf-meta-extensions.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:35: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-meta-extensions.yang:41: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-meta-extensions.yang:47: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/third_party/tailf-common.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed.
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.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-netconf-monitoring@2014-11-13.yang	FAILED		tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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:127: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:137: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-netconf-monitoring.yang:161: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:162: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:163: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:180: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:198: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:205: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-netconf-monitoring.yang:207: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:210: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:214: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:218: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:222: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:233: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:238: 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.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/third_party/tailf-netconf-monitoring.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "tailf-netconf-monitoring" failed.
tailf-webui@2013-03-07.yang	FAILED		tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-common.yang:430: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:49: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:50: warning: the escape sequence "\d" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\." is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-meta-extensions.yang:52: warning: the escape sequence "\d" 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.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	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T400/1.1.2/yang/third_party/tailf-webui.yang 2>&1": libyang err : Double-quoted string unknown special character '\d'. (Line number 430.) libyang err : Parsing module "tailf-common" failed. libyang err : Loading "tailf-common" module failed. libyang err : Parsing module "tailf-webui" failed.
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.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