Troubleshooting Tip: FortiManager ADOM Upgrade Error ‘Fail(errno=170):Package copy failed’

[madhan]

Description	This article describes how to fix an issue where the user encounters the error message 'Fail(errno=170):Package copy failed’ during a FortiManager ADOM (Administrative Domain) upgrade.
Scope	FortiManager.
Solution	ADOM upgrade can fail with the error as in the image below: Error: Fail(errno=170):Package copy failed. object: router_bgp template. detail: failed to copy BGP_TEST Further details can be obtained through the debug steps as per the following KB article: Technical Tip: How to upgrade an ADOM on FortiManager. Run the commands according to the version. FortiManager Debug commands: In such a case, it is recommended to use the following CLI troubleshooting commands for FortiManager before v7.4.x: diagnose debug reset diagnose debug enable diagnose debug service cdb 255 For FortiManager v7.4 and above, use the following troubleshooting commands: diagnose debug reset diagnose debug enable diagnose debug service dvmdb 255 Perform the ADOM upgrade until it fails. Below are the details of the error: __copy_pkg_:d_parent=0, s_oid=6128, name="BGP_TEST" [cate: 550] copy template setting.router_bgp(soid=6129) to dparent=6128, [cate: 240] copy router bgp.(soid=6132) to dparent=6128, __do_cdb_node_attr_check error:router bgp.router-id  1.1.1.$(LAST_OCTET) --> commit [cate: 240] copy router bgp.(soid=6132) to dparent=6128,  fail: err=-999,invalid ip - prop[router-id]: ip4any(1.1.1.) invalid ip address Important details are noted down in bold for the output example: Template name is 'BGP_TEST'. The attribute that causes the error is bgp.router-id. Check the template with the attribute to see the error: The object used is a Metadata Variable, and there is no default value configured: Add a default value for the metadata variable 'LAST_OCTET', and ADOM can be upgraded successfully. Related article: Technical Tip: How to upgrade an ADOM on FortiManager