Loading...
Loading...
A Cisco IOS-XE router may see an application error returned with a HTTP 400 response code (RESTCONF) and a operation-failed RPC reply (NETCONF-YANG) when using the Cisco-IOS-XE-install-rpc YANG model to add a .bin image, activate, and commit it: - A sample POST might looks like this for RESTCONF: curl -i -k -u ":" -X POST https:///restconf/operations/Cisco-IOS-XE-install-rpc:install \ -H "Accept:application/yang-data+json" \ -H "Content-Type: application/yang-data+json" \ -d '{"install":[{"uuid":"", "path":"bootflash:isr4300-universalk9.17.03.05.SPA.bin", "one-shot": "true", "reloadfast": "false"}]}' HTTP/1.1 400 Bad Request Server: nginx Content-Type: application/yang-data+json .... "error": [ { "error-message": "application error", "error-path": "/Cisco-IOS-XE-install-rpc:install", "error-tag": "malformed-message", "error-type": "application" } - A sample RPC call might look like this for NETCONF-YANG: "> bootflash:isr4300-universalk9.17.03.05.SPA.bin true false "> application operation-failed error /nc:rpc/install-ios-xe-rpc:install application errorinstall
This is applicable to IOS-XE routers using RESTCONF or NETCONF-YANG. This is not applicable to other catalyst switching platforms for the xfsu / one-shot upgrade process.
There are no complete workarounds at this time for the xfsu / one-shot upgrade process at this time. However, it is possible to achieve an upgrade programmatically using the Cisco-IOS-XE-native:native boot modules to change the boot statement. The trade off would be additional steps being required and this being only applicable for routers on BUNDLE mode (booted from a .bin image) instead of INSTALL mode (booted from .conf/packages file). Alternatively, the XFSU process can be achieved via the CLI: install add file bootflash: activate commit
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.