Schema Versioning not enabled by default
Bug #898170 reported by
Ziad Sawalha
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Dolph Mathews |
Bug Description
Newly created database throws a DatabaseNotCont
Changed in keystone: | |
milestone: | none → essex-3 |
assignee: | nobody → Dolph Mathews (dolph) |
importance: | Undecided → Medium |
status: | New → Confirmed |
status: | Confirmed → In Progress |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | essex-3 → 2012.1 |
To post a comment you must log in.
This is fixed along with the rewrite of keystone-manage (bp keystone-manage2)
$ rm keystone.db manage version --database
$ ./bin/keystone-
Database not under version control