yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #01088
[Bug 829209] Re: MySQL/UTF-8: Issue while executing nova-manage db sync
nova now requires all database to be innodb, so I think we're ok now
(this was released in Folsom)
** Changed in: nova
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/829209
Title:
MySQL/UTF-8: Issue while executing nova-manage db sync
Status in MySQL Server:
Unknown
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
When executing "/usr/bin/nova-manage db sync" following error was given at /var/log/manage/nova-manage.log.
Nova compute is trying to configure with MY SQL 5.1.53
(nova): TRACE: raise errorclass, errorvalue(nova): TRACE:
OperationalError: (OperationalError) (1071, 'Specified key was too
long; max key length is 1000 bytes') '\nCREATE TABLE
user_project_association (\n\tcreated_at DATETIME, \n\tupdated_at
DATETIME, \n\tdeleted_at DATETIME, \n\tdeleted BOOL, \n\tuser_id
VARCHAR(255) NOT NULL, \n\tproject_id VARCHAR(255) NOT NULL,
\n\tPRIMARY KEY (user_id, project_id), \n\tCHECK (deleted IN (0, 1)),
\n\tFOREIGN KEY(project_id) REFERENCES projects (id), \n\tFOREIGN
KEY(user_id) REFERENCES users (id)\n)\n\n' ()(nova): TRACE:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/829209/+subscriptions