| 2015-01-21 14:50:43 |
Boris Bobrov |
bug |
|
|
added bug |
| 2015-01-21 14:52:19 |
Boris Bobrov |
summary |
migration_cli.ext_migrate raises ValueError |
migration_cli.ext_migrate version check doesn't support migrate's VerNum |
|
| 2015-01-21 14:57:59 |
Boris Bobrov |
description |
When version passed to ext_migrate.upgrade does not equal to 'head', it raises ValueError: http://paste.openstack.org/show/159771/ |
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 itself. |
|
| 2015-01-21 14:58:25 |
Boris Bobrov |
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 itself. |
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. |
|
| 2015-03-02 19:13:40 |
Doug Hellmann |
oslo.db: status |
New |
Confirmed |
|
| 2015-03-02 19:13:43 |
Doug Hellmann |
oslo.db: importance |
Undecided |
Medium |
|
