After upgrade to 2.9.0, our UI which was is run on...
# prefect-community
After upgrade to 2.9.0, our UI which was is run on K8S on separate pod, stopped working:
File "/usr/local/lib/python3.10/site-packages/prefect/server/database/", line 53, in alembic_upgrade
alembic.command.upgrade(alembic_config(), revision, sql=dry_run)
File "/usr/local/lib/python3.10/site-packages/alembic/", line 378, in upgrade
File "/usr/local/lib/python3.10/site-packages/alembic/script/", 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.
Sounds like the UI is not correctly configured to talk to the API
It should not be attempting to run database migrations if you have an API elsewhere
Can you share the
prefect config view
output for the UI container? As well as the full traceback?