Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

One revision is skipped when doing alembic upgrade head #819

Closed
Zlopez opened this issue Sep 2, 2019 · 0 comments · Fixed by #820
Closed

One revision is skipped when doing alembic upgrade head #819

Zlopez opened this issue Sep 2, 2019 · 0 comments · Fixed by #820
Labels

Comments

@Zlopez
Copy link
Contributor

Zlopez commented Sep 2, 2019

When I execute alembic upgrade head one 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 running alembic upgrade head again.

Reported upstream sqlalchemy/alembic#598

@Zlopez Zlopez added the type.bug label Sep 2, 2019
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]>
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
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant