Closed samip5 closed 7 months ago
Hi @samip5
The message migration already started
means that your setup step got stuck for some reason. In this case, you should run the command zitadel setup cleanup
manually, so the step is retried on the next setup.
I will try to find a way to define a job in kubernetes without starting it that can be executed manually instead.
Preflight Checklist
Version
7.3.0
App version
No response
Describe the problem caused by this bug
I'm trying to upgrade from chart 7.3.0 to 7.5.0 but unable due to zitadel-setup trying to create the database again, despite it existing already.
To reproduce
Logs
zitadel-setup:
Expected behavior
I would have expected it to be smart and see that it already exists, so it shouldn't try to re-create the database on upgrade but rather just run migrations if needed.
Relevant Configuration
My Helm values are here: https://github.com/samipsolutions/infra/blob/main/kubernetes/apps/security/zitadel/app/hr.yaml
Additional Context
No response