Relation "Token" does not exist
When migrating or installing to an external metadata database, you may encounter an error where the web pods are failingAnd/ or restarting with an error noting "Relation token does not exist".
Ensure that the pre-requisite command is ran prior to attempting migration:
ALTER ROLE bometa SET search_path TO bometadata,public;
If using an alternate role than bometa
in your values file, simply change the role to reflect that role and run the command.
Then restart the web pods to trigger migrations with the below command:
If using IHC:
kubectl -n <NAMESPACE> rollout restart deployment/<prefix>-immuta-web
If using IEHC:
kubectl -n <NAMESPACE> rollout restart deployment/<prefix>-immuta-service
PreviousInstalling Kubernetes via `helm install` using a SHA instead of image tagNextAudit pod is restarting with "prisma migrations..." related errors on fresh installation
Last updated