migrations are failing. This looks oddly like the other error

[SoneNiko]

#426

[evroon]

Is this shortly after reinitializing the db or did you use a new version of Bracket while still using the same database state?

I think alembic is running migrations that shouldn't be run, maybe the value in your alembic_version column ended up being old/null.

[SoneNiko]

This kinda happened after both of these scenarios. I got around it by disabling the alembic migrations using the environment variable. This is just a temporary solution. I don't know what exactly is causing these issues with migration but since its probably going to happen again i will just open an issue again then.

To my limited understanding, the core issue seems to be that the migration is trying to create an pgsql enum type which already exists which is what happens last time. maybe its just an issue with how alembic handles migrations for enum types.

[robigan]

@SoneNiko You can close this now. Migrations were manually made using alembic stamp version in prod. Internal for us: See incident report 004 for steps taken.