Migrations may create MyISAM tables
Bug #1191110 reported by
Dolph Mathews
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Brant Knudson |
Bug Description
Following bug 1189633, it was discovered that keystone's migrations do not explicitly define InnoDB as the desired storage engine, although that is what we recommend and test against.
In the case of RHEL, mysql's default storage engine is set to MyISAM, which causes keystone-manage db_sync to fail as of migration 23 due to a lack of support for constraints.
Changed in keystone: | |
assignee: | Brant Knudson (blk-u) → Dolph Mathews (dolph) |
status: | Confirmed → In Progress |
tags: | removed: grizzly-backport-potential |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
This is related to nova's bug 741274