Running db_sync --check against new installs fails
Bug #1663627 reported by
Jimmy McCrory
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Richard |
Bug Description
If 'keystone-manage db_sync --check' is run against a new install, prior to any DB migrations, it will raise an exception.
DBMigrationError: Invalid version : 66
Changed in keystone: | |
milestone: | none → pike-1 |
To post a comment you must log in.
I was able to recreate by doing the following based on the latest patch in master [0].
1.) update tox environments using `tox -er --notest`
2.) drop and recreated the keystone database
3.) ran `keystone-manage db_sync --check`
The issues is that the code is looking for a database version [1] but it's not finding it because the database is actually empty [2].
[0] https:/ /github. com/openstack/ keystone/ tree/d5ce8ea0ed 6a3b9f748427d1b 552fb88ad738545 cdn.pasteraw. com/renjlmlq3ui 14jtnzh4b4iuklo 23xc9 cdn.pasteraw. com/i0wqp6za9ca yx6n1igr6hjgo7h zs29s
[1] http://
[2] http://