alarm_history_project_fkey Constraint fails on el6 MySQL
Bug #1224666 reported by
Dan Prince
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Fix Released
|
High
|
Eoghan Glynn |
Bug Description
Using Ceilometer master I'm now getting the following exception when migration 015_add_
2013-09-12 18:52:26.251 12849 CRITICAL ceilometer [-] (OperationalError) (1005, "Can't create table 'ceilometer.
Changed in ceilometer: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → havana-rc1 |
Changed in ceilometer: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
Changed in ceilometer: | |
status: | Triaged → In Progress |
Changed in ceilometer: | |
status: | Fix Committed → Fix Released |
Changed in ceilometer: | |
milestone: | havana-rc1 → 2013.2 |
To post a comment you must log in.
This issue occurs because the add_alarm_ history_ table migration eagerly included mysql_engine= 'InnoDB' in the new table definition: /github. com/openstack/ ceilometer/ blob/master/ ceilometer/ storage/ sqlalchemy/ migrate_ repo/versions/ 015_add_ alarm_history_ table.py# L42
https:/
with the expectation that https:/ /review. openstack. org/45306 would have landed first.
With InnoDB explicitly selected for all tables or none, the 'ALTER TABLE' issue above does not occur.