Relative db revision migration exception

Bug #1486790 reported by Daniel Allegood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.db
Fix Released
Critical
Unassigned

Bug Description

I'm observing a new failure in a sqlalchemy migration test as of this morning. Part of our testing would create an oslo_db.sqlalchemy.migration_cli.manager.MigrationManager and call a downgrade/upgrade of relative revisions (for example: manager.downgrade("-1") ). Now I'm observing this throw a "oslo_db.exception.DbMigrationError: Revision does not exist".

It looks as though the downgrade function in oslo_db/sqlalchemy/migration_cli/manager.py looks for an explicit revision id to exist in the revision argument (for a None) and not considering relative revision args like "-1", "+1", ect.

Changed in oslo.db:
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Boris Bobrov (bbobrov) wrote :
Changed in oslo.db:
status: Confirmed → Fix Committed
Changed in oslo.db:
milestone: none → 2.4.1
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.