Dan - on RHEL 6.4 with mysql 5.1.69, I'm seeing the ceilometer migrations run to completion.
If you're still seeing issues, can you attach the logs/stacktraces etc.?
BTW I did initially see an issue with an alembic migration failing due to:
https://bugs.launchpad.net/ceilometer/+bug/1221467
i.e.:
File "/opt/stack/ceilometer/ceilometer/storage/sqlalchemy/alembic/versions/b6ae66d05e3_remove_extra_indexes.py", line 68, in index_cleanup op.drop_constraint(uniq_name, table_name, type_='unique') TypeError: drop_constraint() got an unexpected keyword argument 'type_'
which may be resolved by updating the alembic version from 4.2 to 6.0.
Dan - on RHEL 6.4 with mysql 5.1.69, I'm seeing the ceilometer migrations run to completion.
If you're still seeing issues, can you attach the logs/stacktraces etc.?
BTW I did initially see an issue with an alembic migration failing due to:
https:/ /bugs.launchpad .net/ceilometer /+bug/1221467
i.e.:
File "/opt/stack/ ceilometer/ ceilometer/ storage/ sqlalchemy/ alembic/ versions/ b6ae66d05e3_ remove_ extra_indexes. py", line 68, in index_cleanup drop_constraint (uniq_name, table_name, type_='unique')
op.
TypeError: drop_constraint() got an unexpected keyword argument 'type_'
which may be resolved by updating the alembic version from 4.2 to 6.0.