Why is it 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
API Portal 5.1
A user 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.
Create a tenant using the steps in the doc/GitHub:
https://github.com/CAAPIM/apim-charts/tree/stable/utils
The documented procedure allows you to create your own tenant (empty portal). Enroll the gateway proxy and add APISs/applications and other portal objects for your organization.