release_failed
Severity: error. Your app's release step (its database migrations) did not succeed, so the new version was not started. The version that ran before keeps serving.
What happened
When your app has a database, Kaviris runs its release step once per deploy,
before the new version starts: a release: line in your Procfile, a
db:migrate (or migrate) script in package.json, or Django's
manage.py migrate. It runs with the new version's code, your secrets and
your database, and never again when the app wakes from sleep or restarts.
It runs twice for every deploy: first while Kaviris checks the build, against a new empty database, then against your app's database. Either one failing stops the deploy, and the message says which. A rollback to an earlier release runs no migrations at all (there are no down-migrations).
How to fix it
- Read the release step's last lines in the refusal: they name the failing migration or the missing setting.
- Run the same command locally against a copy of your database, fix the migration, and deploy again.
- A migration that needs a secret (an encryption key, say) gets the same secrets as your app: declare and set it first.
- A command that resets the database, pushes a schema (
db push) or runs a development migration (migrate dev) is never run as a release step.