With MySQL 5.6 setup to use UTF-8 for everything, the 033 migration
will fail. This is because a VARCHAR(256) cannot be indexed in UTF-8
databases. In versions of MySQL before 5.6, this produced a warning and
a truncated, less-useful index. In 5.6 it was changed to an error.
We will reduce these columns further to 64 bytes in the model in a
subsequent fix. For now, we will just create the table with 64 character
columns on new systems, which will allow this migration to work properly
on mysql-5.6. There is no danger of overflow, as 64 chars is what Keystone
uses for them anyway.
Closes-Bug: #1316646
(cherry picked from commit db0a7fe91d3eddc6d337028332fbd496bb000df2)
Reviewed: https:/ /review. openstack. org/142431 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=314437f2323 ed90ec2338fc7da e78b3be70c2beb
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit 314437f2323ed90 ec2338fc7dae78b 3be70c2beb
Author: Clint Byrum <email address hidden>
Date: Tue May 6 10:48:36 2014 -0700
Patch 033 migration to work w/ MySQL 5.6
With MySQL 5.6 setup to use UTF-8 for everything, the 033 migration
will fail. This is because a VARCHAR(256) cannot be indexed in UTF-8
databases. In versions of MySQL before 5.6, this produced a warning and
a truncated, less-useful index. In 5.6 it was changed to an error.
We will reduce these columns further to 64 bytes in the model in a
subsequent fix. For now, we will just create the table with 64 character
columns on new systems, which will allow this migration to work properly
on mysql-5.6. There is no danger of overflow, as 64 chars is what Keystone
uses for them anyway.
Closes-Bug: #1316646 6d337028332fbd4 96bb000df2)
(cherry picked from commit db0a7fe91d3eddc
Change-Id: I27b9c61828301b a8c392b3d316f65 6641af753bc