cinder test_migrations fails for mysql

[Jay Bryant]

Cinder test_migrations is failing for test_migration_008, 009, 010, 011, 018 and 020 fail because the test case is checking for a BOOLEAN type but a 'TINYINT' is being returned.

This will require a change similar to changes made for DB2 to check the engine type and update the check accordingly.

[Jay Bryant (jsbryant)]

Some details on how to recreate this:

1) Edit cinder/tests/test_migrations.conf
2) Uncomment the mysql line and configure it for your system.
3) Run ./run_tests.sh -V cinder.tests.test_migrations

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/65169
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=2a7b11922bd9389287915c45de92ca5eed3d448e
Submitter: Jenkins
Branch: master

commit 2a7b11922bd9389287915c45de92ca5eed3d448e
Author: Jay S. Bryant <email address hidden>
Date: Mon Jan 6 14:45:34 2014 -0600

    Add bool_type dictionary to test_migrations

    A number of MySQL migration tests fail because the test case
    is verifying that an sqlalchemy.types.BOOLEAN column was created.
    When the column type is checked, however, mysql reports the type as
    sqlalchemy.dialects.mysql.TINYINT. The mismatch causes numerous
    test cases to fail for MySQL.

    This creates a dictionary for each engine being tested to handle the
    different boolean types.

    postgresql and DB2 encounter similar issues. Subsequent patches
    will make the appropriate changes for those databases.

    Change-Id: I81cb3c6feeacf887f1f473ec54414e0e215d2c24
    Closes-bug: 1260126