fwiw, we faced same issue in keystone.migrate_version table. The fix was to set default charset for all tables to 'utf8';
I think we should have migration script for all components and document mysql setting to use utf8 as default character set for new databases.
fwiw, we faced same issue in keystone. migrate_ version table. The fix was to set default charset for all tables to 'utf8';
I think we should have migration script for all components and document mysql setting to use utf8 as default character set for new databases.