Troubleshooting
Problem
- Upgrade from v2018.4.1.13-ifix3.0 or earlier to v2018.4.1.19
Before upgrading to v2018.4.1.19, verifying the upgrade tarballs is important to ensure you have the correct archive and prevent appliance stuck while running the upgrade task. Should there be a problem with applying a wrong tarball, you can recover by running the workaround.
-
Issue while upgrading to v2018.4.1.16You may see in the appliance-manager log "helm rendered manifests contain a resource that already exists" and the upgrade may not be complete.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000CeCAAA0","label":"API Connect-\u003EManagement and Monitoring (MM)-\u003EUpgrade\/Downgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2018.4.1.0"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
18 March 2022
UID
ibm16564239