Closed jeff1010322 closed 5 months ago
For additional info, I also disabled the wait-for-migration
init container conditions since I was having this issue just for testing purposes. The frontend and api were able to run after this, but getting this error when trying to do a sign up:
NoMethodError (undefined method `default_currency'
I see that this is likely related to this migration not finishing.
I figured out what was causing the issue. In my case the redis service was not coming up quick enough and the lago-migrate was failing to make the connection. When I updated the restart policy to OnFailure for the migrate job it worked on the second retry.
Not sure what the official solution for this should be. Maybe an init container check for redis on the migrate job in the helm charts. But either way doesn't appear to be an issue with the lago API.
@jeff1010322, ho yes I can add a wait for redis also on migrate job, it is already the case on api
!
Describe the bug Trying to test out Lago by deploying using the helm chart: https://github.com/getlago/lago-helm-charts Using PostgreSQL 14 on Google Cloud for the DB. The migrate-job always fails at the RunCustomerCurrencyTask.
The previous migration jobs worked and created tables. But this and all later migrations will not run due to it failing each time on this migration. Looking for any information regarding what may be causing this particular migration to fail.
To Reproduce Steps to reproduce the behavior:
As a note I did fork and run my own version of the helm chart mainly just to add in trace flags and manually removed the postgres dependency as I was unable to prevent it from deploying postgres containers with just the configs.
The migrate-job appears to be running this command:
Expected behavior Migrate job to finish successfully and initialize the DB.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context lago-migrate logs:
Version