← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1300814] Re: Tables "migrate_version" have non utf8 collation

 

*** This bug is a duplicate of bug 1301036 ***
    https://bugs.launchpad.net/bugs/1301036

This is a dupe of bug 1301036, but LP is timing out when I try to "Mark
as duplicate."

** Tags removed: keystone
** Tags added: icehouse-rc-potential

** Changed in: keystone
       Status: New => Invalid

** Changed in: keystone (Ubuntu)
       Status: Confirmed => Invalid

** This bug has been marked a duplicate of bug 1301036
   openstack.common.db.sqlalchemy.migration utf8 table check issue on initial migration

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1300814

Title:
  Tables "migrate_version" have non utf8 collation

Status in OpenStack Identity (Keystone):
  Invalid
Status in “keystone” package in Ubuntu:
  Invalid

Bug description:
  On ubuntu 14.04
  I updated keystone to the version  1:2014.1~rc1-0ubuntu1.

  I drop the database and re-create.

  CREATE DATABASE keystone;
  GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'%' IDENTIFIED BY '$KEYSTONE_DBPASS';
  GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'localhost' IDENTIFIED BY '$KEYSTONE_DBPASS';
  GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'$' IDENTIFIED BY '$KEYSTONE_DBPASS';

  And then,

  keystone-manage db_sync

  I got the next error

  ./keystone/keystone.log:2014-04-01 10:49:20.681 5423 CRITICAL keystone [-] ValueError: Tables "migrate_version" have non utf8 collation, please make sure all tables are CHARSET=utf8
  ./keystone/keystone.log:2014-04-01 10:49:20.681 5423 TRACE keystone ValueError: Tables "migrate_version" have non utf8 collation, please make sure all tables are CHARSET=utf8

  Problem:
  Bad charset 

  Solution:
  alter table migrate_version charset=utf8;

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1300814/+subscriptions