One revision is skipped when doing alembic upgrade head
#819
Labels
Comments
Zlopez
added a commit
to Zlopez/anitya
that referenced
this issue
Sep 2, 2019
* When using production database one revision was skipped. This was caused by bad order of the revisions. * Thanks to recent changes to alembic.ini one issue was found in ansible script that tried to replace non-existing line in alembic.ini. Fixes fedora-infra#819. Signed-off-by: Michal Konečný <[email protected]>
Merged
Zlopez
added a commit
that referenced
this issue
Sep 2, 2019
* When using production database one revision was skipped. This was caused by bad order of the revisions. * Thanks to recent changes to alembic.ini one issue was found in ansible script that tried to replace non-existing line in alembic.ini. Fixes #819. Signed-off-by: Michal Konečný <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I execute
alembic upgrade headone column is missing and it looks like this revision was just skipped.To fix this I need to manually downgrade to revision before the skipped one using
alembic downgrade 1ab95561edae, which means commenting the downgrade method, because the column is missing, and runningalembic upgrade headagain.Reported upstream sqlalchemy/alembic#598
The text was updated successfully, but these errors were encountered: