oslo.db

migration_cli.ext_migrate version check doesn't support migrate's VerNum

Bug #1413239 reported by Boris Bobrov on 2015-01-21

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	oslo.db	Confirmed	Medium	Unassigned

Bug Description

In Keystone we determine latest available version for upgrade using migrate's http://sqlalchemy-migrate.readthedocs.org/en/latest/api.html?highlight=version#migrate.versioning.repository.Repository.version

When this version passed to ext_migrate.upgrade, it raises ValueError: http://paste.openstack.org/show/159771/ . It would be great if ext_migrate supported VerNum, produced by sqlalchemy-migrate.

See original description

Boris Bobrov (bbobrov) on 2015-01-21

summary:

- migration_cli.ext_migrate raises ValueError
+ migration_cli.ext_migrate version check doesn't support migrate's VerNum

Boris Bobrov (bbobrov) on 2015-01-21

description:	updated
description:	updated

Doug Hellmann (doug-hellmann) on 2015-03-02

Changed in oslo.db:
status:	New → Confirmed
importance:	Undecided → Medium

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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