Troubleshooting
Problem
Portal subsystem is stuck at the SETUP_SUBSYSTEM, when upgrading to 2018.4.1.17.
Type: BOOTSTRAP_MASTER
Install stage: SETUP_SUBSYSTEM
Upgrade stage: UPGRADE_DONE
Subsystem type: portal
Subsystem version: 2018.4.1.17
Subsystem detail: Running helm upgrade
Diagnosing The Problem
You see this error in the syslog:
level=debug msg="Error: UPGRADE FAILED: rendered manifests contain a resource that exists. Unable to continue with update: Ingress \"apic-portal-apic-portal-director\" in namespace \"default\" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key \"app.kubernetes.io/managed-by\": must be set to \"Helm\"; annotation validation error: missing key \"meta.helm.sh/release-name\": must be set to \"apic-portal\"; annotation validation error: missing key \"meta.helm.sh/release-namespace\": must be set to \"default\"\n"
Resolving The Problem
To resolve this issue, delete the portal ingresses:
kubectl delete ing apic-portal-apic-portal-director -n <namespace>
kubectl delete ing apic-portal-apic-portal-web -n <namespace>
Note: Make sure you have a Portal backup.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000CeCAAA0","label":"API Connect->Management and Monitoring (MM)->Upgrade\/Downgrade"}],"ARM Case Number":"TS007120279","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2018.4.1.0"}]
Was this topic helpful?
Document Information
Modified date:
12 October 2021
UID
ibm16498175