Why is that on reboot in a container env - the portal has data issues - the reboot could happen anytime
Error:
ingress: Checking if apim-dev-portal exist in TENANT_INFO
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5622 0 5622 0 0 209k 0 --:--:-- --:--:-- --:--:-- 203k
ingress: Checking if Proxy exists for apim-dev-portal
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 327 0 327 0 0 8233 0 --:--:-- --:--:-- --:--:-- 8384
ingress: Proxy exists for apim-dev-portal
ingress: Updating Proxy with new key
ingress: Error updating Proxy with new key
ERROR - Failed executing the script: /opt/docker/rc.d/zzz_init-tenant-enrollment.sh
Release : 5.1
Custom accessed the APIM tenant portal (admin tenant used internally for portal functionality) to enroll gateway and create API - this caused the failure to start APIM container
Resolved it by creating a tenant using the steps in the doc/github:
https://github.com/CAAPIM/apim-charts/tree/stable/utils
The documented procedure is to follow the docs to create your own tenant (empty portal) Enroll gateway proxy and add apis/application and other portal objects for your organization
,