heat-db-setup should set default character set to utf-8

[Matt Riedemann]

Running the heat db migrations will fail if the heat database isn't created with the utf-8 character set.

The heat-db-setup script checks to see if there is an entry in the migrate_versions table which there is, but it's the base version (14) so the migrations failed but the script doesn't know that.

This is the error you'll see when the migrations fail:

ERROR: Tables "migrate_version" have non utf8 collation, please make sure all tables are CHARSET=utf8

[Matt Riedemann (mriedem)]

By the way, I'm using this version of mysql:

[root@szmlnx11 ~]# mysql --version
mysql Ver 14.14 Distrib 5.1.71, for ibm-linux-gnu (s390x) using readline 5.1

I'm on RHEL 6.5.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/71437

[Steven Hardy (shardy)]

Thanks for the fix, I saw the same issue on mariadb-5.5.34-2.fc20.x86_64 yesterday (but I was configuring the DB via openstack-db, which I guess needs a similar fix)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/71437
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=84e1942f0b53ff3be651f290f11879ddabac4b76
Submitter: Jenkins
Branch: master

commit 84e1942f0b53ff3be651f290f11879ddabac4b76
Author: Matt Riedemann <email address hidden>
Date: Wed Feb 5 17:26:25 2014 -0800

    Create heat database with default character set utf-8

    The heat-db-setup script wasn't creating the heat database with default
    character set utf-8 which can cause the migrations to fail.

    Closes-Bug: #1276880

    Change-Id: I35861af66d70314285fa76bb148e403aeea4b654

[Pádraig Brady (p-draigbrady)]

So this was triggered by the recent changes for bug 1261605