Mike Logaciuk
04/03/2023, 2:15 PMFile "/usr/local/lib/python3.10/site-packages/prefect/server/database/alembic_commands.py", line 53, in alembic_upgrade
alembic.command.upgrade(alembic_config(), revision, sql=dry_run)
File "/usr/local/lib/python3.10/site-packages/alembic/command.py", line 378, in upgrade
script.run_env()
File "/usr/local/lib/python3.10/site-packages/alembic/script/base.py", line 272, in _catch_revision_errors
raise util.CommandError(resolution) from re
alembic.util.exc.CommandError: Can't locate revision identified by '422f8ba9541d'
Application startup failed. Exiting.
Our main API is running outside K8S on another server (VM with dedicated Postgres) with UI turned off, while pod on K8S is running with UI turned on - env is pointing the API outside K8S.
Agents on K8S work without any problem after, while UI can't start.
Is this an expected behaviour?
It's not the first time that new build destroys something on prod in our environment.Zanie
04/03/2023, 4:10 PMprefect config view
output for the UI container? As well as the full traceback?